Package Details: cvmfs 2.3.5-4

Git Clone URL: (read-only)
Package Base: cvmfs
Description: A client-server file system implemented in FUSE and developed to deliver software distributions onto virtual machines in a fast, scalable, and reliable way.
Upstream URL:
Licenses: BSD
Submitter: bins
Maintainer: fsiegert (vandelli)
Last Packager: fsiegert
Votes: 2
Popularity: 0.005364
First Submitted: 2010-12-08 13:59
Last Updated: 2017-06-23 16:02

Latest Comments

fsiegert commented on 2017-06-23 16:05

Thanks vandelli, that indeed seems to work great.

I have pushed an updated PKGBUILD taking into account many of the suggestions from kgizdov (thanks!) and also the move to systemd.automount. When updating to that, please make sure you don't have any mounts from autofs left and also no directories created (manually) within /cvmfs.

Let me know how this is working for you.

vandelli commented on 2017-06-23 06:00

Hi fsiegert,

indeed I experienced similar problems with autofs.

Eventually I kind of gave trying to understand the problem and instead started experimenting with systemd-automount. So far it works way better for me.
This is what I added to /etc/fstab: /cvmfs/ cvmfs noauto,x-systemd.automount,,x-systemd.idle-timeout=5min,x-systemd.device-timeout=10 0 0

This is on my laptop where I do not CVMFS mounted unless I'm using it, hence the noauto and x-systemd.idle-timeout=5min


fsiegert commented on 2017-06-22 14:16

Hi kgizdov,

thanks a lot, that looks very nice, in particular since one of the built-in libs doesn't compile with gcc7 anymore!

I had tried something similar before, and have encountered the following problem, which also happens with your PKGBUILD: Mounting directly (as root using "mount") works fine, but when I set up the autofs to mount automatically on demand, the mount doesn't succeed. Strangely enough this didn't happen when using the built-in libs, only when compiling against the system ones!

This seems to be some kind of race condition between the cvmfs process trying to mount the originally requested directory, e.g. /cvmfs/, and another cvmfs process spawned automatically, trying to mount /cvmfs/ In other words, the first "sft" cvmfs process tried to access a file in that "cvmfs-config" directory, thus triggering the second process.

If I simply "ls /cvmfs/" first, and only then access e.g. /cvmfs/, then autofs works fine, indicating in my view that there seems to be some conflict between the two simultaneous processes.

Can you (or anybody else) reproduce this?
I'd like to have a cvmfs package with automount working, so if you have any idea for a solution or workaround that would be great. I have also been thinking about whether switching to systemd.automount ( might be an option, anybody have any experience with that?

PS: Good point on the autofs dependency!

kgizdov commented on 2017-06-20 21:24

So I was playing around with this package and did some notable changes. Have a look here -

Significant changes:
- do not use built-in packages, Arch already provides them
- install the license properly
- do not use 'libexec' folder as per Arch Packaging Standard, patch included
- python-geoip.patch not needed when using Arch's python plugin
- some stronger build options in settings.cmake specified
- cvmfs_config does not require edits
- include default.local in package and improve install message
- do not auto configure autofs as it is not a dependency and not required for operation, give use info on install instead

rajanandakumar commented on 2016-02-01 17:34

Hi Frank,

My apologies for the delay. It works fine now.


fsiegert commented on 2016-01-28 13:21

Thanks rajanandakumar for letting me know about this. I was able to reproduce it, even though nothing in the package has changed in quite a while -- so I assume this must have been some external change which triggered this issue.

Anyway, I have just pushed a new PKGBUILD which should take care of using the Arch-compatible directories instead of the two defaults (/usr/bin and /usr/lib instead of /sbin and /usr/lib64).

Can you let me know whether that works for you now?


rajanandakumar commented on 2016-01-28 11:55


Trying to install it, I get

error: failed to commit transaction (conflicting files)
cvmfs: /sbin exists in filesystem
cvmfs: /usr/lib64 exists in filesystem
Errors occurred, no packages were upgraded.

Any suggestions on how to go about fixing this? I did have a look at the various messages regarding this, dating back to 2013, but there seems to be none relevant here. Most seem to suggest that it needs to be fixed at the package level.

Thanks and Cheers,

bins commented on 2014-06-06 17:31

hi Frank,

yes, please, go ahead, adopt it :)


fsiegert commented on 2014-06-06 16:09

Hi Sebastien,

Are you still working on the package or would you like to orphan it?
I have an updated version for the current cvmfs release, which also takes care of some of the configuration steps automatically:

But I don't think I am allowed to upload it to AUR as long as you are the Maintainer.