On Wed, 20 Sep 2017 08:39:56 +0200 Richard Brown <RBrownCCB@opensuse.org> wrote:
On 20 September 2017 at 08:22, John Andersen <jsamyth@gmail.com> wrote:
It was a jab at Brown's denigration of Reiserfs simply because it's mature and needs no maintenance.
Apart from the fact that ReiserFSv3 is the only filesystem I am aware of who's fsck consistently destroys data?
OK, there's a bold assertion and I see there's some justification following, so lets approach this claim with an open mind ...
If you store a ReiserFS v3 disk image (VM, container, etc) on a ReiserFS v3 filesystem, fsck WILL confuse your the disk image for another partition and 'restore' files from the image, corrupting the filesystem and losing data in the process.
OK, so don't do that then! Not something I'm likely to want to do. Moving on ...
This is even possible if you do not totally wipe (not just format, but totally overwrite) a previous ReiserFS v3 partition on the same disk - Reisers' fsck otherwise will try and 'restore' data from the previous partition, overwriting the current one.
Again, don't do that then. So the claim amounts to: you can damage your data if you try to. I can do rm -rf /* as well, does that mean I should stop using GNU? Can you see why some people see your approach as overbearing?
This is behaviour that's abhorrent and remains unfixed. There is no sane person with any understanding of filesystems who could possibly argue that ReiserFS v3 'needs no maintenance' ; even Reiser himself felt the problems were unresolvable, which is why Reiser v4 was started to fundamentally rewrite most of the filesystem to workaround that issue.
Do you really want to trust your data to a filesystem which has fundamental flaws which even the author abandoned rather than trying to fix?
Are there flaws that actually affect me? Why haven't I met them yet? [snip]
And that doesn't mean we fully support ALL filesystems in the kernel; v3 is still built in the mainline kernel for backwards compatibility purposes - but no one should use it. YaST no longer supports installations with it. Upgrades will force migration to a different filesystem. This is good advice - Everyone should migrate to more sensible options than Reiserv3 as soon as possible. Anything is probably a more sensible option.
This is the piece that people are debating and where an answer from somebody knowledgeable would be useful. Is YaST going to suggest that you migrate a reiserfs filesystem to something else or is it going to refuse to continue the upgrade until you have done so? Is that all filesystems on the disks, or just those in the fstab? Is the kernel still going to support reiserfs?
Anyone who ignores this might be able to handcraft a running system regardless, but they should realise they are on their own.
They should expect that no bugs reported will be fixed, bug reports that mention reiserfs are likely to be closed if filesystem type is a possible factor, no compatibility can be ensured as new kernel features are enabled,
Surely that's an issue for the kernel team, not a distro?
breakages are most certainly possible and no effort will be made to test for them, nor fix them if they're reported.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org