* [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS.
@ 2012-09-16 12:21 Namjae Jeon
2012-09-17 13:09 ` OGAWA Hirofumi
0 siblings, 1 reply; 3+ messages in thread
From: Namjae Jeon @ 2012-09-16 12:21 UTC (permalink / raw)
To: hirofumi, akpm; +Cc: bfields, viro, linux-kernel, Namjae Jeon, Namjae Jeon
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
--
1.7.9.5
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS.
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
2012-09-17 14:14 ` Namjae Jeon
0 siblings, 1 reply; 3+ messages in thread
From: OGAWA Hirofumi @ 2012-09-17 13:09 UTC (permalink / raw)
To: Namjae Jeon; +Cc: akpm, bfields, viro, linux-kernel, Namjae Jeon
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v3 0/5] fat: make persistent inode numbers and stablize for NFS.
2012-09-17 13:09 ` OGAWA Hirofumi
@ 2012-09-17 14:14 ` Namjae Jeon
0 siblings, 0 replies; 3+ messages in thread
From: Namjae Jeon @ 2012-09-17 14:14 UTC (permalink / raw)
To: OGAWA Hirofumi; +Cc: akpm, bfields, viro, linux-kernel, Namjae Jeon
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-09-17 14:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2012-09-17 14:14 ` Namjae Jeon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox