User: Password:
|
|
Subscribe / Log in / New account

Allocating uninitialized file blocks

Allocating uninitialized file blocks

Posted Apr 19, 2012 15:21 UTC (Thu) by sandeen (subscriber, #42852)
Parent article: Allocating uninitialized file blocks

As the thread wore on, numbers were posted which show XFS has no serious performance degradation under the same workload. At this point, blowing a security hole in ext4 and promoting the flag to the VFS level seems incredibly premature.

I'd look into just what is making ext4 slow here but so far I can't reproduce a slowdown anything like what the patch submitter has seen...

-Eric


(Log in to post comments)

Allocating uninitialized file blocks

Posted Apr 23, 2012 1:21 UTC (Mon) by szaka (subscriber, #12740) [Link]

The flag (with a better name) could be helpful for filesystems which can't fully support uninitialized allocated blocks efficiently. We are supporting several such interoperable filesystems (NTFS, exFAT, FAT) where changing the specification is not possible.

There is real user need despite explaining potential security consequences. Typical usage scenarios are using a large file as a container for an application which tracks free/used blocks itself. Windows supports this feature by SetFileValidData() if extra privilege is granted.

The performance gain can be huge on embedded using low-end storage and SoC. In one of our cases it took 5 days vs 12 minutes to fully setup a large file for use.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds