remove outdated filesystem recommendation #224
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is more of an issue/discussion but this repo doesn't seem to have issues.
Anyway this line recommending ext3 or 4 over XFS has existed unchanged in the documentation for 8 years and recently made it into the "Best Practices for CernVM FS in HPC" tutorial, probably reaching many eyes.
If there is a specific reason for preferring ext4 over XFS it should be explained and justified in the documentation. But the fact that it was put in 8 years ago and never updated leads me to believe the information is likely stale. A great deal has changed in that time, including extensive improvements and engineering efforts going into XFS and likely ext4 as well. To remain valid as a recommendation, some current benchmarking (or other clarifying information) would be needed.
One can find endless debates about ext4 vs XFS but all in all they both seem fine these days. If one foresees a need to shrink a filesystem, use ext4. XFS seems better for more parallel IO streams (which I would think should favour CVMFS) whereas ext4 may be better for single streams.
But in particular nobody should be recommending ext3 anymore! Unless there is forthcoming information to justify this recommendation I would suggest removing it. @jblomer @DrDaveD ?