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 or low, but i'm still getting the same errors. i'll let it run though the night tho, as it doesn't seem to hurt anything other then slowly lock the system up.
on a side note, all the USB drives are either powered or are connected to a powered hub.. thanks again! On Sun, Apr 15, 2018 at 8:52 PM, Chris Murphy <li...@colorremedies.com> wrote: > On Sun, Apr 15, 2018 at 6:30 PM, Chris Murphy <li...@colorremedies.com> 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://github.com/neilbrown/mdadm/pull/32/commits/af1ddca7d5311dfc9ed60a5eb6497db1296f1bec > > Which could bmaybe be adapted from mdadm raid to look for Btrfs > instead, or in addition to. > > -- > Chris Murphy -- -o) /\\ Message void if penguin violated _\_V Don't mess with the penguin -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
