OpenSUSE considers dropping reiserfs
I recognize that there may be people out there with disks containing reiserfs file systems. If these are in active use, I would seriously encourage migrating to something actively maintained.
Posted Aug 7, 2022 20:30 UTC (Sun)
by flussence (guest, #85566)
[Link] (4 responses)
Posted Aug 7, 2022 20:38 UTC (Sun)
by Wol (subscriber, #4433)
[Link]
SUSE would have nack'd removing it from the kernel, but Tumbleweed dropping it probably is signalling quite clearly that its days are numbered ...
Cheers,
Posted Aug 7, 2022 21:16 UTC (Sun)
by randomguy3 (subscriber, #71063)
[Link]
Posted Aug 8, 2022 17:43 UTC (Mon)
by jeffm (subscriber, #29341)
[Link]
Posted Aug 20, 2022 21:13 UTC (Sat)
by roblucid (guest, #48964)
[Link]
Posted Aug 7, 2022 23:25 UTC (Sun)
by Matlib (guest, #134276)
[Link] (3 responses)
Posted Aug 8, 2022 0:36 UTC (Mon)
by k8to (guest, #15413)
[Link] (2 responses)
Posted Aug 8, 2022 3:20 UTC (Mon)
by motk (guest, #51120)
[Link] (6 responses)
Posted Aug 9, 2022 12:01 UTC (Tue)
by swilmet (subscriber, #98424)
[Link]
For files that you don't need anymore but you prefer to keep as backup (for 10 years or 20 years), a practice is to have two disks with the same content, but disconnected. From time to time, you may check that the content is still readable.
That way it uses less energy.
Posted Aug 9, 2022 20:24 UTC (Tue)
by hailfinger (subscriber, #76962)
[Link] (4 responses)
Then I remembered that ReiserFS (which I had used many years ago when it was more stable than ext3) has no inodes and thus no inode limit. And there are tools to do an in-place conversion to ReiserFS. However, the looming deprecation of ReiserFS and its non-maintenance seem to have accumulated bugs slightly faster than ext4 where bugs are introduced through maintenance (b5776e7). So... ReiserFS was not a choice anymore.
In the end I chose XFS and recreated everything from scratch.
Posted Aug 11, 2022 13:35 UTC (Thu)
by smurf (subscriber, #17840)
[Link]
Posted Aug 12, 2022 18:44 UTC (Fri)
by k8to (guest, #15413)
[Link]
Posted Aug 13, 2022 8:31 UTC (Sat)
by jem (subscriber, #24231)
[Link]
It is generally a bad idea to put a huge amount of files in a single directory, no matter what filesystem you are using. You'll run into limits and performance issues. Fortunately, there is a simple solution to this: design your app to spread the files into subdirectories, like Git does.
Posted Aug 20, 2022 21:33 UTC (Sat)
by roblucid (guest, #48964)
[Link]
Posted Aug 8, 2022 6:42 UTC (Mon)
by donbarry (guest, #10485)
[Link] (8 responses)
Posted Aug 8, 2022 8:34 UTC (Mon)
by rsidd (subscriber, #2582)
[Link] (7 responses)
In my opinion ReiserFS users should have made their migration plans in 2008 (and SuSE should have deprecated it at that time). Almost all hardware from that time must have been upgraded long ago; they should have avoided ReiserFS on any new machine. Reiser himself was already deprecating it in favour of Reiser4, and it was all practically a one-man show.
Posted Aug 8, 2022 13:59 UTC (Mon)
by IanKelling (subscriber, #89418)
[Link] (3 responses)
It sounds like this removal is a good thing.
Posted Aug 11, 2022 3:42 UTC (Thu)
by kena (subscriber, #2735)
[Link] (2 responses)
Posted Aug 16, 2022 14:39 UTC (Tue)
by tome (subscriber, #3171)
[Link] (1 responses)
that generally requires remorse, of which Reiser has none
Posted Aug 16, 2022 16:22 UTC (Tue)
by zdzichu (subscriber, #17118)
[Link]
Posted Aug 8, 2022 14:15 UTC (Mon)
by gwolf (subscriber, #14632)
[Link] (1 responses)
Posted Aug 11, 2022 15:08 UTC (Thu)
by Conan_Kudo (subscriber, #103240)
[Link]
Posted Aug 20, 2022 21:20 UTC (Sat)
by roblucid (guest, #48964)
[Link]
Posted Aug 8, 2022 20:18 UTC (Mon)
by chris_se (subscriber, #99706)
[Link] (5 responses)
This argument is not reiserfs-specific, in general this applies to any existing filesystem that that the kernel has either already dropped or for which there are plans to drop it at some point in the future.
This doesn't have to be in the kernel: a FUSE-based project that gathers all filesystems removed from the kernel and provides read-only support for accessing them would be plenty sufficient. Doesn't have to be very fast, doesn't have to provide write support, just has to work, so that when one encounters a device somewhere with such a filesystem, one can still access the data stored on it. Does anybody know of such efforts?
Posted Aug 8, 2022 20:37 UTC (Mon)
by willy (subscriber, #9762)
[Link] (1 responses)
> If these are in active use, I would seriously encourage migrating to something actively maintained. If these are sitting on a shelf for archival purposes, GRUB ships with a fuse frontend for all of its file system drivers, including reiserfs. It's not fast but it's enough for data access.
Posted Aug 8, 2022 23:13 UTC (Mon)
by plugwash (subscriber, #29694)
[Link]
1. How robust are the grub drivers? have they ever been tested in any context other than booting a system?
Posted Aug 9, 2022 1:30 UTC (Tue)
by k8to (guest, #15413)
[Link] (1 responses)
Posted Aug 9, 2022 2:11 UTC (Tue)
by nybble41 (subscriber, #55106)
[Link]
Posted Sep 4, 2022 17:46 UTC (Sun)
by landley (guest, #6789)
[Link]
Even if conversion is only supported for ~7 years or so, you can boot an image from within that timeframe, convert the data to the newer archive format, boot the NEXT one you need a decade later, convert to the next format, etc. On any unixoid you can almost always manage to write a tarball to an NFS mount, or pipe it through uuencode to an emulated serial device being written to a file, or some such.
Storage getting bigger makes old block devices easier to image, and a proper data recovery setup will have snapshots of things like the devuan "pool1.iso" file so the servers having gone away no longer matter even if you need a weird obscure tool out of the repository:
And you can usually dig up really _old_ stuff if you know where to look... https://archive.download.redhat.com/pub/redhat/linux/
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
Wol
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
I remember as I used reiserfs in SuSE since the release with 2.4 came out, later with XFS which was the one that gave me trouble with corruption on power failures until I bought a UPS.
It's been broken since 4.0 with some severe bugs. It used to be my weapon of choice for laptops, VMs and embedded stuff, and if fact I'm stuck with the last long-term kernel 3.x.x on one such machine.
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
GRUB won't boot from an ext4 filesystem with large_dir active, so I suddenly had a non-bootable system with no spare capacity to recreate a working state. Lesson learned.
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
After running a lot of machines you get defensive from seeing file corruption in / and try to eliminate dramas.
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
It is also possible to convert from ReiserFS to Btrfs in-place.
OpenSUSE considers dropping reiserfs
OpenSUSE considers dropping reiserfs
Removal of filesystem support: downsides
Removal of filesystem support: downsides
Removal of filesystem support: downsides
2. Will grub continue to support filesystems if/when they are dropped from the kernel.
Removal of filesystem support: downsides
Removal of filesystem support: downsides
Removal of filesystem support: downsides
https://ftp.nluug.nl/pub/os/Linux/distr/devuan/devuan_chi...