So a partition on an external (USB) drive reported problems. I ran e2fsck on it, repeatedly. I unfortunately didn't capture the output, but it moved and cleared many inodes. Now when I run "e2fsck -y /dev/sde6" I get the same problems reported and "fixed" over and over. Makes me doubt they were actually fixed. A sample:
Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Filesystem contains large files, but lacks LARGE_FILE flag in superblock. Fix? yes Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong for group #0 (24047, counted=32244). Fix? yes Free blocks count wrong for group #4 (32257, counted=1537). Fix? yes Free blocks count wrong for group #5 (32254, counted=0). Fix? yes Free blocks count wrong for group #6 (32257, counted=0). Fix? yes [snip] Free inodes count wrong (285175, counted=2443180). Fix? yes /dev/sde6: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sde6: 20/2443200 files (10.0% non-contiguous), 602333/4883752 blocks Full capture is at http://panix.com/~carlf/neverends.txt if anyone think it'll help. Is this a known e2fsck bug? I don't mean unfixable problems, I mean reporting that they're fixed but not actually fixing them. Thanks. -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
