[Info-vax] openvms and xterm

[Dan Cross]

In article <memo.20240505180415.16164B at jgd.cix.co.uk>,
John Dallman <jgd at cix.co.uk> wrote:
>In article <fd016548559cb3c8fca2ab4f538153127cfe42c9.camel at munted.eu>,
>alex.buell at munted.eu (Single Stage to Orbit) wrote:
>
>> My experience with btrfs was awful. It's fortunate I only tested it 
>> and took backups, and it kept losing data. Turned to ZFS and it has
>been
>> rock solid. Ten years. 
>
>I had significant trouble with the version in RHEL7/CentOS7, where it was
>the default root filesystem. It's still the default on SUSE Enterprise.
>My local Linux expert tells me that it's been fixed now, although another
>friend who spent some years working for SUSE disagrees. 
>
>I had Android devices connected to a CentOS 7.9 machine, which did
>Android builds, and staged data to be pushed onto the devices. When the
>data set to be pushed was large (more than a few GB), btrfs would often
>decide that it had run out of space, with more than 70% of a 1TB volume
>still free according to df. An fsck would fix the problem, but it would
>reoccur a few days or weeks later. 
>
>My conclusion was that since I was moving to a new Rocky 8.9 machine
>before CentOS 7.9 ran out of support, I'd have my staging area as ext4,
>please, and that has been entirely satisfactory. I was quite happy that
>it was removed from RHEL/Rocky/Alma 8.x; even if it is fixed now, it has
>a bad reputation. 

People who actually know things about filesystems tend to avoid
BtrFS.  OpenZFS on Linux is generally preferred.  Note that the
hyperscalers often use ext4.

	- Dan C.