linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, bfields@fieldses.org,
	viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
	Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS.
Date: Mon, 17 Sep 2012 22:09:33 +0900	[thread overview]
Message-ID: <87k3vs6bjm.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1347798099-2592-1-git-send-email-linkinjeon@gmail.com> (Namjae Jeon's message of "Sun, 16 Sep 2012 08:21:39 -0400")

Namjae Jeon <linkinjeon@gmail.com> writes:

> 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 numbers.
>
> 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.
>
> We reached the conclusion support stable inode's read-only export first after
> discussing with OGAWA and Bruce.
> And will make it writable with some operation(unlink and rename) limitation
> next time.
>
> Namjae Jeon (4)
>  fat: modify nfs mount option
>  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

Sorry for late, I will review at next weekend.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2012-09-17 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-16 12:21 [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS Namjae Jeon
2012-09-17 13:09 ` OGAWA Hirofumi [this message]
2012-09-17 14:14   ` 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=87k3vs6bjm.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;
as well as URLs for NNTP newsgroup(s).