On Sun, Apr 22, 2012 at 11:03:06PM -0400, Jeremy Atkins wrote: > Back story: > I started my pool with a 200gb partition at the end of my drive (sdc5) > , until I was able to clear out the data at the beginning of my drive. > When I was ready, I ran `btrfs dev add /dev/sdc4 /` then `btrfs dev > del /dev/sdc5 /`, > > $ sudo btrfs fi resize max / > Resize '/' of 'max' > ERROR: unable to resize '/' - Invalid argument > > in dmesg i see: > [ 72.729685] btrfs: resizer unable to find device 1 > > $ sudo btrfs fi df / > Data: total=34.00GB, used=17.79GB > System, DUP: total=64.00MB, used=20.00KB > Metadata, DUP: total=33.50GB, used=394.93MB > > $ sudo btrfs fi sh > Label: none uuid: b0ad55e2-09e0-4658-8cab-d2e11ba03753 > Total devices 1 FS bytes used 17.18GB > devid 2 size 1.62TB used 101.12GB path /dev/sdc4 > > > $ uname -r > 3.3.2-1.fc16.x86_64 > > btrfs-progs version is current git master ( commit 1957076 ) > > After writing this email, and searching around the wiki some, I > discovered the command to resize specific devids, > > [antrat@tbox ~]$ sudo btrfs fi resize 2:max / > Resize '/' of '2:max' > > and in dmesg: > [ 1661.933884] btrfs: resizing devid 2 > [ 1661.933895] btrfs: new size for /dev/sdc4 is 1995564908544 Hrm, if we're using filesystem resize max we should probably just max out all the devices and not require one specific device, what do you think Ilya? Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
