From: Andreas Dilger <adilger@turbolabs.com>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.5.0 breakage even with fix?
Date: Fri, 23 Nov 2001 17:23:03 -0700 [thread overview]
Message-ID: <20011123172303.O1308@lynx.no> (raw)
In-Reply-To: <A0A71547524@vcnet.vc.cvut.cz>
In-Reply-To: <A0A71547524@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Sat, Nov 24, 2001 at 12:54:10AM +0000
On Nov 24, 2001 00:54 +0000, Petr Vandrovec wrote:
> 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.
> 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.
> 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.
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/
next prev parent reply other threads:[~2001-11-24 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 0:54 2.5.0 breakage even with fix? Petr Vandrovec
2001-11-24 0:13 ` Alexander Viro
2001-11-24 23:05 ` Robert Boermans
2001-11-24 23:03 ` Alexander Viro
2001-11-24 23:14 ` Jeff Merkey
2001-11-24 0:23 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 1:05 Petr Vandrovec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011123172303.O1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.