On our stratum0, we observe that during periods of inactivity (mainly at night), the cmvfs filesystems are dismounted and then remounted, which causes problems especially for backups (files disappear during the backup). Is this normal? Can we configure this behavior?
Thanks in advance
Hi Martin,
Thanks for your message. Could you please clarify a few things?
Stratum 0: is this the publisher machine for the repository?
What repositories are configured on the machine and which ones are being unmounted? Are those repositories using an automounter?
Cheers!
Hi,
Thank you for your answer. The Stratum 0 is the publisher for the repository, there are 3 repos on the stratum and only one is a problem (the most used).
Autofs is disabled.
In the logs there is regularly this type of message :
Mar 18 11:16:12 apceuclidccstm0.in2p3.fr systemd[1]: Mounting /var/spool/cvmfs/euclid-dev.in2p3.fr/rdonly..
-- Subject: Unit var-spool-cvmfs-euclid\x2ddev.in2p3.fr-rdonly.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-spool-cvmfs-euclid\x2ddev.in2p3.fr-rdonly.mount has begun starting up.
Mar 18 11:16:12 apceuclidccstm0.in2p3.fr mount[31149]: CernVM-FS: running with suid support
Mar 18 11:16:12 apceuclidccstm0.in2p3.fr mount[31149]: CernVM-FS: loading Fuse module... done
Mar 18 11:16:12 apceuclidccstm0.in2p3.fr cvmfs2[31150]: (euclid-dev.in2p3.fr) CernVM-FS: linking /var/spool
Mar 18 11:16:12 apceuclidccstm0.in2p3.fr systemd[1]: Mounted /var/spool/cvmfs/euclid-dev.in2p3.fr/rdonly.
-- Subject: Unit var-spool-cvmfs-euclid\x2ddev.in2p3.fr-rdonly.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-spool-cvmfs-euclid\x2ddev.in2p3.fr-rdonly.mount has finished starting up.
--
-- The start-up result is done.
That’s normal if somebody is publishing something. Backups should exclude those mountpoints.
When a cvmfs transaction starts, the upper overlay layer gets mounted read-write. When a publish happens, the data is taken out of that upper layer and written into the lower cvmfs client layer, and then the upper layer is mounted read-only.
Dave
Thank you Dave for your answer. In this case, how can we run full backups ? Actually we backup /cvmfs and /srv (we don’t backup /var/spool/cvmfs).
Thanks
/cvmfs does not need to be backed up because it is generated from files in /srv. Do keep backing up /srv. Skipping /var/spool/cvmfs is good.
Dave
Thanks. We were doing that because that’s what it says in the documentation (Creating a Repository (Stratum 0) — CernVM-FS 2.9.1 documentation).