Weia. Neue #hdd eingebaut, #resilver vom #zfs gestartet. Binja mal gespannt, ab wann die Angabe, wie lange es noch braucht, halbwegs stabil bleibt.

Fing an mit über 3 Tagen Restzeit. Nach nun knapp 1.2% (eins PUNKT zwei, nicht 12!) erledigt sehen wir noch 18 Stunden Restzeit.

(Nach 2.21% sinds noch 11:52 Stunden)

Lt. iotop Total Disk Read zwischen 900 und 1400 M/s - heissa, soviel ist sonst nie los. 😁

After almost 8 years of use (64613 power on hours) this bad boy finally gave up the ghost #homelab #bad_hdd #westerndigital Manufactured 26/09/2016 so I feel it delivered value. No data lost #zfs and a #resilver in progress

lesson learned on raid array grow - probably much faster to just move all data off your array, part and format all disks, make new array and then add all data back on rather than trying to grow/resize but i did not have removable drive big enough or enough space on other machines so - doing new things allows one to gain appreciation #resilver

The joys of summer #homelab #zfs #resilver

New 𝗭𝗙𝗦 𝗥𝗲𝘀𝗶𝗹𝘃𝗲𝗿 𝗼𝗻 𝗦𝗠𝗥 𝗗𝗿𝗶𝘃𝗲𝘀 (ZFS Resilver on SMR Drives) article on vermaden.wordpress.com blog.

https://vermaden.wordpress.com/2024/05/29/zfs-resilver-smr-drives/

#data #freebsd #linux #nas #openzfs #resilver #server #storage #truenas #zfs

@zirias

@parvXtl

One of the ways I help avoid failures with raidz1 is by replacing HDD when they get to around 5 years old, or they start showing errors. Also, monthly scrubs helps ensure that the drives are getting fully utilized regularly which helps keep things healthy/accelerate detection of failures.

#resilver #FreeBSD #RAID #ZFS #raidz1 #backup

@david_chisnall My pool isn't for a NAS but basically for "everything" I need, which includes serving files, but lots of other things (routing, firewall, internal MTA with mail storage, building base and ports, a windows server 2020 for work, and so on ...). Of course I avoid IO-heavy stuff during resilver, but it's still a busy machine, so I guess a "balanced" default tuning is actually what I want 😉

Thanks for explaining how ETA of #ZFS #resilver ends up so "random" 👍

For whatever reason, #resilver on my #FreeBSD server slowed down continuously, an initial ETA showed around 4 hours, by the time I left my desktop, it already showed around 10 hours. But hey, it finished without errors, so, all fine 😅

BTW, I really don't get why recently, you read a lot of stuff about how #RAID-5 (or the #ZFS equivalent #raidz1) was super dangerous and you should never use it 🫨

What's certainly true is: With larger pools and larger individual disks, the risk of a second disk failure during resilver significantly increases. But then, there's no "risk-free" storage, so a #backup is always a *must*.

What's also true is, raid-5/raidz1 is still the rendundancy scheme with the least storage overhead for most scenarios (3 and more disks). And of course it still reduces the risk of a failed pool. This pool here has only one of its original disks left, I didn't need my backup so far. 🤷

So please move the discussion of RAID back to a sensible base. The scheme/level you choose is always a trade-off between the cost (overhead) and the amount of risk reduction, and that's pretty much all there is....

I love my zfs of hot-pluggable SAS disks. A disk failed? No problem. Detach, physically replace and wait for the "resilver" magic. All while a time-machine and an "rsnapshot" backup are actively going on. And the disk array could even tolerate a second disk failure during reconstruction.
(resilvering starts slow, but will pick up more speed ...)
#selfhosting #SAS #scsi #zfs #raidz2 #NetBSD #backup #resilver

Puh, nach meinem Plattenausfall vom Server am Wochenende, resilver Prozess erfolgreich nach 12 Stunden Laufzeit abgeschlossen. Yippie. #hobbyadmin #truenas #festplattenausfall #resilver