On 20 September 2017 at 11:46, Rodney Baker <rodney.baker@iinet.net.au> wrote:
On Wednesday, 20 September 2017 16:09:56 ACST Richard Brown wrote:
[...] 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.
Straw man argument. The majority of the discussion has been around ReiserV4, not V3.
Who's making what strawman? this whole thread is about the removal of support by openSUSE of ReiserFS openSUSE has NEVER supported ReiserV4, therefore this thread must logically be primarily about V3, which we did support in the past.
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.
This is behaviour that's abhorrent and remains unfixed.
Even with V4?
I don't know, and I don't know anyone who does; no distribution has adopted V4, it's not in the mainline linux kernel, and no major testing has been accomplished.
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.
I don’t recall anyone arguing that V3 needed no maintenance.
Then you're not reading the posts from john, who clearly said that ReiserFS was "mature and needs no maintenance." I assume he must have been talking about V3 given V4 could never possibly be described as 'mature' as it is unfinished - for example it's much promised transactions support is missing, as is any tooling to handle defragmentation.
Besides, I could be equally critical of btrfs, having had a system end up unbootable, and unrecoverable without a complete repartition/reformat/ reinstall, not once but twice, because btrfs’s default installation parameters (as configured by the openSuSE installer) enabled snapshots to use up all available disk space, and there were no (working) tools available to fix it. THAT is ridiculous and abhorrent behaviour and anyone who entrusts their data to a filesystem that does that is equally insane (IMHO).
https://en.opensuse.org/SDB:BTRFS#How_to_repair_a_broken.2Funmountable_btrfs... I am yet to find anyone who has suffered any such problems when following the above documentation.
There should at least be a warning if btrfs is installed during installation, stating, “Warning - you’ve selected btrfs which will eat up all usable space on your root partition if you don’t fix the settings, because our installation defaults are broken by design.”
I will suggest to the YaST team to implement that only when this mailinglist comes with a warning "You've subscribed to a mailinglist which includes individuals who complain about things they don't understand, nor are willing to contribute to the solution of"
And sure, some die-hard volunteers are maintaining Reiser v4, but it has not been merged into the mainline Linux kernel. And it is unlikely to ever do so, because Reiser4 does not follow Linux coding standards.
That is a totally different issue.
Not at all - I'd rather have a filesystem that is supported by people who I can trust to know what they're doing, than a bunch of amateurs who've proven they don't work well with others. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org