Package Details: cvmfs 2.5.2-1

Git Clone URL: https://aur.archlinux.org/cvmfs.git (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: http://cernvm.cern.ch/portal/filesystem
Licenses: BSD
Submitter: bins
Maintainer: fsiegert (vandelli)
Last Packager: vandelli
Votes: 6
Popularity: 0.060623
First Submitted: 2010-12-08 13:59
Last Updated: 2019-03-12 13:33

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

kgizdov commented on 2017-06-29 16:14

@kfinelli, that sounds more like Atlas scripts don't set the correct lib path to the ncurses version they used to compile ROOT against. If you set your environment from CVMFS and then do `ldd $(root-config --libdir)/*.so | grep -B 10 ncurses`, it will tell you whichever library (possibly libCling.so) does not find its dependency correctly.

kfinelli commented on 2017-06-29 12:04

This isn't directly related to the package, but might affect a lot of users- I noticed that in order to run ROOT as distributed on atlas cvmfs I needed to add the ncurses5-compat-libs from AUR.

Another minor point is that the documentation link printed from cvmfs.install seems to be broken/out-of-date

kgizdov commented on 2017-06-26 21:21

Also, you should add `_netdev` as part of the mount options in `/etc/fstab`, otherwise you get a circular dependency on `network-online.target`. Check your `dmesg -l warn` output

kgizdov commented on 2017-06-25 13:39

@fsiegert, @vandelli, thanks for this - the systemd-mount works really nicely for me now. I think from now on that would be my default. I've tried AutoFS for other things before, but it never really worked correctly for me.

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:

atlas.cern.ch /cvmfs/atlas.cern.ch cvmfs noauto,x-systemd.automount,x-systemd.requires=network-online.target,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

Cheers
Wainer


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/sft.cern.ch, and another cvmfs process spawned automatically, trying to mount /cvmfs/cvmfs-config.cern.ch. 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/cvmfs-config.cern.ch" first, and only then access e.g. /cvmfs/sft.cern.ch, 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 (https://wiki.archlinux.org/index.php/Fstab#Automount_with_systemd) 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 - https://github.com/kgizdov/cvmfs

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.

Cheers,
Raja.

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?

Cheers,
Frank