Btrfs of have I come
across a bug of some sort?
On Sat, Nov 14, 2015 at 12:43 PM, audio muze wrote:
> I'm looking to make a "production copy" of my music and video library
> for use in our media server. It is not my intent to create any form
> of RAID array, but rather to t
I'm looking to make a "production copy" of my music and video library
for use in our media server. It is not my intent to create any form
of RAID array, but rather to treat each drive independently where
filesystem is concerned and then to create a single view of the drives
using mhddfs. As the d
I've looked into snap-raid and it seems well suited to my needs as
most of the data is static. I'm planning on using it in conjunction
with mhddfs so all drives are seen as a single storage pool. Is there
then any benefit in using Btrfs as the underlying filesystem on each
of the drives?
--
To uns
Thanks Roman, but I don't have the appetite to use mdadm and have the
array take forever to build or get yet another set of risks to
ultimately migrate from mdadm to btrfs when raid6 is stable. It seems
to me that the simplest option at present is probably to use each disk
separately, formatted bt
Thanks Chris
I should've browsed recent threads, my apologies. Terribly
frustrating though that the issues you refer to aren't documented in
the btrfs wiki. Reading the wiki one is lead to believe that the only
real issue is the write hole that can occur as a result of a power
loss. There I was
Hi
I've 6 x 3TB SATA drives available with a view to consolidating long
term storage to a single raid array intended to be operational more or
less 24/7. I've done this a few times too many and run into the
inevitable issues like waiting days to expand raid arrays whilst
running the risk of disk
