Messages in this thread | | | Date | Wed, 5 Sep 2012 22:37:41 +0900 | Subject | Re: [PATCH v2 4/5] fat: eliminate orphaned inode number allocation | From | Namjae Jeon <> |
| |
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> >
| |