Yes, I had the same problem some days ago on a lfs partition after upgrading
to lfs. After a time I couldn't write anything (the write process stops
responding) on that fs so i had the copy my datas and then do newfs_lfs.

Cheers,
Mihai

-----Original Message-----
From: John Goerzen <jgoerzen@complete.org>
To: Mihai Chelaru <mihai@romtelenet.org>
Cc: current-users@netbsd.org <current-users@netbsd.org>
Date: Tuesday, January 15, 2002 3:38 AM
Subject: Re: lfs_cleanerd


>Mihai Chelaru <mihai@romtelenet.org> writes:
>
>> Is this normal ? It stays like that all the time. And my HDD is working
>> all this time.
>
>I have a machine where lfs_cleanerd started spewing crap to the
>console and to /var/log/messages recently:
>
>Lots of stuff like this:
>
>Jan 14 20:35:02 sam lfs_cleanerd[25502]: seg 1 (0x810), ino 366801 lbn -1,
0xf51 != 0xf55
>Jan 14 20:35:02 sam lfs_cleanerd[25502]: bi_daddr = 0x1100141 = 156160b;
0x8606a00 - 0x85e0000 = 158208
>Jan 14 20:35:02 sam lfs_cleanerd[25502]: seg 8704 (0x1100010), ino 320769
lbn -1, 0x1100141 != 0x1100145
>Jan 14 20:35:03 sam lfs_cleanerd[25502]: bi_daddr = 0x10ffd21 = 664064b;
0x8682680 - 0x85e0000 = 665216
>Jan 14 20:35:03 sam lfs_cleanerd[25502]: seg 8703 (0x10ff810), ino 366832
lbn -1, 0x10ffd21 != 0x10ffd23
>Jan 14 20:35:03 sam lfs_cleanerd[25502]: bi_daddr = 0x10ff2f1 = 377344b;
0x863c680 - 0x85e0000 = 378496
>Jan 14 20:35:03 sam lfs_cleanerd[25502]: seg 8702 (0x10ff010), ino 320784
lbn -1, 0x10ff2f1 != 0x10ff2f3
>
>The same stuff, over and over again, about once every 5 seconds.
>
>I tried umounting the partition, running fsck_lfs on it (found no
>errors), but no avail.  I'm wondering if it's the result of a version
>mismatch between lfs_cleanerd and the kernel.  I have had a lot of
>trouble building userland lately so it's entirely possible.
>
>-- John
>