• Metztli Reiser4 / Debian 11 Bullseye on Google Compute Engine (GCE)

    New Metztl Reiser4 based on Debian 11, codename Bullseye, still to be released by the Google Compute Engine (GCE) team. Metztli Reiser4 / Debian 11, Bullseye, 200 Gig with JFS /boot and reiser4, Software Framework Release Number (SFRN) 4.0.2 / root file system, on Google Compute Engine (GCE) Cloud. PoC more »

  • volume.reiser4

    Manpage for volume.reiser4, Software Framework Release Number (SFRN) 5, aka 'reiser5'. (supersedes previous man page) more »

  • volume.reiser4

    Manpage for volume.reiser4, Software Framework Release Number (SFRN) 5, aka 'reiser5'. more »

  • 'maybe reiser4 is just terribly slow for this access pattern?'

    In an ageing reiser4 development environment where I still build Metztli Reiser4 and, recently, Metztli Reiser5 kernels and hack the Debian Installer (d-i) minimal netboot images that I make available in SourceForge site, I began to notice systemd errors in dmesg logs. more »

  • "Er... Does anybody maintain reiser4 these days?"¹

    In Reiser5, i.e., Reiser4 Software Framework Release Number (SFRN) 5.1.3, scaling out is performed by file system means, rather than by block layer means. The flow of IO-requests issued against each device is controlled by user. To add a device to a logical volume with parallel scaling out, you first need to format that device -- this is the difference between parallel and non-parallel scaling at first glance. The principal difference between parallel and non-parallel scaling out will be discussed below more »