On Tue, Jan 22, 2013 at 07:29:47PM +0400, Pavel Vasilyev wrote: > > In "single" data mode, btrfs makes no special attempt to keep files > > together on the same disk, but if a file is written linearly and never > > modified there's a chance it might happen. (Each modification will COW > > the file, putting the modified portion on a random disk.) > > > > As a result, yes, you may lose a substantial number - even most - of > > your files if one disk dies while in single data mode. > > So, on highly fragmented fs reliability in single data mode is near to raid0? > Rhetorical question, actually.
Correct. The difference against 'single' is that it does not spread the data by default, depends on actual data layout and is unpredictable in most cases. > > The failure mode you are describing would be interesting, and people > > talk about it now and then, but there is no current support in btrfs for > > it. > > Is there any plans to support it? I've added a project to the wiki, if that counts :) david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
