From: Eric Sandeen <sandeen@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: powerpc e2fsprogs and fast symlink
Date: Thu, 20 Mar 2008 14:49:00 -0500 [thread overview]
Message-ID: <47E2BFAC.5080806@redhat.com> (raw)
In-Reply-To: <20080319193801.GA16687@skywalker>
Aneesh Kumar K.V wrote:
> Hi Ted,
>
> While testing on powerpc i found that e2fsck is getting confused about
> fast symlink on powerpc. On x86_64 it works fine.
Just as a sanity check I made an ext4 image on ppc with fast/long
symlinks, dirs, files of various sizes etc; e2fsck from next fails on ppc:
e2fsck 1.40.8 (13-Mar-2008)
Pass 1: Checking inodes, blocks, and sizes
Error while reading over extent tree in inode 12: Corrupt extent header
Clear inode? no
Segmentation fault
but transporting the image to x86_64, e2fsck is fine. So at least it
doesn't look like an on-disk problem. :)
-Eric
prev parent reply other threads:[~2008-03-20 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 19:38 powerpc e2fsprogs and fast symlink Aneesh Kumar K.V
2008-03-20 7:47 ` Aneesh Kumar K.V
2008-03-21 5:18 ` Eric Sandeen
2008-03-21 5:40 ` Eric Sandeen
2008-03-20 12:50 ` Theodore Tso
2008-03-20 12:56 ` Aneesh Kumar K.V
2008-03-20 19:49 ` Eric Sandeen [this message]
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=47E2BFAC.5080806@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).