I was wondering about adding fallocate() to cp,
where one of the benefits would be immediate indication of ENOSPC.
I'm now wondering though might fallocate() fail to allocate an
extent with ENOSPC, but there could be fragmented space available to write()?
If the above was true, then perhaps we could assume that
any file system returning ENOSPC from fallocate(),
might provide accurate fstatvfs().f_b{free,avail} values
for a subsequent check, though needing to do that seems hacky.
cheers,
Pádraig.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
