Skip to contentSkip to conversation

2.5.0 breakage even with fix?

DISCUSSION Petr Vandrovec 5 participants 6 messages Nov 23, 2001 – Nov 24, 2001

lore
Share & tools
lore
#0 lore raw

Hi Al,
I'm now running 2.5.0 with fix you posted - and now during dselect
run I received:

Unpacking replacement manpages ...
EXT2-fs error (device ide0(3,3)): ext2_check_page: bad entry in directory
#3801539: unaligned directory entry - offset=0, inode=1801675088, rec_len=26465, name_len=101
Remounting filesystem read-only
rm: cannot remove directory `/var/lib/dpkg/tmp.ci': Read-only file system
...

and system is obviously unusable. I'll probably reboot and run fsck again. If someone can show me how I can dump contents of some inode by number (and not by name) in debugfs, I can look into inode itself... I found only 'ncheck', to convert number to name, and this is running and running...

System was running 2.5.0 without patch for some time, but I followed your guidelines for rebooting:

fuser -k /
sync
mount -o remount,ro /
sync
reboot

After reboot fsck was NOT run, so it is possible that there might be some corruption - but I ran fsck on my non-root partition after boot, and it did not show any problems.
Thanks,
Petr Vandrovec [email protected]

#1 lore raw
Quoted 3 lines · Petr Vandrovec

After reboot fsck was NOT run, so it is possible that there might be some corruption - but I ran fsck on my non-root partition after boot, and it did not show any problems.

fsck -f

Filesystem _is_ marked clean, so unless you do forced fsck no checks are done.

Moreover, attempt to work with corrupted fs can break in very interesting ways, so unless you do fsck -f even correct kernel (be it patched 2.4.15 or something earlier than 2.4.15-pre9) will not help.

#2 lore raw
Quoted 8 lines · Alexander Viro

fsck -f

Filesystem _is_ marked clean, so unless you do forced fsck no checks are done.

Moreover, attempt to work with corrupted fs can break in very interesting ways, so unless you do fsck -f even correct kernel (be it patched 2.4.15 or something earlier than 2.4.15-pre9) will not help.

If the filesystem is marked clean, does that mean that people with journalling file systems are fscked? (since there might be no journal entry of what hasn't finished.)

just guessing, I don't know how these work, but if ext2 gets the 'clean' bit set, i can imagine the journaling file systems refusing to check anything...

Robert.

#3 lore raw
Quoted 3 lines · Robert Boermans

If the filesystem is marked clean, does that mean that people with journalling file systems are fscked? (since there might be no journal entry of what hasn't finished.)

Well, if filesystem doesn't have a recovery tool that would allow forced check mode - you _are_ screwed. As you will be again and again if you get memory corruption/driver bugs/fs bugs/RAID bugs/physical disk problems/etc.

Again, if filesystem trusts clear bit to the extent that you have no way to convince it that checks _are_ needed - it's unfit for any serious use. I suspect that by now everybody had learnt that much - that used to be a permanent source of problems with early journalling filesystems and AFAIK all of them had been fixed since then.

#4 lore raw

Al,

I am not seeing any more breakage with this fix with NWFS.

Jeff

----- Original Message -----
From: "Alexander Viro" <[email protected]>
To: "Robert Boermans" <[email protected]>
Cc: "Petr Vandrovec" <[email protected]>; <[email protected]>
Sent: Saturday, November 24, 2001 4:03 PM
Subject: Re: 2.5.0 breakage even with fix?

Quoted 6 lines · Robert Boermans
Quoted 3 lines

If the filesystem is marked clean, does that mean that people with journalling file systems are fscked? (since there might be no journal

entry

Quoted 5 lines
Quoted 1 line

of what hasn't finished.)

Well, if filesystem doesn't have a recovery tool that would allow forced check mode - you _are_ screwed. As you will be again and again if you get memory corruption/driver bugs/fs bugs/RAID bugs/physical disk

problems/etc.

Quoted 5 lines

Again, if filesystem trusts clear bit to the extent that you have no way to convince it that checks _are_ needed - it's unfit for any serious use. I suspect that by now everybody had learnt that much - that used to be a permanent source of problems with early journalling filesystems and

AFAIK

Quoted 7 lines

all of them had been fixed since then.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#5 lore raw
In reply to Petr Vandrovec
Quoted 9 lines · Petr Vandrovec

I'm now running 2.5.0 with fix you posted - and now during dselect
run I received:

Unpacking replacement manpages ...
EXT2-fs error (device ide0(3,3)): ext2_check_page: bad entry in directory
#3801539: unaligned directory entry - offset=0, inode=1801675088, rec_len=26465, name_len=101
Remounting filesystem read-only
rm: cannot remove directory `/var/lib/dpkg/tmp.ci': Read-only file system

Did you run e2fsck -f after running unpatched 2.4.15/2.5.0? This may be left-over garbage from the other problem.

Quoted 4 lines

and system is obviously unusable. I'll probably reboot and run fsck again. If someone can show me how I can dump contents of some inode by number (and not by name) in debugfs, I can look into inode itself... I found only 'ncheck', to convert number to name, and this is running and running...

debugfs> stat <inum>
debugfs> dump <inum> /tmp/file

Note that you need to include the <> around the inode number.

Quoted 9 lines

System was running 2.5.0 without patch for some time, but I followed your guidelines for rebooting:

fuser -k /
sync
mount -o remount,ro /
sync
reboot

Quoted 3 lines

After reboot fsck was NOT run, so it is possible that there might be some corruption - but I ran fsck on my non-root partition after boot, and it did not show any problems.

Ah, yes. Definitely sounds like left over corruption.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/