Colin Raven wrote:
Hi all!
I've decided to take the "big jump" and build a ZFS home filer (although it might also do "other work" like caching DNS, mail, usenet, bittorent and so forth). YAY! I wonder if anyone can shed some light on how long a pool scrub would take on a fairly decent rig. These are the specs as-ordered:

Asus P5Q-EM mainboard
Core2 Quad 2.83 GHZ
8GB DDR2/80

On this system (Dual core Athlon64 4600+ 2.4GHz, 8GB ram), 7200RPM enterprise duty disks, it takes about 14 hours on the following zpool:

# zpool status
 pool: export
state: ONLINE
status: The pool is formatted using an older on-disk format.  The pool can
   still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
   pool will no longer be accessible on older software versions.
scrub: scrub completed after 13h45m with 0 errors on Fri Nov 20 15:05:20 2009
config:

   NAME        STATE     READ WRITE CKSUM
   export      ONLINE       0     0     0
     mirror-0  ONLINE       0     0     0
       c3d0    ONLINE       0     0     0
       c2d0    ONLINE       0     0     0

errors: No known data errors
# zpool list
NAME     SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
export   930G   503G   427G    54%  ONLINE  -
#

OS:
2 x SSD's in RAID 0 (brand/size not decided on yet, but they will definitely be some flavor of SSD)

Can only be RAID1 (mirrored) for the OS.

Data:
4 x 1TB Samsung Spin Point 7200 RPM 32MB cache SATA HD's (RAIDZ)

Prefer mirrors myself, but depends on how much data you have verses how much disk you can afford.

Data payload initially will be around 550GB or so, (before loading any stuff from another NAS and so on)

Does scrub like memory, or CPU, or both? There's enough horsepower available, I would think. Same question applies to resilvering if I need to swap out drives at some point. [cough] I can't wait to get this thing built! :)

I also use the system as a desktop now (after doing some system consolidation). Scrub doesn't use much CPU, but it does interfere with the interactive response of the desktop. I suspect this is due to the i/o's it queues up on the disks.

--
Andrew
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to