On Mon, Oct 9, 2017 at 1:22 AM, Nick Gilmour <nickefo...@gmail.com> wrote: >> I don't see a 'btrfs filesystem resize' command in your sequence. Did >> you actually resize the file system before you resized the underlying >> (virtual) block device? > > > OK. I guess, this is it. I didn't do any 'btrfs filesystem resize' . The > guides I was following didn't mention something like that. I was assuming > that if it works for other FS like this it should also work for BTRFS.
Literally all other file systems require the fs be resized first when shrinking, before the underlying partition or virtual block device is reduced. There is nothing unique about Btrfs in this respect. Some tools will use fsadm in the sequence to make sure the file system is properly resized. So the question is whether any of the resize tools you did use, expect to use fsadm. And if they do or did, whether and why there wasn't an error if fsadm doesn't support Btrfs before the block device was resized anyway. I don't know offhand if Btrfs is supported by fsadmn, the man page does not list it as one of the supported file systems. > # btrfs filesystem resize -350g /home ? > > Should it be before or after I shrink the .img? When shrinking, the fs resize must happen first. Then the block device can be reduced to match. When growing, the block device is extended, then the fs is resized. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
