Yep. It would be very good if you could capture a preferably small image of a filesystem which makes this happen and make it available to the committers via a PR
Poul-Henning In message <19990407205026.a27...@cicely8.cicely.de>, Bernd Walter writes: ># fsck -p >/dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% >fragmentation) >/dev/rccd0c: CANNOT READ: BLK 16 >/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: page is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >/dev/rccd0c: CANNOT SEEK: BLK -1 >/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >/dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, >4.2% fragmentation) >/dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% >fragmentation) > >ccd0 was not configured the time I started fsck > >-- > B.Walter > > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message