lkml.org 
[lkml]   [2012]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH v2 4/5] fat: eliminate orphaned inode number allocation
From
2012/9/5, OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>:
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
>
>> Namjae Jeon <linkinjeon@gmail.com> writes:
>>
>>> From: Namjae Jeon <namjae.jeon@samsung.com>
>>>
>>> Maintain a list of inode(i_pos) numbers of orphaned inodes (i.e the
>>> inodes that have been unlinked but still having open file
>>> descriptors).At file/directory creation time, skip using such i_pos
>>> values.Removal of the i_pos from the list is done during inode eviction.
>>
>> What happens if the directory (has busy entries) was completely removed?
Hi OGAWA.
There are 2 cases:
1. The cluster can be used as a data cluster of a file - In which case
we can write
normally into it.
2. The cluster can be allocated to a new directory. In this case, the busy i_pos
locations can not be used to create new entries until the correspnding
inodes are
evicted.

>>
>>
>> And Al's point is important for NFS too. If you want stable ino for NFS,
>> you never can't change it.
Yes, It is also important, I will explain throughout reply in Al's mail.
Thanks!
>
> s/never can't/never can/
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
>


\
 
 \ /
  Last update: 2012-09-05 16:43    [W:0.088 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site