On Sun, Apr 15, 2018 at 10:33 PM, Chris Murphy wrote:
> On Sun, Apr 15, 2018 at 7:45 PM, Alexander Zapatka
> wrote:
>> thanks, Chris. i have given a timeout of 300 to all the drives. they
>> are all USB, all connected to an apollo lake based htpc. then i
>> started the command again... the dme
On Sun, Apr 15, 2018 at 7:45 PM, Alexander Zapatka
wrote:
> thanks, Chris. i have given a timeout of 300 to all the drives. they
> are all USB, all connected to an apollo lake based htpc. then i
> started the command again... the dmesg output is here from a few
> minutes after i started the btr
thanks, Chris. i have given a timeout of 300 to all the drives. they
are all USB, all connected to an apollo lake based htpc. then i
started the command again... the dmesg output is here from a few
minutes after i started the btrfs device remove command.
https://paste.ee/p/H1R0i. no hopes, high
On Sun, Apr 15, 2018 at 6:30 PM, Chris Murphy wrote:
> # echo value > /sys/block/device-name/device/timeout
>
Also note that this is not a persistent setting. It needs to be done
per boot. But before you change it, use cat to find out what the value
is. Default is 30.
I'm seeing this:
https://g
Please keep the list in the cc:
On Sun, Apr 15, 2018 at 5:55 PM, Alexander Zapatka
wrote:
> output:
>
> $ sudo smartctl -l scterc /dev/sdc
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-38-generic] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
On Sun, Apr 15, 2018 at 6:14 AM, Alexander Zapatka
wrote:
> i recently set up a drive pool in single mode on my little media
> server. about a week later SMART started telling me that the drive
> was having issue and there is one bad sector. since the array is far
> from full i decided to remove
