Skip to content

Commit dde8cf5

Browse files
committed
Expand known issues and make it more prominent
1 parent 14223f9 commit dde8cf5

File tree

3 files changed

+47
-2
lines changed

3 files changed

+47
-2
lines changed

apx-issues.rst

Lines changed: 41 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,47 @@
11
Known Issues
22
============
33

4+
These pages mentions known limitations that won't be fixed, and bugs affecting certain verisons that can interfere with operations. For a more details see the changelog pages and issue tracker.
5+
6+
Known Issues By Version
7+
-----------------------
8+
9+
CernVM-FS 2.13.2
10+
^^^^^^^^^^^^^^
11+
12+
* Race condition in auto-mounts/umounts can lead to stuck cvmfs processes
13+
14+
CernVM-FS 2.13.1
15+
^^^^^^^^^^^^^^^^^^
16+
17+
* Race condition in auto-mounts/umounts can lead to stuck cvmfs processes
18+
* Crashes due to Page Cache Tracker Mismatches
19+
20+
21+
CernVM-FS 2.12.7
22+
^^^^^^^^^^^^^^^^^^
23+
24+
* [server] ingesting a tarball with double slashes in base_dir corrupts repository
25+
* Crashes due to Page Cache Tracker Mismatches
26+
27+
28+
Description
29+
----------
30+
31+
32+
Race condition in auto-mounts/umounts can lead to stuck cvmfs processes
33+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
34+
35+
36+
The feature of pre-mounting the fuse device introduced in 2.13.0 can make issues when autofs unmounts the repository just as another process remounts it. This can be especially noticeable with short autofs timeouts and automatic checks that may remount the repositories. Github issue: `3993 <https://github.com/cvmfs/cvmfs/issues/3993>`__
37+
38+
Crashes due to Page Cache Tracker Mismatches
39+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
40+
41+
A mismatch in internal data structures triggered by repository updates can throw an assert, crashing cvmfs. Github issue: `3520 <https://github.com/cvmfs/cvmfs/issues/3520>`__
42+
443
Slow Performance with a Very Large File Descriptor Limit
5-
--------------------------------------------------------
44+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
645

746
Before CernVM-FS 2.11, having the file descriptor limit set to a very large number
847
will result in a very slow ``cvmfs`` performance in certain situations.
@@ -11,7 +50,7 @@ instead of just the used/opened ones.
1150
This issue is resolved in CernVM-FS 2.11.
1251

1352
Publisher nodes with AUFS and XFS
14-
---------------------------------
53+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1554

1655
If the ``/tmp`` file system is on xfs, the publisher node cannot be used with AUFS.
1756
On such systems, adding the mount option ``xino=/dev/shm/aufs.xino`` can be

cpt-releasenotes.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@
44
Release Notes for CernVM-FS 2.13.2
55
==================================
66

7+
.. note::
8+
In CernVM-FS 2.13.2 there is a race when automounting/-unmounting repositories that lead to clients. A new patch release is in preparation. This issue can be mitigated by increasing the autofs timeout. See the "Known Issues" page for more details
9+
710
CernVM-FS 2.13.2 is a fairly large patch release. It fixes two long standing issues in the core client code that have caused crashes in some rare circumstances.
811
A regression in 2.13 that has led to spurious "failed to umount (errno 22)" log messages is fixed as well.
912
Furthermore this patch release includes some important improvements for stratum one operations (As a reminder, the versioning of CVMFS is semantic mostly for the client.

index.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,12 @@ CernVM-FS is actively used by small and large HEP collaborations. In many
3232
cases, it replaces package managers and shared software areas on cluster file
3333
systems as means to distribute the software used to process experiment data.
3434

35+
3536
Contents
3637
^^^^^^^^
3738

39+
We recommend to consult the Release Notes and Known Issues pages before doing any upgrades.
40+
3841
.. toctree::
3942
:maxdepth: 2
4043

0 commit comments

Comments
 (0)