Hello.
On 03/05/2020 04:49 PM, Metztli Information Technology wrote:
Niltze Ed-
Regarding reiser4, software framework release number (SFRN) 5.1.3, version of reiser4progs-2.0.0 utilities, is
mkfs.reiser4 -yo "create=reg40"
It will work, but it will be suboptimal configuration.
By default reiser4progs-2.0.0 create asymmetric volume (with scaling-out
abilities), but reg40 doesn't support scaling-out. That is, you will be
able to add a device to you logical volume, but data of all files will
go to only one (meta-data) brick :)
Scaling out is supported by a new reg42 file plugin (default in
reiser4progs-2.0.0). That is, data of files managed by reg42 will be
distributed to multiple devices.
So, what do you really want? To work with reg40 files on the kernel with
reiser4 module of SFRN 5.1.3? If so, then you might want to
1) build and install kernel with reiser4 of SFRN 5.1.3 - don't forget to
turn on "Plan-A key allocation scheme" in menuconfig.
2) format a partition by old reiser4progs-1.2.1 (SFRN 4.0.2) with the
option "-o create=reg40" and mount it.
In theory you will be able to prepare such partition by new
reiser4progs-2.X.Y (SFRN-5.Y.Z). The equivalent formatting option is
"-o vol=simple,dist=trivial,keyalloc=plana,create=reg40"
But it doesn't work for now (mkfs segfaults when specifying that option)
- I'll fix it later..
Thanks,
Edward.
P.S. As usual, list of default plugins is available by option "-p" of
mkfs. List of all possible plugins - by option "-l".
reiser4progs-2.0.0 (5.1.3) has default settings, which are optimal for
new scaling-out features. Unfortunately old file plugins ("classic"
reg40, as well as cryptcompress "ccreg40", which provide the most
compact storage, don't make a friendship with scaling-out - use them
only in conjunction with simple volumes. Well, it is possible to use
them on asymmetric volume (vol=asym), but, as I said, it will be
suboptimal - that volume plugin spends more resources, which is not
justified when using only one device.
still appropriate to formatting a rootfs (/) media and/or a partition prior to
installation of a GNU/Linux distribution, i.e., Debian Buster for AMD64?
I have already built/embedded the SFRN5 kernel into preliminary metztli-reiser4-sfrn5.iso, minimal netboot installation media
< https://metztli.it/buster-reiser5/metztli-reiser4-sfrn5.iso >
< https://metztli.it/buster-reiser5/metztli-reiser4-sfrn5.iso.SHA256SUM >
and, using the formatting command above, installed onto ~2TB and ~200GB VirtualBox instances with Reiser5 rootfs, i.e.,
< https://metztli.systems/system/media_attachments/files/000/000/161/original/ca7acd7030d7565b.png?1583319334 >
< https://metztli.systems/system/media_attachments/files/000/000/162/original/e3e043e640d5ee97.png?1583319358 >
as well as into a ~100GB physical partition with Reise5 rootfs. But I wanted to ascertain
the default format command for the hacked SFRN5 Debian installer (d-i) for Buster (stable) distribution prior to making the image public.
Best Professional Regards.
