On 2016-07-20 15:58, Chris Murphy wrote:
On Sun, Jul 17, 2016 at 3:08 AM, Hendrik Friedel <hend...@friedels.name> wrote:
Well, btrfs does write data very different to many other file systems. On
every write the file is copied to another place, even if just one bit is
changed. That's special and I am wondering whether that could cause
problems.
It depends on the application. In practice, the program most
responsible for writing the file often does a faux-COW by writing a
whole new (temporary) file somewhere, when that operation completes,
it then deletes the original, and move+renames the temporary one into
place where the original one, doing fsync in between each of those
operations. I think some of this is done via VFS also. It's all much
more metadata centric than what Btrfs would do on its own.
I'm pretty certain that the VFS itself does not do replace by rename
type stuff. BTRFS by nature technically does though, it's the same idea
as a COW update, just at a higher level, so we're technically doing the
same thing for every single block that changes. The only issue I can
think of in this context with a replace by rename is that you end up
hitting the metadata trees twice.
I'd expect the write pattern of Btrfs to be similar to f2fs, with
respect to sequentiality of new writes.
Not necessarily, F2FS is log structured, and while not as much like
traditional log structured filesystems, it still has a similar long-term
write pattern to stuff like NILFS2 or LFS. I've not done as much with
F2FS specifically, but I can say based on comparison to other log
structured filesystems that outside of WORM write patterns in userspace,
BTRFS does not have a similar write pattern to a log structured
filesystem. We try to pack stuff into existing allocations pretty
aggressively, so we end up with most of our writes condensed in a small
area of the disk. The only cases I've seen where we get long sequential
writes are when writing out single files one by one, without having
anything else running at the same time on the FS.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
