On 2015-11-01 09:33, Ken Long wrote:
> I get a similar read-only status when I try to remove the drive from the
> array..
>
> Too bad the utility's function can not be slowed down.. to avoid
> triggering this error... ?
>
Actually, there are a couple of ways you could do this. The most
I have a file system of four 5TB drives. Well, one drive is 8TB with a
5TB partition.. the rest are 5TB drives. I created the initial btrfs
file system on on drive. rsync'd data to it. added another drive.
rsync'd data. added a third drive, rsync'd data. Added a four drive,
trying to balance. The
On Sun, Nov 01, 2015 at 06:24:53AM -0500, Ken Long wrote:
> I have a file system of four 5TB drives. Well, one drive is 8TB with a
> 5TB partition.. the rest are 5TB drives. I created the initial btrfs
> file system on on drive. rsync'd data to it. added another drive.
> rsync'd data. added a
I get a similar read-only status when I try to remove the drive from the array..
Too bad the utility's function can not be slowed down.. to avoid
triggering this error... ?
I had some success putting data *onto* the drive by croning sync every
two seconds in a different terminal.
Doesn't seem
On Sun, 1 Nov 2015 06:24:53 -0500
Ken Long wrote:
> Well, one drive is 8TB with a 5TB partition.
Is this by any chance a Seagate "SMR" drive? From what I remember seeing on
the list, those do not work well with Btrfs currently, with symptoms very
similar to what you're
Yes, the one drive is that Seagate 8TB drive..
Smart tools doesn't show anything outrageous or obvious in hardware.
Is there any other info I can provide to isolate, troubleshoot further?
I'm not sure how to correlate the dmesg message to a specific drive,
SATA cable etc..
On Sun, Nov 1,
On Sun, 1 Nov 2015 09:07:08 -0500
Ken Long wrote:
> Yes, the one drive is that Seagate 8TB drive..
>
> Smart tools doesn't show anything outrageous or obvious in hardware.
>
> Is there any other info I can provide to isolate, troubleshoot further?
>
> I'm not sure how