Skip to contentSkip to conversation

fat: make persistent inode numbers and stablize for NFS.

PATCH Superseded Namjae Jeon 1 participant 1 message Sep 4, 2012

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

v2 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.

If process is referring to the file, and the file is unlinked(deleted). Then, the file 'i_pos' is added to the busy list so the the entry is not available for new file creation. when finally inode is evicted the corresponding busy list entries are removed and slots are made available for new entries.

Namjae Jeon (5)
fat: allocate persistent inode numbers
fat (exportfs): rebuild inode if ilookup() fails fat (exportfs): rebuild directory-inode if fat_dget() fails
fat: eliminate-orphaned-inode-number-allocation
Documentation: update nfs option in filesystem/vfat.txt

Signature · 1 line
1.7.9.5