On 10/25/2014 05:57 PM, Michael Hamilton wrote:
I had the same problem when trying to merge partitions and grow a filesystem. It was really quite scary to see the /home remounted while in the middle of re-partitioning and re-sizing (I had to spend some time diffing the result against a backup to make sure it was OK).
Unless you are running A FS such as ReiserFs which supports resizing while mounted, then trying to resize while in multi-user mode is going to be risky.
I don't really have an answer - I somehow muddled through. But from reading man systemd.mount, it seems temporarily changing the fstab entry to noauto might help. I suspect it would take a reboot or some kind of systemd command to make such a change stick.
It strikes me that if the /etc/fstab says that a FS should be mounted that if systemd is trying to maintain that definition of the system state this behaviour is predictable; that changing the state definition to noauto makes sense of you don't want the system automatically mounted. Think 'state' rather than 'command sequence'.
I'm not that happy to see umount fail to behave it the old expected manner - perhaps it is no longer the umount we expect it to be and should be renamed.
I think there is a misunderstanding here. In effect there is an 'automounter' running. The fsatab tells the 'automounter' what _should_ be mounted and it tried to maintain that state. Perhaps the misunderstanding is that, as I keep saying, systemd takes a DECLARATIVE approach rather than a PROCEDURAL approach.
But it would be good to get some pointers in how to do admin in a systemd environment. Does anyone know of a HOWTO for doing standard system maintenance tasks, such as re-sizing filesystems, in a systemd environment?
I think you need to step back and look at how to prepare the system for resizing first. The ability to dynamically resize without the unmount/remount cycle is one of the reasons I chose to use ReiserFS. YMMV. As such this whole issue does not arise. The OP clearly was using LVM. In the case I've had to convert from non-ReiserFS to ReiserFS I've created the new partition, created the ResiserFS then rsynced across and altered to fstab and done the umount (the long, literal way, not using fstab) and then 'mount -a'. That worked before systemd and works after systemd. Once the ResierFs was in place adjusting its size (and that of the LVM partition to match) was quite independent of systemd vs sysvinit. I think you will find that there are other file systems that permit dynamic resizing, or at lest dynamic increase in size. As far as I'm concerned the idea of sysadmin by defining the state of the machine and having tools that keep it in that state makes a lot of sense. But then, as I've said before, I have the hardware background in state machines so this is not strange to me. I can see how it is, how all the state definition nature of systemd, is strange to people who are used to the procedural -- "do this now do this not do this" ... Sequencing -- approach. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org