Re: Simple btrfs use case

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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.

> 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?

> (One thing to note: small files are often stored in the metadata area
> instead of data area, which would be raid1 in your setup. As a result,
> those small files are more likely to be recoverable).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux