lkml.org 
[lkml]   [2012]   [Sep]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS.
From
2012/9/17 OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>:
> 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.
No, problem. Thanks~
>
> Thanks.
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>


\
 
 \ /
  Last update: 2012-09-17 17:01    [W:0.037 / U:1.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site