On Wed, Jun 21, 2017 at 03:13:36PM +0100, Sami Kerola wrote:
> On 21 June 2017 at 13:15, Sami Kerola <kerolasa@xxxxxx> wrote:
> > We (Cloudflare) got a strange issue with mount(8) from debian jessie
> > package v2.25.2. Kernel version is 4.4.46 (self compiled, works on
> > other servers).
> >
> > An md device, that is constructed of 12 luks encrypted disks, will not
> > mount to a path /disk/data but it happily mounts to any other path.
> > This is rather unfortunate because we expect to see our device in that
> > path. The same happens with a dummy file-based filesystem[1], so this
> > is unlikely to be related to the device. Here is a debug sample.
>
> Found it. A systemd mount unit defined a label, that the device did
> not have and neither the dummy filesystem, so the systemd immediately
> umounted the /data/disk/ mount point.
If I good remember there was some systemd issue with "immediately
umounted", it should be fixed in the recent versions.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
