161–170 of 260 posts
"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…
Removing a kernel driver does not break userspace. I mean, yes, your filesystem becomes inaccessible, but any programs that you could run if you could access that filesystem by some other means would still function. None of them depend on ReiserFS specifically for their function. Userspace breakage is more about changing interfaces in such a way that applications using that interface change their behaviour somehow. T…
Earlier quoted context omitted.
edit: sorry, cheap shot at Facebook. I have no idea why BTRFS edge cases are not being fixed. 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…
I could already grow mdraid and reiserfs forever ago.
Earlier quoted context omitted.
Well in the case of last name unless those dead peoples was the last one standing with the surname there is always the possibility of a descendant or someone from a different branch of the family name tree commiting bad things. Add to that some people sometimes decide to give a famouse surname as a firstname for their kids. There is a non negligible number of people sporting the Lafayette, Napoleon, Lincoln as first…
Well, it can work out OK if one particular person has a strong enough association with the name. Lincoln is a great example. It seems unlikely that anyone with that name will become so infamous as to tarnish it. The voters of Lincoln, Nebraska or the board of the Ford Motor Company (owners of the Lincoln automotive brand) are pretty safe from needing to rename those things.
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…
don't murder your wife, got it. this is the kind of high level advice i come here for
Earlier quoted context omitted.
> The logical successor was supposed to be btrfs, but that project IMHO may never be ready for production use. https://btrfs.wiki.kernel.org/index.php/Production_Users Facebook deployed it on millions of servers. Is that production enough? Synology NAS devices also use it.
Facebook doesn’t use it’s servers the same way we use our computers. They image machines in and out of existence. They don’t have file systems going through power loss on a weekly basis. They don’t upgrade the kernel on existing installations. They don’t expand their storage after the fact. If their machines fail, they don’t care - they’re completely fungible.
This myth is being perpetuated despite btrfs devs (who work at facebook) stating the exact opposite many times over.
Every FS corruption and weird behavior is put aside and investigated. They very much do care.
https://lwn.net/ml/fedora-devel/03fbbb9a-7e74-fc49-c663-3272...
Please read the whole thread before repeating this nonsense, or at least every email sent there by Josef Bacik.
See also:
Earlier quoted context omitted.
There are interesting links to slavery and workhouses by allowing people to do actual labor from prison. There is pretty much no way to allow people to 'volunteer' to do this kind of work without giving someone an incentive to get as many people into prison and using it as a giant slave work camp.
Don't prisoners already work in prisons, atleast in US ones? (although my knowledge comes mostly from movies and new articles).
Maybe someone with more understanding of kernel development could explain things to me. Does there have to be explicit kernel-level support to support a filesystem? Even if they remove support, does that stop anyone from releasing a kernel module and supporting it?
Depends if you want to boot from it, IIRC. Your kernel has to have compiled-in support for the filesystem of the drive you store your kernel modules on.
Thats how people boot from ZFS
Earlier quoted context omitted.
> The logical successor was supposed to be btrfs, but that project IMHO may never be ready for production use. https://btrfs.wiki.kernel.org/index.php/Production_Users Facebook deployed it on millions of servers. Is that production enough? Synology NAS devices also use it.
Lots of people seem to turn up their nose at btrfs. Is there a reason for that? Was it perhaps launched before it was really ready and people still remember early versions?
Earlier quoted context omitted.
> The logical successor was supposed to be btrfs, but that project IMHO may never be ready for production use. https://btrfs.wiki.kernel.org/index.php/Production_Users Facebook deployed it on millions of servers. Is that production enough? Synology NAS devices also use it.
Lots of people seem to turn up their nose at btrfs. Is there a reason for that? Was it perhaps launched before it was really ready and people still remember early versions?
I've never lost data to it, I've never tried the soft RAID modes it has though, but I've experienced it making a system almost unusably slow. SUSE out of the box with it automates a lot of it and it's pretty remarkable. Transactional mode if you want it seems like a game changer for some servers and the snapper stuff has saved my bacon a couple times. It's getting there but like I said, it needs some maintenance and just formatting a partition with it is likely the wrong way to experience it.