btrfs replace with bigger disk
I am replacing a set of 4 x 3TB disks with 4 x 6TB disks in a server that holds backups. I did btrfs replace on one disk, and that has completed but is still showing the original size: Total devices 4 FS bytes used 5.21TiB devid 1 size 2.73TiB used 2.73TiB path /dev/sda3 devid 2 size 2.73TiB used 2.73TiB path /dev/sdb3 devid 3 size 2.73TiB used 2.73TiB path /dev/sdc3 devid 4 size 2.73TiB used 2.73TiB path /dev/sde3 /dev/sde3 replaced /dev/sdd3, and the partition itself is definitely the correct size: major minor #blocks name 8 19 2929216967 sdb3 8 67 5859472967 sde3 8 51 2929216967 sdd3 8 35 2929216967 sdc3 8 3 2929216967 sda3 I've tried running a btrfs resize but it hasn't changed anything. Google just keeps giving me the same pages telling me about how replace works and why btrfs is awesome, but nothing that will actually fix the problem so far... Does anyone know how I might fix this? Thanks James
On Wed, 16 Sep 2015 08:56:04 PM James Harper wrote:
I've tried running a btrfs resize but it hasn't changed anything.
What was the exact resize command you used? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On Wed, 16 Sep 2015 08:56:04 PM James Harper wrote:
I've tried running a btrfs resize but it hasn't changed anything.
What was the exact resize command you used?
The docs say: # btrfs filesystem resize amount /mount-point So I said: btrfs filesystem resize max / and Linux says: Resize '/' of 'max' Which doesn't really make any sense... If I say '+1G' instead of 'max' it says there is no space on the devices, which makes more sense. So I need to tell btrfs that the device is bigger first I guess. Thanks James
On Thu, 17 Sep 2015, James Harper <james@ejbdigital.com.au> wrote:
# btrfs filesystem resize amount /mount-point
So I said:
btrfs filesystem resize max /
and Linux says:
Resize '/' of 'max'
Which doesn't really make any sense...
The docs for the version I have say that you can specify the devid and if you don't it will default to 1. Maybe the device you want to resize is not devid 1. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On Wed, 16 Sep 2015 08:56:04 PM James Harper wrote:
I've tried running a btrfs resize but it hasn't changed anything.
What was the exact resize command you used?
The docs say:
# btrfs filesystem resize amount /mount-point
So I said:
btrfs filesystem resize max /
and Linux says:
Resize '/' of 'max'
Which doesn't really make any sense...
Sorted. The special sauce was to specify the device id, so: # btrfs filesystem show / Label: none uuid: 3826b465-0224-41df-9e1e-182d5eb68904 Total devices 4 FS bytes used 5.15TiB devid 1 size 2.73TiB used 2.73TiB path /dev/sda3 devid 2 size 2.73TiB used 2.73TiB path /dev/sdb3 devid 3 size 2.73TiB used 2.73TiB path /dev/sdc3 devid 4 size 2.73TiB used 2.73TiB path /dev/sde3 # btrfs filesystem resize 4:max / Resize '/' of '4:max' # btrfs filesystem show / Label: none uuid: 3826b465-0224-41df-9e1e-182d5eb68904 Total devices 4 FS bytes used 5.15TiB devid 1 size 2.73TiB used 2.73TiB path /dev/sda3 devid 2 size 2.73TiB used 2.73TiB path /dev/sdb3 devid 3 size 2.73TiB used 2.73TiB path /dev/sdc3 devid 4 size 5.46TiB used 2.73TiB path /dev/sde3 w00t! James
It's almost worth filing a bugreport for that. Surely in the case of multiple backing devices, if you don't specify which one, the default should be *all*, not the *first*. I bet every single person who ever resizes a multiple-backing-device btrfs will have hit this issue. On Sat, 19 Sep 2015 at 18:43 James Harper <james@ejbdigital.com.au> wrote:
On Wed, 16 Sep 2015 08:56:04 PM James Harper wrote:
I've tried running a btrfs resize but it hasn't changed anything.
What was the exact resize command you used?
The docs say:
# btrfs filesystem resize amount /mount-point
So I said:
btrfs filesystem resize max /
and Linux says:
Resize '/' of 'max'
Which doesn't really make any sense...
Sorted. The special sauce was to specify the device id, so:
# btrfs filesystem show / Label: none uuid: 3826b465-0224-41df-9e1e-182d5eb68904 Total devices 4 FS bytes used 5.15TiB devid 1 size 2.73TiB used 2.73TiB path /dev/sda3 devid 2 size 2.73TiB used 2.73TiB path /dev/sdb3 devid 3 size 2.73TiB used 2.73TiB path /dev/sdc3 devid 4 size 2.73TiB used 2.73TiB path /dev/sde3
# btrfs filesystem resize 4:max / Resize '/' of '4:max'
# btrfs filesystem show / Label: none uuid: 3826b465-0224-41df-9e1e-182d5eb68904 Total devices 4 FS bytes used 5.15TiB devid 1 size 2.73TiB used 2.73TiB path /dev/sda3 devid 2 size 2.73TiB used 2.73TiB path /dev/sdb3 devid 3 size 2.73TiB used 2.73TiB path /dev/sdc3 devid 4 size 5.46TiB used 2.73TiB path /dev/sde3
w00t!
James _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
On Wed, 16 Sep 2015 10:56:04 AM James Harper wrote:
I've tried running a btrfs resize but it hasn't changed anything.
What do these say? uname -r btrfs --version cheers, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
On Wed, 16 Sep 2015 10:56:04 AM James Harper wrote:
I've tried running a btrfs resize but it hasn't changed anything.
What do these say?
uname -r
4.1.0-0.bpo.2-amd64 (from Debian jessie-backports)
btrfs --version
Btrfs v3.17 (from Debian jessie)
Just backported 4.1 from Stretch, but no change. James
participants (4)
-
Chris Samuel -
James Harper -
Russell Coker -
Toby Corkindale