From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH 0/4] fat: fix ESTALE errors
Date: Tue, 21 Aug 2012 15:41:36 +0900 [thread overview]
Message-ID: <874nnwiw67.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd8fkV5x454vtXvwM6LN3Hb2dLgemhJdNFKyxnwweNq75A@mail.gmail.com> (Namjae Jeon's message of "Tue, 21 Aug 2012 14:19:46 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
> And.. Hi Ogawa.
> I checked other filesystem about unlink - inode issue. but I found
> Ext4 have same issue.
> Although other filesysm is having this issue, Can we think It could be
> only FAT issue ?
(I assume this issue == orphaned inode issue).
ext* doesn't have this issue. If ext* made orphaned inode, ext* doesn't
delete inode from inode table until calling iput() from last referencer.
In FAT case, FAT inode is embedded into dir entry. So, if unlinked inode
(then orphaned inode is detached (fat_detach())), FAT deletes inode (dir
entry) from dir.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-08-21 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 9:41 [PATCH 0/4] fat: fix ESTALE errors Namjae Jeon
2012-08-18 13:25 ` Al Viro
2012-08-18 14:09 ` OGAWA Hirofumi
2012-08-20 4:19 ` Namjae Jeon
2012-08-20 20:52 ` J. Bruce Fields
2012-08-21 5:19 ` Namjae Jeon
2012-08-21 6:41 ` OGAWA Hirofumi [this message]
2012-08-21 10:58 ` Namjae Jeon
2012-08-21 21:11 ` Bastien ROUCARIES
2012-08-22 6:14 ` OGAWA Hirofumi
2012-08-22 6:17 ` OGAWA Hirofumi
2012-08-21 13:20 ` Steven J. Magnani
2012-08-21 18:02 ` Ravishankar
2012-08-20 4:21 ` Namjae Jeon
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=874nnwiw67.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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