Hello Joseph,

Monday, April 2, 2007, 9:42:24 PM, you wrote:

JB> I have a couple of questions:

JB> 1.)
JB> I am working with an v240 IMAP server that is currently set up with 3 zfs
JB> pools, one (conf-pool) on the internal disks, and two (email-pool, and
JB> email1-pool) that are spread across 12 disks in an attached JBOD like so:

JB>    pool: email-pool
JB>   state: ONLINE
JB> config:
JB>          NAME         STATE     READ WRITE CKSUM
JB>          email-pool   ONLINE       0     0     0
JB>            mirror     ONLINE       0     0     0
JB>              c0t1d0   ONLINE       0     0     0
JB>              c0t9d0   ONLINE       0     0     0
JB>            mirror     ONLINE       0     0     0
JB>              c0t2d0   ONLINE       0     0     0
JB>              c0t10d0  ONLINE       0     0     0
JB>            mirror     ONLINE       0     0     0
JB>              c0t3d0   ONLINE       0     0     0
JB>              c0t11d0  ONLINE       0     0     0
JB>            mirror     ONLINE       0     0     0
JB>              c0t4d0   ONLINE       0     0     0
JB>              c0t12d0  ONLINE       0     0     0

JB>    pool: email1-pool
JB>   state: ONLINE
JB> config:
JB>          NAME         STATE     READ WRITE CKSUM
JB>          email1-pool  ONLINE       0     0     0
JB>            mirror     ONLINE       0     0     0
JB>              c0t5d0   ONLINE       0     0     0
JB>              c0t13d0  ONLINE       0     0     0
JB>            mirror     ONLINE       0     0     0
JB>              c0t6d0   ONLINE       0     0     0
JB>              c0t14d0  ONLINE       0     0     0

JB> We are planning on migrating everything over to email-pool eventually, but
JB> for now that's what I'm working with.

JB> I currently have a script that runs every night at midnight to create 
JB> full/normal snapshots of the various filesystems on the two pools so we can
JB> do backups.  The script also renames and deletes snapshots such that I
JB> always have the last two week's worth of snapshots.  Also, email-pool has
JB> 26 file systems (one per letter), and email1-pool has just 1.

JB> So, normally, when the script runs, all snapshots finish in maybe a minute
JB> total.  However, on Sundays, it continues to take longer and longer.   On
JB> 2/25 it took 30 minutes, and this last Sunday, it took 2:11.  The only
JB> thing special thing about Sunday's snapshots is that they are the first
JB> ones created since the full backup (using NetBackup) on Saturday. All
JB> other backups are incrementals.

hmmmmm do you have atime property set to off?
Maybe you spend most of the time in destroying snapshots due to much
larger delta coused by atime updates? You can possibly also gain some
performance by setting atime to off.



JB> 2.)
JB> Possibly related to the above, I've found that my zfs tools have been 
JB> patched/upgraded, and now zpool status says I can/should upgrade. zpool
JB> upgrade shows the following:

JB>      -bash-3.00$ zpool upgrade
JB>      This system is currently running ZFS version 3.

JB>      The following pools are out of date, and can be upgraded.  After being
JB>      upgraded, these pools will no longer be accessible by older software
JB>      versions.

JB>      VER  POOL
JB>      ---  ------------
JB>       2   conf-pool
JB>       2   email-pool
JB>       2   email1-pool

JB> I've looked a bit, and can't find anything that tells me if there will be
JB> any sort of a hit on my performance if I upgrade the pools.  I'm especially
JB> cautious as this is our production email server.  Will an upgrade cause
JB> load/performance problems?  Will I need to take down the IMAP server while
JB> I do this?  Also, the whole 'older software versions' mentioned above: what
JB> is the older software I'd have to worry about?  Just the ZFS tools?  If the
JB> array is staying on this server, do I even have to worry about this? I'm
JB> running a patched 2006/06 OS.

It's about zfs on-disk format.
By doing upgrade it won't issue any significant number of IOs (should
complete in a second or so). It won't hit performance but it will add
new features like hot spare support (in version 3) or proper disk
space accounting for raid-z* file systems (but they have to be
re-created).

There's nothing to worry about upgrade and of course you can do it
online without stopping applications. However once you upgrade you
won't be able to import version 3 pool on older systems with version 2
only support (so basically you won't be able to import on S10U2).
So once you're sure that system is working correctly for some time after 
applying
last patches you can safely upgrade.



-- 
Best regards,
 Robert                            mailto:[EMAIL PROTECTED]
                                       http://milek.blogspot.com

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

Reply via email to