On 20 September 2017 at 08:22, John Andersen <jsamyth@gmail.com> wrote:
On September 19, 2017 3:34:47 PM PDT, Anton Aylward <opensuse@antonaylward.com> wrote:
On 19/09/17 09:17 AM, Per Jessen wrote:
it looks like there will be no provision in the Leap15 kernel for ReiserFS as a module any more.
I don't see that mentioned anywhere. It's also difficult to see why we should go to the length of changing the kernel build config to exclude a module just because we don't want to support that file system.
I agree, but that seems to be the implication if it steps through the /etc/fstab forcing you to change all the ReiserFS to something else. Why do that unless the ReiserFS module has been pulled?
ReiserFS never was part of the kernel, it was always a module. Uh, gazillions of things are "part of the kernel", as modules.
Precisely. And John's argument that its old is pretty meaningless when you look at some of those others.
If you wanted it in the kernel you had to recompile it yourself. If "in the kernel" means "not as a module", you are right. Same applies to most of the other file systems and drivers.
Right now, it seems the only one hard compiled in is ext4FS. I look that the modules for my 42.2/4.2.13 and btrfs is there. It's not compiled in.
Whooosh! I never made that argument.
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? 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. 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. 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? 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. Do you really want to trust your data to a filesystem who's code quality is so poor there is no likelihood of it ever being merged into the Linux kernel? Whatever people may or may not do in other OBS repos is immaterial - openSUSE currently only supports filesystems that are part of the mainline Linux kernel. 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. 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, 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