Hi,
On 05/08/2012 10:56 PM, Roman Mamedov wrote:
Regarding btrfs, AFAIK even "btrfs -d single" suggested above works not "per
file", but per allocation extent, so in case of one disk failure you will lose
random *parts* (extents) of random files, which in effect could mean no file
in your whole file system will remain undamaged.
Maybe we should evaluate the possiblility of such a "one file gets on
one disk" feature.
Helmut Hullen has the use case: Many disks, totally non-critical but
nice-to-have data. If one disk dies, some *files* should lost, not some
*random parts of all files*.
This could be accomplished by some userspace-tool that moves stuff
around, combined with "file pinning"-support, that lets the user make
sure a specific file is on a specific disk.
Cheers
Kaspar
--
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
