FS#37446 : [glusterfs] Automounting seems completely broken

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#37446 - [glusterfs] Automounting seems completely broken

Attached to Project: Community Packages
Opened by ... (spider007) - Tuesday, 22 October 2013, 14:01 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 05 December 2013, 14:41 GMT

Task Type	Bug Report
Category	Packages
Status	Closed
Assigned To	Sergej Pupykin (sergej)
Architecture	All
Severity	Medium
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	0
Private	No

Details

I may be doing something wrong, but although I'm quite happy with Glusterfs; the integration with systemd on arch is a bit less satisfying. I'm using 3.4.0; which broke the ',nofail' in mount options; thus causing systemd to think it shouldn't continue booting. What makes this even worse is that systemd has never understood that a networked filesystem like Glusterd needs a network, therefore mounting on boot has never worked and I had to create a cronjob to mount stuff...

So:

* a glusterfs mount in fstab causes systemd to attempt mounting before the network is up
* a failed mount causes local-fs.target to stop booting
* nofail causes /usr/bin/fusermount-glusterfs: mount failed: Invalid argument

This task depends upon

Closed by Sergej Pupykin (sergej)
Thursday, 05 December 2013, 14:41 GMT
Reason for closing: Upstream
Additional comments about closing: and workaround looks available