Dave, > .... because when backed by thinp storage, plumbing user level > fallocate() straight through from the filesystem introduces a > trivial, user level storage DOS vector.... > > i.e. a user can just fallocate a bunch of files and, because the > filesystem can do that instantly, can also run the back end array > out of space almost instantly. Storage admins are going to love > this! In the standards space, the allocation concept was mainly aimed at protecting filesystem internals against out-of-space conditions on devices that dedup identical blocks and where simply zeroing the blocks therefore is ineffective. So far we have mainly been talking about fallocate on block devices. How XFS decides to enforce space allocation policy and potentially leverage this plumbing is entirely up to you. -- Martin K. Petersen Oracle Linux Engineering
