5 ms·
$ head -1 /proc/meminfo MemTotal: 4046880 kB $ grep model.name /proc/cpuinfo | head -1 model name : Intel(R) Core(TM)2 Quad CPU Q660
by barrkel 10y ago
$ head -1 /proc/meminfo
MemTotal: 4046880 kB
$ grep model.name /proc/cpuinfo | head -1
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
$ sudo zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
tank 36.2T 27.2T 9.09T - 10% 74% 1.00x ONLINE -
That's 10x 4TB WD Red drives in raidz2 configuration.
I've been running ZFS for the past 6 years, a little over 2 years on ZoL, and 4 years before that on Nexenta (Ubuntu userland with OpenSolaris kernel).
I've had 5 HDD failures over the past few years, never lost any data.
I've found ZoL to have less jitter when streaming video files in particular over SMB than the Solaris implementation did. ZoL is tighter on memory though.
raidz2 isn't particularly fast for random I/O (since it acts like it has a single spindle), but I don't do much random I/O. It's mostly video and local backup cache.
I'll be thinking about expanding my current setup soon enough. I'll probably be aiming for a raid10 setup for better random access, and of course the new system will have more RAM, and ECC.
- agumonkey 10y agoThanks. Beefier cpu than the beefier I got here, but RAM is a great hint that for personal needs ZFS can run on normal machines. Interesting that you had no issues without ECC in the first place. Some ZFS boards are pretty against trying ZFS without.
- rincebrain 10y agoZFS boards really encourage you to use ECC because one of the nominal features of ZFS, "end-to-end checksumming", is not quite as useful if you have a point between ends where it won't notice silent data corruption (e.g. a bad stick of non-ECC RAM). ZFS will notice, depending on _when_ the munging happened (if it was mangled after it got to RAM but before ZFS checksummed it, it obviously can't), but that's (primarily) why ZFS boards often tell you not to do that.
- erkkie 10y agoNot only that, but I believe a bad checksum can also cause a cascade to "fix the data", causing further corruption.
- the_why_of_y 10y agoFor that to happen, you would need a bad checksum and the corresponding data block to be corrupted in such a way that the corrupted data block checksums to the corrupted checksum. Given that the checksum is 256-bit, the scariest I'd call that is "possible in theory".
- mioelnir 10y ago> Interesting that you had no issues without ECC in the first place. Some ZFS boards are pretty against trying ZFS without. ZFS without ECC is no better or worse than any other filesystem without ECC, in that silent data corruption is possible. It is for this reason just a lot worse than ZFS with ECC, introducing a fault condition normally not seen on ZFS. But that fault condition does not go away because you chose to skip ZFS due to no ECC. And you will get a lot of other problems on top that ZFS would have helped against, even without ECC. Lastly, you'll end up back in the horrible land of static partitioning schemes with questionable tooling. Why suffer through that if you do not have to?
- Elhana 10y agoZFS don't really need ECC that much, just FUD. Most likely someone got bitten by faulty RAM, got corrupted data, which stopped after getting ECC RAM. => "ZFS wants ECC" myth, but in reality you just need stable hardware. At the same time, if you are running like 30-40 TB pool, you probably want that ECC RAM, it will cost only small fraction of total storage box price and will save you from rebuilding a pool if shit happens.
- wstrange 10y agoIt's not so much that ZFS needs ECC anymore than any other filesystem, but rather when you do have RAM errors, you are going to find out very quickly. Other filesystems will happily let you write corrupt data blocks...
- erkkie 10y agoSee my other comment a bit up in the thread. ZFS does data checksumming which relies on the ram not lying to you.
- the_why_of_y 10y agoBut at least with ZFS checksums you have a statistical chance of detecting bad RAM because it will sometimes manifest as checksum errors, whereas with non-checksumming filesystems you just get silent data corruption.
- __jal 10y agoI don't know about anyone else, but when I'm seeking advice about software from people on the internet whom I don't know personally, I tend to weight the words of the authors of the software in question more highly than that of people who didn't write it. There are probably exceptions to that I'm currently forgetting. And the authors of ZFS, from the Sun days on, have been consistently and repeatedly saying that if you care about your data, use ECC. I personally don't get why people seem so resistant to using ECC. It isn't that much more expensive and we know these errors happen in around 8% of DIMMS[1]. It reminds me of people I know who refuse to buy a decent power supply and then complain about hardware failures because of shoddy power. Personally, paying a slight premium to avoid an almost one in 10 likelihood of silent data corruption seems like a no-brainer to me. But then, I care about my data. Edit: to be clear, ZFS will perform less dangerously with non-ECC ram than a filesystem that doesn't checksum with non-ECC, because it will detect Bad Things happening and tell you about it. ECC helps avoid the problems in the first place. [1] http://research.google.com/pubs/pub35162.html http://research.google.com/pubs/pub35162.html
- barrkel 10y agoI don't think I've seen ZFS use much more than a single core. Apart from it being left over from upgrading desktop machines, I put that CPU in in there for video transcoding. It's well worth while creating a bunch of sub-filesystems (something ZFS makes really easy) with different settings: block sizes, compression, etc. - and copying sample data to it, to tune things in. The defaults are not necessarily a good fit for everybody. There's no reason not to turn on lz4 compression, for example. If you create zvols for use with different filesystems or sharing out over iSCSI, watch out for 100+% space consumption (e.g. 500G volume takes up 1+T space out of the pool, which is more than you would expect even with 8+2 raid overhead). I understand it relates to block vs stripe mismatch. This makes it a little less handy for things like virtual machine backing store than I had originally hoped.
- bogomipz 10y agoI think the ECC myth has long ago been debunked no?
- erkkie 10y agoThe ECC myth?
- awqrre 10y agoIssues related to not having ECC RAM are rare but if they happen, you might not notice the corrupted data, unless you try to access it.
- coolspot 10y agoWow! That is a lot of porn!