On Thu, Aug 27, 2015 at 10:35 AM, Mike Aubury <m...@aubit.com> wrote: > Thanks for that. > I found something similar online - using a loop back device and a file > on a usb stick. > I created a 2GB file, and mounted that tried the balance - and once > completed - rebooted.
OK but did you delete the loop device before rebooting? If not, then that's why. You need to reactivate that loop device from the file to mount the fs normally. It's not good enough to just balance. You have to use btrfs dev del on the extra device so the fs moves everything off that soon to be removed device. >>> root@ReadyNAS:~# btrfs fi df /data >>> Data, single: total=6.33TiB, used=5.87TiB >>> System, RAID1: total=32.00MiB, used=768.00KiB >>> System, single: total=4.00MiB, used=0.00B >>> Metadata, RAID1: total=9.00GiB, used=8.98GiB >>> Metadata, DUP: total=3.00GiB, used=2.12GiB I just noticed this, and it's confusing. All data is single copy. Some of the metadata is DUP on *one* device rather than RAID1. So it's entirely possible that some of the DUP metadata, without conversion, ends up on the loop device and if that loop device isn't first deleted before the reboot, then you have a broken file system because that necessary fs metadata isn't available anywhere. The metadata DUP is kinda dangerous in multiple device cases. -- 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
