Skip to contentSkip to conversation

fat: make persistent inode numbers and stablize for NFS.

PATCH In review Namjae Jeon 2 participants 3 messages Sep 16, 2012 – Sep 17, 2012

lore
Share & tools
lore
#0 lore raw

v3 cover fat: make persistent inode numbers and stablize for NFS.

From: Namjae Jeon <[email protected]>

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

Signature · 1 line
1.7.9.5
#1 lore raw
Quoted 19 lines · Namjae Jeon

From: Namjae Jeon <[email protected]>

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.

Quoted 6 lines

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.

Signature · 1 line
OGAWA Hirofumi <[email protected]>
#2 lore raw

2012/9/17 OGAWA Hirofumi <[email protected]>:

Quoted 21 lines
Quoted 19 lines · Namjae Jeon

From: Namjae Jeon <[email protected]>

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.

Quoted 8 lines
Quoted 6 lines

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~

Quoted 4 lines

Thanks.
--
OGAWA Hirofumi <[email protected]>