From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.0 breakage even with fix?
Date: Sat, 24 Nov 2001 01:05:56 MET-1 [thread overview]
Message-ID: <A0AA3407CDC@vcnet.vc.cvut.cz> (raw)
On 24 Nov 01 at 0:54, viro@math.psu.edu wrote:
> 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
Well, ncheck finished.
debugfs: stat /var/lib/dpkg/tmp.ci
Inode: 3801539 Type: directory Mode: 0755 Flags: 0x0 Generation: 537829
User: 0 Group: 0 Size: 4096
File ACL: 0 Directory ACL: 0
Links: 2 Blockcount: 8
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x3bfede00 -- Sat Nov 24 00:38:40 2001
atime: dtto
mtime: dtto
BLOCKS:
(0):7603845
TOTAL: 1
debugfs: cat /var/lib/dpkg/tmp.ci
Package: diff
Version: 2.7-28
Section: base
Priority: required
Architecture: i386
...
It does not look like a directory to me. Unfortunately, as we
do not have coherent /dev/hda3 cache, I have no idea how to read
real contents of /var/lib/dpkg/tmp.ci, but
ls -l /var/lib/dpkg/tmp.ci/ reemited error message about
ext2-fs error, so I think that it is real problem, and my tmp.ci directory
contains some file contents instead. And I'm 100% sure that
/var/lib/dpkg/tmp.ci was created with patched kernel :-(
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2001-11-24 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 1:05 Petr Vandrovec [this message]
2001-11-24 0:14 ` Re: 2.5.0 breakage even with fix? Jeff Merkey
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 0:54 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
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=A0AA3407CDC@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