101–110 of 260 posts
Earlier quoted context omitted.
Maybe it's a sort of Teutonic tradition to name things after yourself. e.g. Hetzner, ReiserFS.
Well, there is also Linux, DebIan, Knoppix (Klaus Knopper, admittedly also a German)...
ReiserFS is a lesson in project naming. When I started in Linux full-time, back in the early 2000s, I was presented with different fs options - the installer did not give me any information on benefits, or on which ones were considered "stable". ext2 was available, but it also had a built-in version number, and I feared that once ext3 eventually rolled over, it might be incompatible. So I chose the fs that came with…
That’s why it’s best to only name things after dead people. Less surprises.
Earlier quoted context omitted.
Maybe it's a sort of Teutonic tradition to name things after yourself. e.g. Hetzner, ReiserFS.
Well, there is also Linux, DebIan, Knoppix (Klaus Knopper, admittedly also a German)...
Earlier quoted context omitted.
Yes, the only real problems are edge cases. I use it all the time.
I agree, I love BTRFS and have used it for ages, including some small scale production systems. But I know it still has some edge cases as you mention, which made me wonder: what is the impediment to having those cases fixed? BTRFS has been around long enough and even has some decent commercial support from a few vendors, so it seems like we can't just discount it as "it's open source and nobody is motivated to fix t…
What I do know is that ZFS recently released a feature specifically for the hobbyist/frugal community. The feature allows you to grow an existing RAID array, something a financially sound business would never do. So no customer of anyone supporting ZFS would ever use this, and it took significant effort of ZFS developers to implement this. Not to mention that introducing feature potentially introduces weird behaviour in ZFS that might endanger its (reputation of) stability.
I'm super happy with it, (as my company was not in fact financially sound when we invested in our on-premise storage hardware), but if I was CEO of ZFS I'm not sure I'd sign off on it.
ReiserFS is a lesson in project naming. When I started in Linux full-time, back in the early 2000s, I was presented with different fs options - the installer did not give me any information on benefits, or on which ones were considered "stable". ext2 was available, but it also had a built-in version number, and I feared that once ext3 eventually rolled over, it might be incompatible. So I chose the fs that came with…
Earlier quoted context omitted.
It's interesting that, having avoided a filesystem with a version number, you eventually ended up on Reiser 4! Shows how much some branding decisions can affect with you acquire a user or not, since you then stuck with the "brand" (though I presume quite a lot of time had passed and circumstances may have been different). I formed the impression that Hans Reiser's somewhat bombastic approach did not interface well wi…
There were grandiose plans indeed! Including things like plugins, yes, and ideas like exposing metadata about files (like MP3 artist tags and such) in virtual files. You'd `cat song.mp3/artist` or some such, treating the file as a virtual directory. There also was weird artwork to go with all of that: http://web.archive.org/web/20070219175315/http://www.namesys...
Wow! You weren't kidding. Those really are something else.
Earlier quoted context omitted.
It's great for small files, but it's also got some really nasty little corner cases. You do not store ReiserFS filesystem images on ReiserFS filesystems without encryption, or the next time you run fsck, you'll end up with the two filesystems oddly merged into something entirely useless. I'm not sure if that's been fixed, I got a bit tired of the exotica for general daily driver systems, and ext3/ext4 cover my needs…
I feel like you really need to have a reason to use ext3/4. I stick to xfs for daily stuff and btrfs if I want any sort of extra functionality. It's super stable in basic configs. For example, I have a /data drive formated xfs, then I mount a /backup formated btrfs, rsync the 2, take a btrfs snapshot, and unmount /backup.
Earlier quoted context omitted.
That's one heck of an edge case! How does fsck manage to completely confuse filesystem metadata and data like this? Surely this is only if there's corruption in the (outer) filesystem, right?
No, the meta-data is somehow distributed and fsck can pick up pieces of it. I don't think you have to encrypt the image to avoid the edge case, a compress of the image should be enough. It still sucks though.
"WE DO NOT BREAK USERSPACE" https://lkml.org/lkml/2012/12/23/75 I was surprised to see that Linux has in fact removed other filesystems in the past (and I had to look up the word "senescent"). So the real news to me here is that a somewhat "major" break in userspace is being considered. Sure, ReiserFS might not be getting a lot of new installs, but the fact that people have submitted fixes to it within the past few y…