On Tue, Feb 23, 2016 at 01:59:11PM -0800, Marc MERLIN wrote:
> I have a freshly created md5 array, with drives that I specifically
> scanned one by one block by block, and for good measure, I also scanned
> the entire software raid with a check command which took 3 days to run.
>
> Everything
Marc MERLIN posted on Tue, 23 Feb 2016 16:19:44 -0800 as excerpted:
> Cabling is indeed a likely culprit, I'm just surprised that if it's the
> case, the sata layer is showing me nothing (I'm doing tail -f
> /var/log/kern.log and usually I'd see sata or PMP errors there)
That /is/ surprising.
On Tue, Feb 23, 2016 at 11:22:47PM +, Duncan wrote:
> Forgot to mention, tho you're probably already considering it, if this is
> the same raid5-backed btrfs you were complaining about being slow in the
> other thread,
No, that's another one :)
This one was remade from scratch after the
Duncan posted on Tue, 23 Feb 2016 23:17:06 + as excerpted:
> Marc MERLIN posted on Tue, 23 Feb 2016 13:59:11 -0800 as excerpted:
>
>> I have a freshly created md5 array, with drives that I specifically
>> scanned one by one block by block, and for good measure, I also scanned
>> the entire
Marc MERLIN posted on Tue, 23 Feb 2016 13:59:11 -0800 as excerpted:
> I have a freshly created md5 array, with drives that I specifically
> scanned one by one block by block, and for good measure, I also scanned
> the entire software raid with a check command which took 3 days to run.
>
>
I have a freshly created md5 array, with drives that I specifically
scanned one by one block by block, and for good measure, I also scanned
the entire software raid with a check command which took 3 days to run.
Everything passed.
Then, I made a bcache of that device, an ssd that seems to work
