Hi,
Having done this numerous times over the years I proceeded to move our data
to new storage array, first time on a new os version though.
Goes always like this,
* attach array, create LUNS, create multipath conf etc...
* umount old filesystem, mount new filesystems, mount old filesys to temp
lo
14.06.2017 16:58, Andre Maasikas пишет:
> systemd: Unit xx.mount is bound to inactive unit dev-mapper-xx.device.
> Stopping, too.
> systemd: Unmounting /mountpoint...
> kernel: XFS (dm-22): Unmounting Filesystem
> systemd: Unmounted /mountpoint.
> systemd: Unit xxx.mount entered failed state.
>
>
On Thu, 15 Jun 2017, Andrei Borzenkov wrote:
14.06.2017 16:58, Andre Maasikas пишет:
systemd: Unit xx.mount is bound to inactive unit dev-mapper-xx.device.
Stopping, too.
systemd: Unmounting /mountpoint...
kernel: XFS (dm-22): Unmounting Filesystem
systemd: Unmounted /mountpoint.
systemd: Unit x
I'm pretty it should only be necessary to call daemon-reload before using
systemctl. It warns if any source files (unit files, dropins and
anything mentioned by SourcePath= in a unit) have been updated since
the last reload. The fstab generator should be using SourcePath=.
Would it be theo
On Thu, 15 Jun 2017, Jérémy Rosen wrote:
I'm pretty it should only be necessary to call daemon-reload before using
systemctl. It warns if any source files (unit files, dropins and anything
mentioned by SourcePath= in a unit) have been updated since the last
reload. The fstab generator shoul
On Thu, Jun 15, 2017 at 10:39 AM, Jérémy Rosen
wrote:
>
> I'm pretty it should only be necessary to call daemon-reload before using
> systemctl. It warns if any source files (unit files, dropins and anything
> mentioned by SourcePath= in a unit) have been updated since the last
> reload. The fsta
14.06.2017 16:58, Andre Maasikas пишет:
>
> OK, let's mount manually,
>
> mount /dev/mapper/newdev /mountpoint
>> no errors, seems ok
> still df, mount and /proc/mounts show nothing...
> WTF moment
>
Well, opposite case (it is mounted when it should not) is equally true
https://github.com/syst
This reminds me of a bug (misfeature) that *I think* was fixed in recent
releases...
Mount points are bound to the corresponding .device so that they'd get
cleaned up when the device disappears, but the way it was implemented meant
they'd also get immediately unmounted if the device wasn't there i
