Re: [PATCH v3 0/5] fat: make persistent inode numbers and stablizefor NFS.

[Namjae Jeon]

2012/9/17 OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx>:
> Namjae Jeon <linkinjeon@xxxxxxxxx> writes:
>
>> From: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
>>
>> 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@xxxxxxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/