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 100%
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
Comment by Sergej Pupykin (sergej) - Wednesday, 23 October 2013, 10:52 GMT
did you try
x-systemd.device-timeout=
?
Comment by ... (spider007) - Wednesday, 23 October 2013, 11:05 GMT
No I didn't and it might indeed work. Is that the best solution?
Comment by Sergej Pupykin (sergej) - Thursday, 05 December 2013, 14:40 GMT
Not sure, but anyway glusterfs uses upstream .service file now.

Loading...