News for hackers. Stuff that matters.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by gbrown_ on Friday August 05, 2016 @11:42AM (#12233149)
Bryan Cantrill expresses this[1] in a manner I certainly agree with. Software that is designed/ intended to be reliable should not go through large periods of instability only to be written off as "prepubescence".

[1]http://www.youtube.com/watch?v=79fvDDPaIoY&t=18m28s

Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by cpeterso on Friday August 05, 2016 @12:06PM (#12233385)
Bryan Cantrill is such a great storyteller. "My therapist says I need to talk about the firmware revision numbers, just to let it out so it doesn't corrode me." He then shares a story about a firmware bug where the polarity would be reversed of the disk read/write head. :)
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by rdtsc on Friday August 05, 2016 @01:13PM (#12234058)
Completely agree.

I often just search for videos by him and just listen to him present a topic or talk about anything. I learned about things normally I wouldn't go and read about otherwise -- history of Sun, ZFS, dtrace, containerization (Joyent, zones legacy, KVM, comparison with Docker).

In that respect he is like David Beazley (of Python fame). I could just listen to David talk all day and not get tired of it.

Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by rdtsc on Friday August 05, 2016 @01:21PM (#12234118)
Ooh, like that analogy. Pure gold:

(Paraphrasing):

---

ZFS never went through a period where people lost data using it. ... amazing how people are willing to write that off like 'Oh well, it kind of lost my data but Omg! A million eyeballs'.

This is like a 12 year old who is stealing cars -- this is a serious issue. Not like "Well...he's only 12" it is more like "He stole a car at gunpoint, having just robbed a liquor store". Can't say let's just wait till he's 18. Would you want to know what he's like when he's 18?

---

Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by makomk on Friday August 05, 2016 @02:02PM (#12234482)
Technically, ZFS never went through a period where people lost data using it. It just kernel paniced when they tried to access their data and besides it was probably their fault for using hardware that was slightly flaky. (Early ZFS adopters had a really interesting time of it, judging from the complaints people had back then.)
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by rdtsc on Friday August 05, 2016 @04:18PM (#12235465)
I am guessing in general losing data (overwriting, dropping it on the floor) is usually worse than crashing the system.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by X86BSD on Friday August 05, 2016 @03:54PM (#12235305)
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by vidoc on Friday August 05, 2016 @07:34PM (#12236371)
About the first video talking about epoll design flaws, doesn't EPOLLONESHOT kind of solve this? Unless I am missing something..
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by X86BSD on Friday August 05, 2016 @11:02PM (#12236825)
Perhaps it does. But the point was that the Linux world never seems to get things right. They implement horrendous solutions that are not engineered or even well thought out and wind up reimplementing said solution over and over and over again to solve the problem instead of learning anything from others who have solved these problems already. They refuse to look outside their echo chamber and double down on NIH and just implement piss poor solutions to problems. And it's so frustrating for the rest of us to watch.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by vidoc on Saturday August 06, 2016 @12:09AM (#12236983)
> Perhaps it does. But the point was that the Linux world never seems to get things right.

Well in this particular case, seems like this feature was added in linux 2.6.2 (2004). epoll itself was added in linux 2.5.44 (2002), so yep, you're correct that they didn't make this right immediately. Now I think it is rather easy to play this game of pinpointing flaws this way and it could be done the other way around, probably in an equally as unconstructive matter (e.g: how long did freebsd wait for robust mutexes?).

That said, amazing speaker, thanks for the links.

Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by X86BSD on Saturday August 06, 2016 @12:55AM (#12237078)
Waiting to implement a feature while you actually engineer it well and robustly is not the same as throwing poop at a wall and seeing what sticks then scraping the poop off and forming it into another shape and throwing at the wall again.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by vidoc on Saturday August 06, 2016 @01:14AM (#12237137)
Seems like you are no fan of linux's robust mutexes implementation. Sincerely, you probably know more than me about the implementation and I'd be curious to have your take on it as I have not looked at how (and so late) it was implemented in FreeBSD.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by X86BSD on Saturday August 06, 2016 @01:28AM (#12237171)
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by koverstreet on Saturday August 06, 2016 @12:11PM (#12238592)
edge triggered is the correct way to use epoll, which has been there since the beginning.

The reason epoll has a stupid mode is that it was also designed to be a drop in replacement for select.