Re: [RFC][PATCH] ChunkFS: fs fission for faster fsck

[Amit Gud <gud@ksu.edu>]

Jeff Dike wrote:
> How about this case:
>
> 	Growing file starts in chunk A.
> 	Overflows into chunk B.
> 	Delete file in chunk A.
> 	Growing file overflows chunk B and spots new free space in
> chunk A (and nothing anywhere else)
> 	Overflows into chunk A
> 	Delete file in chunk B.
> 	Overflow into chunk B again.
>
> Maybe this is not realistic, but in the absence of a mechanism to pull
> data back from an overflow chunk, it seems at least a theoretical
> possibility that there could be > 1 continuation inodes per file per
> chunk.

Preventive measures are taken to limit only one continuation inode per 
file per chunk. This can be done easily in the chunk allocation 
algorithm for disk space. Although I'm not quite sure what you mean by 
"Delete file in chunk A". If you are referring to same file thats 
growing, then deletion is not possible, because individual parts of any 
file in any chunk cannot be deleted.


AG
--
May the source be with you.
http://www.cis.ksu.edu/~gud

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/