On 05/28/2010 01:14 PM, H. Peter Anvin wrote:
Hi all, I have looked a bit at e4defrag, and it does not appear to prevent the relocation of files marked immutable. This is a problem for boot loaders, which may need to have a block pointer to a specific file in order to bootstrap themselves. Would it be possible to either: a) prevent e4defrag and/or EXT4_IOC_MOVE_EXT from relocating an immutable file, or b) add a new attribute with the above property (in case there is legitimate need to move around immutable files)?
We (ocfs2) are looking to add a new attribute to denote files that have a fixed allocation on disk. But at the same time, allow writes that do not change the allocation on disk. No truncating, extending, filling holes, etc. We were thinking of calling it "Static" files. No meddling with the allocation will allow ocfs2 to not have any cluster locks associated with that inode. And no cluster locks means no need to pause ios during node recovery. This could be of interest to vm users who are willing have fully allocated images for no stoppage during cluster reconfiguration. Thanks Sunil -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
