[systemd-devel] using native *.mount units instead of /etc/fstab - unpredictable state in case of many disks

Lennart Poettering lennart at poettering.net
Tue Jun 19 11:29:09 PDT 2012


On Sun, 03.06.12 22:18, Peter Lemenkov (lemenkov at gmail.com) wrote:

> Hello.
> I've hit by a strange issue on a machine with 8 hard disks. if I list
> them all in /etc/fstab they mounts fine. If I provide native *.mount
> files then almost every reboot one or several disks failed to mount
> (with 32 error, e.g. "code=exited, status=32", which means that no
> hadrwae is available at the moment of mount attempt, wrong fs, etc).
> If I login and run "systemctl restart media-mypathX.mount" it mounts
> just fine. Here is how these *.mount files looks like (no RAID, no
> LVM, etc - just plain alone single-partitioned hard disk):

Hmm, usually mount is also connected to syslog/journal and will write an
error message there with more details. Could you check if you find
anything there?


Lennart

-- 
Lennart Poettering - Red Hat, Inc.


More information about the systemd-devel mailing list