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: e2fsprogs and fast symlink
Date: Fri, 21 Mar 2008 17:12:34 +0530	[thread overview]
Message-ID: <20080321114234.GB6542@skywalker> (raw)

Hi Ted,

The below test case fails x86
#ln -s sfdajsfsdsdfskjdgfkshdfkshdfkgdsjdsjdhsdfdafdsgakfasdgfsjksdsdsdfsd p 
#sync
#rm p
root@elm3b165:~# /usr/local/e2fsprogs/sbin/e2fsck  -f  /dev/sda5
e2fsck 1.40.8 (13-Mar-2008)
Pass 1: Checking inodes, blocks, and sizes
Fast symlink 12 has EXTENT_FL set.  Clear<y>? 

ie because after deleting the file we have
debugfs:  stat <12>
Inode: 12   Type: symlink    Mode:  0777   Flags: 0x80000   Generation:
25346603
User:     0   Group:     0   Size: 0
File ACL: 0    Directory ACL: 0
Links: 0   Blockcount: 0
Fragment:  Address: 0    Number: 0    Size: 0
ctime: 0x47e39ea3 -- Fri Mar 21 11:40:19 2008
atime: 0x47e39e9e -- Fri Mar 21 11:40:14 2008
mtime: 0x47e39e9a -- Fri Mar 21 11:40:10 2008
dtime: 0x47e39ea3 -- Fri Mar 21 11:40:19 2008
Size of extra inode fields: 28
Fast_link_dest: 


shouldn't e2fsprogs also look at whether the inode is in use ?

-aneesh

             reply	other threads:[~2008-03-21 11:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 11:42 Aneesh Kumar K.V [this message]
2008-03-24 11:37 ` e2fsprogs and fast symlink Aneesh Kumar K.V
2008-03-24 20:45   ` Andreas Dilger
2008-03-24 21:26     ` Theodore Tso
2008-03-25  0:40       ` Andreas Dilger
2008-03-24 12:20 ` [E2FSPROGS, PATCH] e2fsck: Don't object to extents flags on deleted fast symlinks Theodore Ts'o
2008-03-24 12:25 ` e2fsprogs and fast symlink Christian Kujau
2008-03-24 12:36   ` Theodore Tso
2008-03-24 13:18     ` Christian Kujau

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=20080321114234.GB6542@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