Bug 53665 - mount fails when fstab has more than one entry for unloaded fs module
Summary: mount fails when fstab has more than one entry for unloaded fs module
Status: RESOLVED NOTOURBUG
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-18 01:34 UTC by Gerardo Exequiel Pozzi
Modified: 2012-09-14 13:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Gerardo Exequiel Pozzi 2012-08-18 01:34:07 UTC
OS: Arch Linux / systemd-188 / kmod-9 / Linux 3.4.9 (or 3.0.40)

Sometimes one mount fails, others two mounts fails. To workaround this, I need to preload such fs module (for example in /etc/modules-load.d/xfs.conf).

My fstab looks like:
--
/dev/sda1 / ext4 defaults 0 1
/dev/sdb1 /data/data1 xfs defaults 0 2
/dev/sdc1 /data/data2 xfs defaults 0 2
/dev/sdd1 /data/data3 xfs defaults 0 2
--

systemctl status
--
-.mount                    loaded active mounted     /
data-data1.mount           loaded active mounted     /data/data1
data-data2.mount           loaded active mounted     /data/data2
data-data3.mount           loaded failed failed      /data/data3
--

systemctl status data-data3.mount
--
data-data3.mount - /data/data3
          Loaded: loaded (/etc/fstab)
          Active: failed (Result: exit-code) since Fri, 17 Aug 2012 22:23:20 -0300; 3min 34s ago
           Where: /data/data3
            What: /dev/sdd1
         Process: 138 ExecMount=/bin/mount /dev/sdd1 /data/data3 -t xfs (code=exited, status=32)
          CGroup: name=systemd:/system/data-data3.mount

Aug 17 22:23:20 archbase mount[138]: mount: unknown filesystem type 'xfs'
--
Comment 1 Kay Sievers 2012-09-13 17:55:39 UTC
It's a bug in kmod/the kernel:
  https://bugzilla.redhat.com/show_bug.cgi?id=771285

Systemd can not fix that, it only exposes the bug because of the parallelism.

Lucas (kmod) and Rusty (kernel) have a kernel patch pending to fix that.

Thanks!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.