* [PATCH v2 0/5] fat: make persistent inode numbers and stablize for NFS.
@ 2012-09-04 15:57 Namjae Jeon
0 siblings, 0 replies; only message in thread
From: Namjae Jeon @ 2012-09-04 15:57 UTC (permalink / raw)
To: hirofumi, akpm, bfields, viro; +Cc: linux-kernel, Namjae Jeon, Namjae Jeon
From: Namjae Jeon <email@example.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.
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
Documentation: update nfs option in filesystem/vfat.txt
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-09-04 15:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-04 15:57 [PATCH v2 0/5] fat: make persistent inode numbers and stablize for NFS Namjae Jeon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).