From: Namjae Jeon <linkinjeon@gmail.com>
To: hirofumi@mail.parknet.co.jp, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Namjae Jeon <linkinjeon@gmail.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: [PATCH 0/4] fat: fix ESTALE errors
Date: Sat, 18 Aug 2012 05:41:39 -0400 [thread overview]
Message-ID: <1345282899-7534-1-git-send-email-linkinjeon@gmail.com> (raw)
From: Namjae Jeon <namjae.jeon@samsung.com>
This patch-set eliminates the client side ESTALE errors when
a FAT partition exported over NFS has its dentries evicted
from the cache.
One of the reasons for this error is lack of permanent inode
numbers on FAT which makes it difficult to construct persistent
file handles.This can be overcome by using the on-disk location
of the directory entries (i_pos) as the inode number.
Once the i_pos is available, it is only a matter of reading the
directory entries from the disk clusters to locate the matching
entry and rebuild the corresponding inode.
Namjae Jeon (4):
fat: allocate persistent inode numbers
fat (exportfs): rebuild inode if ilookup() fails
fat (exportfs): rebuild directory-inode if fat_dget() fails
Documentation: update nfs option in filesystem/vfat.txt
---
next reply other threads:[~2012-08-18 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 9:41 Namjae Jeon [this message]
2012-08-18 13:25 ` [PATCH 0/4] fat: fix ESTALE errors 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
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=1345282899-7534-1-git-send-email-linkinjeon@gmail.com \
--to=linkinjeon@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
/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