public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: powerpc e2fsprogs and fast symlink
Date: Thu, 20 Mar 2008 01:08:01 +0530	[thread overview]
Message-ID: <20080319193801.GA16687@skywalker> (raw)

Hi Ted,

While testing on powerpc i found that e2fsck is getting confused about
fast symlink on powerpc. On x86_64 it works fine.

lrwxrwxrwx  1 root root    60 Mar 19 15:18 d -> /usr/share/icons/hicolor/48x48/apps/gnome-netstatus-txrx.png
[root@gekko-lp2 ~]# /usr/local/e2fsprogs/sbin/debugfs  /dev/sda7 
debugfs 1.40.8 (13-Mar-2008)
debugfs:  stat d
Inode: 24483   Type: symlink    Mode:  0777   Flags: 0x80000
Generation: 2913520215
User:     0   Group:     0   Size: 60
File ACL: 0    Directory ACL: 0
Links: 1   Blockcount: 8
Fragment:  Address: 0    Number: 0    Size: 0
ctime: 0x47e166f9 -- Wed Mar 19 15:18:17 2008
atime: 0x47e166fb -- Wed Mar 19 15:18:19 2008
mtime: 0x47e166f9 -- Wed Mar 19 15:18:17 2008
Size of extra inode fields: 28
BLOCKS:

debugfs:

root@gekko-lp2 ~]# /usr/local/e2fsprogs/sbin/e2fsck  -f /dev/sda7
e2fsck 1.40.8 (13-Mar-2008)
Pass 1: Checking inodes, blocks, and sizes
Error while reading over extent tree in inode 24483: Corrupt extent
header
Clear inode<y>? yes

Inode 24483, i_blocks is 8, should be 0.  Fix<y>? yes

Fast symlink 100055 has EXTENT_FL set.  Clear<y>? 

-aneesh

             reply	other threads:[~2008-03-19 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 19:38 Aneesh Kumar K.V [this message]
2008-03-20  7:47 ` powerpc e2fsprogs and fast symlink 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

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=20080319193801.GA16687@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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