Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As another anecdote:

I've been working with systems for a long time, too. I've screwed things up.

I once somehow decided that using an a.out kernel would be a good match for a Slackware diskset that used elf binaries. (It didn't go well.)

In terms of filesystems: I've had issues with FAT, FAT32, HPFS, NTFS, EXT2, ReiserFS, EXT3, UFS, EXT4, and exFAT. Most of those filesystems are very old now, but some of of these issues have trashed parts of systems beyond comprehension and those issues are part of my background in life whether I like it or not.

I've also had issues with ZFS. I've only been using ZFS in any form at all for about 9 years so far, but in that time I've always able to wrest the system back into order even on the seemingly most-unlikely, least-resilient, garbage-tier hardware -- including after experiencing unlikely problems that I introduced myself by dicking around with stuff in unusual ways.

Can you elaborate upon the two particular unrecoverable issues you experienced?

(And yeah, Google is/was/has been poisoned for a long time as it relates to ZFS. There was a very long streak of people proffering bad mojo about ZFS under an air of presumed authority, and this hasn't been helpful to anyone. The sheer perversity of the popular myths that have popularly surrounded ZFS are profoundly bizarre, and do not help with finding actual solutions to real-world problems.

The timeline is corrupt.)



>The sheer perversity of the popular myths that have popularly surrounded ZFS are profoundly bizarre

Cyberjock sends his regards, I'm sure.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: