You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cpt-releasenotes.rst
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,23 @@
1
1
2
+
Release Notes for CernVM-FS 2.12.2
3
+
==================================
4
+
5
+
CernVM-FS 2.12.2 is a small patch release that adds the "quick" ``cvmfs_config fsck -q`` option to check for and quarantine zeroed files in the cache.
6
+
7
+
Release Notes for CernVM-FS 2.12.1
8
+
==================================
9
+
10
+
CernVM-FS 2.12.1 is a small patch release that fixes a packaging issue: it ensures that the service to reload cvmfs after package upgrades is correctly configured.
2
11
3
12
Release Notes for CernVM-FS 2.12.0
4
13
==================================
5
14
6
-
CernVM-FS 2.12.0 is a sizeable feature release with new features, bug fixes and performance improvements,
15
+
CernVM-FS 2.12.0 is a sizeable feature release with new features, bug fixes and performance improvements.
16
+
NOTE: Testing has shown instances of cache corruption with this release, it will not be released in production. On your testing instances, upgrade to 2.12.2, run ``cvmfs_config fsck -q`` frequently and report any errors.
7
17
8
18
Highlights are:
9
19
10
-
* Support for FUSE-T on MacOS, allowing for easy installation without security tweaks
20
+
* Experimental Support for FUSE-T on MacOS, allowing for easy installation without security tweaks
11
21
12
22
* Refcounted Cache Manager now the default
13
23
@@ -17,6 +27,8 @@ Highlights are:
17
27
18
28
* Several fixes in the fuse internals, for example the page cache tracker
19
29
30
+
* Reloading of CVMFS after package upgrades is now done via a daemon to avoid blocking the package transaction
31
+
20
32
21
33
As with previous releases, upgrading clients should be seamless just by
22
34
installing the new package from the repository. As usual, we recommend updating only a few worker nodes first and gradually ramp up once the new version proves
0 commit comments