On 02/05/2014 01:34 AM, Remco Hosman - Yerf-it.com wrote:
How can i tell?
Label: data uuid: a8626d67-4684-4b23-99b3-8d5fa8e7fd69
Total devices 5 FS bytes used 820.00KiB
devid2 size 1.82TiB used 1.00GiB path /dev/sdb2
devid3 size 1.82TiB used 1.00GiB path /dev/sdf2
devid5 size 2.73T
How can i tell?
Label: data uuid: a8626d67-4684-4b23-99b3-8d5fa8e7fd69
Total devices 5 FS bytes used 820.00KiB
devid2 size 1.82TiB used 1.00GiB path /dev/sdb2
devid3 size 1.82TiB used 1.00GiB path /dev/sdf2
devid5 size 2.73TiB used 3.00GiB path /dev/sdd
On 02/03/2014 03:51 PM, Remco Hosman - Yerf-it.com wrote:
FIrst, a bit of history of the filesystem:
used to be 6 disks, now 5. partially raid1 / raid10. been migrating back and
forth a few times.
As some point, a balance would not complete and would end with 164 ENOSPC’ses,
while there was pl
to reply to my own thread:
i managed to empty the filesystem, but it still segfaults in the same way when
i try to balance the last few blocks. a `btrfs bal start -dusage=0 /mountpoint`
finishes, but leaves a few blocks allocated. when i skip the usage=0, it
segfaults.
What can i do to provide
Remco Hosman - Yerf-it.com posted on Mon, 03 Feb 2014 21:51:26 +0100 as
excerpted:
> Anything i can do to resolve / debug the issue?
I see from the trace you're running kernel 3.13.0. (FWIW 3.13.1 is out,
but there weren't any btrfs commits therein, as they weren't upstream in
3.14-pre yet at
FIrst, a bit of history of the filesystem:
used to be 6 disks, now 5. partially raid1 / raid10. been migrating back and
forth a few times.
As some point, a balance would not complete and would end with 164 ENOSPC’ses,
while there was plenty of unallocated space on each disk.
i scanned for extend
