On Mon, Nov 5, 2018 at 6:27 AM, Austin S. Hemmelgarn
wrote:
> On 11/4/2018 11:44 AM, waxhead wrote:
>>
>> Sterling Windmill wrote:
>>>
>>> Out of curiosity, what led to you choosing RAID1 for data but RAID10
>>> for metadata?
>>>
>>> I've flip flipped between these two modes myself after finding
On 11/4/2018 11:44 AM, waxhead wrote:
Sterling Windmill wrote:
Out of curiosity, what led to you choosing RAID1 for data but RAID10
for metadata?
I've flip flipped between these two modes myself after finding out
that BTRFS RAID10 doesn't work how I would've expected.
Wondering what made you
Sterling Windmill wrote:
Out of curiosity, what led to you choosing RAID1 for data but RAID10
for metadata?
I've flip flipped between these two modes myself after finding out
that BTRFS RAID10 doesn't work how I would've expected.
Wondering what made you choose your configuration.
Thanks!
Out of curiosity, what led to you choosing RAID1 for data but RAID10
for metadata?
I've flip flipped between these two modes myself after finding out
that BTRFS RAID10 doesn't work how I would've expected.
Wondering what made you choose your configuration.
Thanks!
On Fri, Nov 2, 2018 at 3:55
Duncan wrote:
waxhead posted on Fri, 02 Nov 2018 20:54:40 +0100 as excerpted:
Note that I tend to interpret the btrfs de st / output as if the error
was NOT fixed even if (seems clearly that) it was, so I think the output
is a bit misleading... just saying...
See the btrfs-device manpage,
waxhead posted on Fri, 02 Nov 2018 20:54:40 +0100 as excerpted:
> Note that I tend to interpret the btrfs de st / output as if the error
> was NOT fixed even if (seems clearly that) it was, so I think the output
> is a bit misleading... just saying...
See the btrfs-device manpage, stats
Hi,
my main computer runs on a 7x SSD BTRFS as rootfs with
data:RAID1 and metadata:RAID10.
One SSD is probably about to fail, and it seems that BTRFS fixed it
nicely (thanks everyone!)
I decided to just post the ugly details in case someone just wants to
have a look. Note that I tend to
