# Doh.. Looks like hardware failure coming up!

**URL:** <https://forum.storj.io/t/doh-looks-like-hardware-failure-coming-up/16181>\
**Category:** Node Operators\
**Created:** [November 19, 2021, 4:03pm UTC](https://forum.storj.io/t/doh-looks-like-hardware-failure-coming-up/16181 "2021-11-19T16:03:00Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 20, 2021, 9:12am UTC](https://forum.storj.io/t/doh-looks-like-hardware-failure-coming-up/16181/9 "2021-11-20T09:12:27Z")

</div>

> [@SGC](#):
>
> i will never use a non checksum file system again, thats for sure

It makes sense only in RAID configurations, otherwise it’s slower than ext4 in 6 times (the simple single disk zfs and the same disk ext4).  
Unfortunately in my tests with default options for raidz and LVM parity volumes I received not good results. On the same hardware and disks the raidz (3 disks) is slower than LVM parity (the same 3 disks and 3 columns) in 5 (!) times for the rsync and a continuous 1G and 2G files 😕  
I tested it 3 times cleaning env before the next test, the difference in results is less than 1%

---

_[View the full topic](https://forum.storj.io/t/doh-looks-like-hardware-failure-coming-up/16181)._