On Thu, Dec 31, 2015 at 5:27 PM, Chris Murphy wrote:
> On Thu, Dec 31, 2015 at 6:09 PM, ronnie sahlberg
> wrote:
>> Here is a kludge I hacked up.
>> Someone that cares could clean this up and start building a proper
>> test suite or something.
>>
>> This test script creates a 3 disk raid1 filesys
On Thu, Dec 31, 2015 at 5:27 PM, Chris Murphy wrote:
> On Thu, Dec 31, 2015 at 6:09 PM, ronnie sahlberg
> wrote:
>> Here is a kludge I hacked up.
>> Someone that cares could clean this up and start building a proper
>> test suite or something.
>>
>> This test script creates a 3 disk raid1 filesys
On Thu, Dec 31, 2015 at 6:09 PM, ronnie sahlberg
wrote:
> Here is a kludge I hacked up.
> Someone that cares could clean this up and start building a proper
> test suite or something.
>
> This test script creates a 3 disk raid1 filesystem and very slowly
> writes a large file onto the filesystem w
Here is a kludge I hacked up.
Someone that cares could clean this up and start building a proper
test suite or something.
This test script creates a 3 disk raid1 filesystem and very slowly
writes a large file onto the filesystem while, one by one each disk is
disconnected then reconnected in a loo
On Thu, Dec 31, 2015 at 12:11 PM, Chris Murphy wrote:
> This is a torture test, no data is at risk.
>
> Two devices, btrfs raid1 with some stuff on them.
> Copy from that array, elsewhere.
> During copy, yank the active device.
>
> dmesg shows many of these:
>
> [ 7179.373245] BTRFS error (device
On Thu, Dec 31, 2015 at 1:24 PM, Hugo Mills wrote:
> On Thu, Dec 31, 2015 at 01:11:25PM -0700, Chris Murphy wrote:
>> This is a torture test, no data is at risk.
>>
>> Two devices, btrfs raid1 with some stuff on them.
>> Copy from that array, elsewhere.
>> During copy, yank the active device.
>>
>
On Thu, Dec 31, 2015 at 01:11:25PM -0700, Chris Murphy wrote:
> This is a torture test, no data is at risk.
>
> Two devices, btrfs raid1 with some stuff on them.
> Copy from that array, elsewhere.
> During copy, yank the active device.
>
> dmesg shows many of these:
>
> [ 7179.373245] BTRFS erro
On Thu, Dec 31, 2015 at 1:11 PM, Chris Murphy wrote:
> Also, is there a command to make a block device go away?
Maybe?
echo 1 > /sys/block/device-name/device/delete
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...
This is a torture test, no data is at risk.
Two devices, btrfs raid1 with some stuff on them.
Copy from that array, elsewhere.
During copy, yank the active device.
dmesg shows many of these:
[ 7179.373245] BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr
652123, rd 697237, flush 0, corrupt 0,