[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k3vs6bjm.fsf@devron.myhome.or.jp>
Date: Mon, 17 Sep 2012 22:09:33 +0900
From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To: Namjae Jeon <linkinjeon@...il.com>
Cc: akpm@...ux-foundation.org, bfields@...ldses.org,
viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
Namjae Jeon <namjae.jeon@...sung.com>
Subject: Re: [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS.
Namjae Jeon <linkinjeon@...il.com> writes:
> From: Namjae Jeon <namjae.jeon@...sung.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@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists