From: Olaf Hering <olh@suse.de>
To: Dave Johnson <djohnson+linux-kernel@sw.starentnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cramfs mounts provide corrupted content since 2.6.15
Date: Sat, 25 Feb 2006 23:01:30 +0100 [thread overview]
Message-ID: <20060225220130.GA2748@suse.de> (raw)
In-Reply-To: <17408.34808.422077.518881@zeus.sw.starentnetworks.com>
On Sat, Feb 25, Dave Johnson wrote:
> Looking at your output it's definitely getting inodes confused with
> each other so the checks in cramfs_iget5_test() aren't working.
>
> Can you stat the files in question to make sure they are actually
> inode #1 on a working as well as non-working kernel? If your mkcramfs
> isn't using #1 for empty files/links/dirs that'd be the problem.
Another try, and different results again:
./etc/nsswitch.conf: FAILED
./usr/lib/perl5/5.8.8/ppc-linux-thread-multi-64int/auto/Data/Dumper/Dumper.so: FAILED
./usr/lib/perl5/5.8.8/ppc-linux-thread-multi-64int/auto/Fcntl/Fcntl.so: FAILED
./usr/lib/perl5/5.8.8/ppc-linux-thread-multi-64int/auto/IO/IO.so: FAILED
./usr/lib/perl5/5.8.8/ppc-linux-thread-multi-64int/auto/POSIX/POSIX.so: FAILED
./usr/lib/perl5/5.8.8/ppc-linux-thread-multi-64int/auto/Sys/Hostname/Hostname.so: FAILED
./usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi-64int/auto/Compress/Zlib/Zlib.so: FAILED
./usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi-64int/auto/Locale/gettext/gettext.so: FAILED
inode numbers match in both cases, just the filesize is zero and they have only one block.
File: `./usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi-64int/auto/Locale/gettext/gettext.so'
Size: 0 Blocks: 1 IO Block: 4096 regular empty file
Device: 701h/1793d Inode: 53053956 Links: 1
Access: (0444/-r--r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 1970-01-01 01:00:00.000000000 +0100
Change: 1970-01-01 01:00:00.000000000 +0100
File: `./usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi-64int/auto/Locale/gettext/gettext.so'
Size: 24004 Blocks: 47 IO Block: 4096 regular file
Device: 702h/1794d Inode: 53053956 Links: 1
Access: (0555/-r-xr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 1970-01-01 01:00:00.000000000 +0100
Change: 1970-01-01 01:00:00.000000000 +0100
./var/spool/locks turned into a file:
File: `./var/spool/locks'
Size: 0 Blocks: 1 IO Block: 4096 regular empty file
Device: 701h/1793d Inode: 85741484 Links: 1
Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 1970-01-01 01:00:00.000000000 +0100
Change: 1970-01-01 01:00:00.000000000 +0100
File: `./var/spool/locks' -> `../lock'
Size: 7 Blocks: 1 IO Block: 4096 symbolic link
Device: 702h/1794d Inode: 85741484 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 1970-01-01 01:00:00.000000000 +0100
Change: 1970-01-01 01:00:00.000000000 +0100
next prev parent reply other threads:[~2006-02-25 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 11:08 cramfs mounts provide corrupted content since 2.6.15 Olaf Hering
2006-02-25 12:55 ` Olaf Hering
2006-02-25 16:38 ` Dave Johnson
2006-02-25 22:01 ` Olaf Hering [this message]
2006-02-27 16:31 ` Dave Johnson
2006-02-28 19:14 ` Chris Mason
2006-02-28 20:40 ` Dave Johnson
2006-02-28 20:53 ` Chris Mason
2006-02-28 21:08 ` Dave Johnson
2006-02-28 21:13 ` Chris Mason
[not found] ` <20060301155813.245d71ff.akpm@osdl.org>
[not found] ` <20060301235858.GA6792@suse.de>
[not found] ` <17414.16541.260439.712849@zeus.sw.starentnetworks.com>
[not found] ` <20060302115446.GA9708@suse.de>
[not found] ` <20060302093216.67b90533.akpm@osdl.org>
2006-03-02 17:45 ` [PATCH] " Dave Johnson
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=20060225220130.GA2748@suse.de \
--to=olh@suse.de \
--cc=djohnson+linux-kernel@sw.starentnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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.