Messages in this thread | | | From | OGAWA Hirofumi <> | Subject | Re: [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS. | Date | Mon, 17 Sep 2012 22:09:33 +0900 |
| |
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>
| |