Hi all,
I have defined a zfs pool on a Solaris 10 :
root at suntzu:/kernel/drv> zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
nsrcatalog 125G 72.7G 52.4G 58% ONLINE -
root at suntzu:/kernel/drv> zpool status nsrcatalog
pool: nsrcatalog
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
nsrcatalog ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd0 ONLINE 0 0 0
c6t5005076307034352d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd1 ONLINE 0 0 0
c6t5005076307034352d1 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd2 ONLINE 0 0 0
c6t5005076307034352d2 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd3 ONLINE 0 0 0
c6t5005076307034352d3 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd4 ONLINE 0 0 0
c6t5005076307034352d4 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd5 ONLINE 0 0 0
c6t5005076307034352d5 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t500507630708433Bd6 ONLINE 0 0 0
c6t5005076307034352d6 ONLINE 0 0 0
errors: No known data errors
I would now like to use mpxio - multipathing driver. So, i will change
the file /kernel/drv/fp.conf and set the parameter mpxio-disable="no";
But, I thing Solaris will change after a reboot the device name !!. What
will be the status of my zpool after the reboot. Do I have to redefine
it ?
How can I preserve data on it ?
Thanks a lot for your help.
Kind regards.
Pierre.
-----------------------------------------
Visit our website! http://www.nbb.be
"DISCLAIMER: The content of this e-mail message should not be
construed as binding on the part of the National Bank of Belgium
(NBB) unless otherwise and previously stated. The opinions
expressed in this message are solely those of the author and do not
necessarily reflect NBB viewpoints, particularly when the content
of this message, or part thereof, is private by nature or does not
fall within the professional scope of its author."
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080818/e978a514/attachment.html>
On Mon, Aug 18, 2008 at 04:43:02PM +0200, Dony Pierre wrote:> > I have defined a zfs pool on a Solaris 10 : > > I would now like to use mpxio - multipathing driver. So, i will change > the file /kernel/drv/fp.conf and set the parameter mpxio-disable="no"; > > But, I thing Solaris will change after a reboot the device name !!. > What will be the status of my zpool after the reboot. Do I have to > redefine it ? > > How can I preserve data on it ?We''ve done the same thing with ZFS on Iscsi devices. Once we set up the second path, we exported the pool. Then, we enabled mpxio and imported the pool again. `zpool import'' will show the new device names, but you only need to specify the pool name. It worked perfectly. -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
James C. McPherson
2008-Aug-18 20:49 UTC
[zfs-discuss] Zfs and mpxio - device name changed
Dony Pierre wrote:> > Hi all, > > I have defined a zfs pool on a Solaris 10 : > > root at suntzu:/kernel/drv> zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > nsrcatalog 125G 72.7G 52.4G 58% ONLINE - > > root at suntzu:/kernel/drv> zpool status nsrcatalog > pool: nsrcatalog > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > nsrcatalog ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd0 ONLINE 0 0 0 > c6t5005076307034352d0 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd1 ONLINE 0 0 0 > c6t5005076307034352d1 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd2 ONLINE 0 0 0 > c6t5005076307034352d2 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd3 ONLINE 0 0 0 > c6t5005076307034352d3 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd4 ONLINE 0 0 0 > c6t5005076307034352d4 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd5 ONLINE 0 0 0 > c6t5005076307034352d5 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd6 ONLINE 0 0 0 > c6t5005076307034352d6 ONLINE 0 0 0 > > errors: No known data errors > > I would now like to use mpxio - multipathing driver. So, i will change > the file /kernel/drv/fp.conf and set the parameter mpxio-disable="no"; > > But, I thing Solaris will change after a reboot the device name !!. What > will be the status of my zpool after the reboot. Do I have to redefine it ? > > How can I preserve data on it ?Yes, the cXtYdZ paths will change. You don''t even need to export and import the pool, ZFS looks at the devid (device id) of each disk in your pool in preference to a device path - if the devid doesn''t change (and it shouldn''t!), then there''s no issue at all. I strongly advise you to use the stmsboot(1m) command to handle the enabling of MPxIO. Otherwise your system might not boot - there are a few niggly little things that stmsboot(1m) does for you which you might not do by yourself. If you''d like more information on devids, please have a look at my presentation on the concept: http://www.jmcp.homeunix.com/~jmcp/WhatIsAGuid.pdf James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
James, Thanks a lot for your answer and for your presentation. I will read it before making the activation of mpxio. Thanks ! Kind regards. Pierre. -----Original Message----- From: James.McPherson at Sun.COM [mailto:James.McPherson at Sun.COM] Sent: maandag 18 augustus 2008 22:49 To: Dony Pierre Cc: zfs-discuss at opensolaris.org Subject: Re: [zfs-discuss] Zfs and mpxio - device name changed Dony Pierre wrote:> > Hi all, > > I have defined a zfs pool on a Solaris 10 : > > root at suntzu:/kernel/drv> zpool list > NAME SIZE USED AVAIL CAP HEALTHALTROOT> nsrcatalog 125G 72.7G 52.4G 58% ONLINE - > > root at suntzu:/kernel/drv> zpool status nsrcatalog > pool: nsrcatalog > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > nsrcatalog ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd0 ONLINE 0 0 0 > c6t5005076307034352d0 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd1 ONLINE 0 0 0 > c6t5005076307034352d1 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd2 ONLINE 0 0 0 > c6t5005076307034352d2 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd3 ONLINE 0 0 0 > c6t5005076307034352d3 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd4 ONLINE 0 0 0 > c6t5005076307034352d4 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd5 ONLINE 0 0 0 > c6t5005076307034352d5 ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7t500507630708433Bd6 ONLINE 0 0 0 > c6t5005076307034352d6 ONLINE 0 0 0 > > errors: No known data errors > > I would now like to use mpxio - multipathing driver. So, i will change> the file /kernel/drv/fp.conf and set the parameter mpxio-disable="no"; > > But, I thing Solaris will change after a reboot the device name !!.What> will be the status of my zpool after the reboot. Do I have to redefineit ?> > How can I preserve data on it ?Yes, the cXtYdZ paths will change. You don''t even need to export and import the pool, ZFS looks at the devid (device id) of each disk in your pool in preference to a device path - if the devid doesn''t change (and it shouldn''t!), then there''s no issue at all. I strongly advise you to use the stmsboot(1m) command to handle the enabling of MPxIO. Otherwise your system might not boot - there are a few niggly little things that stmsboot(1m) does for you which you might not do by yourself. If you''d like more information on devids, please have a look at my presentation on the concept: http://www.jmcp.homeunix.com/~jmcp/WhatIsAGuid.pdf James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog ----------------------------------------- Visit our website! http://www.nbb.be "DISCLAIMER: The content of this e-mail message should not be construed as binding on the part of the National Bank of Belgium (NBB) unless otherwise and previously stated. The opinions expressed in this message are solely those of the author and do not necessarily reflect NBB viewpoints, particularly when the content of this message, or part thereof, is private by nature or does not fall within the professional scope of its author."