> On Fri, Oct 15, 2010 at 3:16 PM, Marty Scholes > <martyscho...@yahoo.com> wrote: > > My home server's main storage is a 22 (19 + 3) disk > RAIDZ3 pool backed up hourly to a 14 (11+3) RAIDZ3 > backup pool. > > How long does it take to resilver a disk in that > pool? And how long > does it take to run a scrub? > > When I initially setup a 24-disk raidz2 vdev, it died > trying to > resilver a single 500 GB SATA disk. I/O under 1 > MBps, all 24 drives > thrashing like crazy, could barely even login to the > system and type > onscreen. It was a nightmare. > > That, and normal (no scrub, no resilver) disk I/O was > abysmal. > > Since then, I've avoided any vdev with more than 8 > drives in it.
MY situation is kind of unique. I picked up 120 15K 73GB FC disks early this year for $2 per. As such, spindle count is a non-issue. As a home server, it has very little need for write iops and I have 8 disks for L2ARC on the main pool. Main pool is at 40% capacity and backup pool is at 65% capacity. Both take about 70 minutes to scrub. The last time I tested a resilver it took about 3 hours. The difference is that these are low capacity 15K FC spindles and the pool has very little sustained I/O; it only bursts now and again. Resilvers would go mostly uncontested, and with RAIDZ3 + autoreplace=off, I can actually schedule a resilver. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
