Edward Shishkin

Hello. For now we can not find enough resources for reiser4 support. Porting to the latest kernels will take approximately 1 week. Thanks, Edward.

Yes, it is.

Yes, the patch for 5.18 is in plans. Unfortunately there were essential changes in VFS interface, so the port will take some time. Thanks, Edward.

It is because of VFS changes backported to 5.15.41. Respectively, a new reiser4-for-5.15.41 patch is needed. This patch should include the following commit (or only some its parts, related to the new function fault_in_readable()): https://github.com/edward6/reiser4/commit/719c4bb7c8b2c009c28b1f33c3e28fbef9239ca0 If you don't want to wait, you can do it by yourself, Just let me know, if any problems. Thanks, Edward. On Mon, May 30, 2022 at 6:43 AM Dee boonfogle@users.sourceforge.net wrote: Using the...

This resource is devoted to a software product. Any irrelevant stuff will be removed. With any suggestion to rename something please provide a complete set of patches (including the ones against partition manipulating utilities like parted) plus make sure that file systems with the old and new name being installed in the same OS won't step to each other. Thanks.

Sorry, not interesting. I also have a lot of ideas, and it it not clear who will implement them. Thanks, Edward.

Slow umount of reiser4 partition after many hours of high load

Hello, The stable version of Reiser4 includes 2 modules (file plugins) which manage regular files: unix file plugin: Doesn’t use compression. Stores file bodies either as fragments in the tree, or as sets on unformatted blocks (extents) depending on formatting policy (mkfs option “formatting=[tails, extents, smart]”. “tails” means storing file body as a set of fragments (tails) in the tree, “extents” means storing file body as sets of unformatted blocks (extents). “smart” means storing small (<=20K)...