public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.0 breakage even with fix?
Date: Sat, 24 Nov 2001 00:54:10 MET-1	[thread overview]
Message-ID: <A0A71547524@vcnet.vc.cvut.cz> (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
                                                    vandrove@vc.cvut.cz
                                                    
                                                    

             reply	other threads:[~2001-11-23 23:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24  0:54 Petr Vandrovec [this message]
2001-11-24  0:13 ` 2.5.0 breakage even with fix? 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
  -- 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=A0A71547524@vcnet.vc.cvut.cz \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox