On 01/04/2010 02:01, Charles Hedrick wrote:
So we tried recreating the pool and sending the data again.
1) compression wasn't set on the copy, even though I did sent -R, which is
supposed to send all properties
2) I tried killing to send | receive pipe. Receive couldn't be killed. It hung.
3) This is Solaris Cluster. We tried forcing a failover. The pool mounted on
the other server without dismounting on the first. zpool list showed it mounted
on both machines. zpool iostat showed I/O actually occurring on both systems.
Altogether this does not give me a good feeling about ZFS. I'm hoping the
problem is just with receive and CLuster, and the it works properly on a single
system. Because i'm running a critical database on ZFS on another system.
1. you shouldn't allow for a pool to be imported on more than one node
at a time, if you do you will probably loose entire pool
2. if you have a pool under a cluster control and you want to manually
import make sure that you do it in such an order:
- disable hastorageplus resource which manages the pool
- suspend a resource group so cluster won't start a storage
resource in any event
- manually import a pool and do whatever you need to do with it -
however to be on a safe side import it with -R / option so if your node
would reboot for some reason the pool won't be automatically imported
- after you are done with whatever you wanted to do make sure you
export the pool, resume the resource group and enable the storage resource
The other approach is to keep a pool under a cluster management but
eventually suspend a resource group so there won't be any unexpected
failovers (but it really depends on circumstances and what you are
trying to do).
--
Robert Milkowski
http://milek.blogspot.com
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
