Den 03/05/16 kl. 13:13 skrev Hasse Hagen Johansen: >>> >>> The exact thing I did was having the subvols mounted. Then mounted >> top-level volume on /mbt/temp. And then ran balance to convert to >> raid1.. When finished I umounted /mnt/temp (the top-level) and then my >> 3 subvolumes was unmounted and a cannot mount them at the same >> mountpoints again... No errors and it says that it is not mounted when >> trying to umount them. So it seems they don't get mounted at all and >> without throwing an error >>> >>> I will look into it more thoroughly now that I can at least mount the >> subvols on other mountpoints than the original >> >> Given those symptoms (mount doesn't report errors, but no mount >> happens), I would guess that your problem is with systemd. It has a >> bug where it sometimes unmounts things immediately after you've >> mounted them. >> You were right. Looking more into it (home at my computer and not my phone) I found this in /var/log/syslog: May 3 19:57:23 pris systemd[1]: books.mount: Unit is bound to inactive unit dev-Data\x2dVG-books. device. Stopping, too. May 3 19:57:23 pris systemd[1]: Unmounting /books... May 3 19:57:25 pris systemd[1]: Unmounted /books. May 3 19:57:25 pris systemd[1]: books.mount: Unit entered failed state. So it is indeed systemd...great...seems it is confused because the mountpoints which I have now moved to btrfs was earlier using lvm. I will try telling systemd to forget that old unit Thanks for the help -- 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
