zfs discuss - Mar 2012 - Advice for migrating ZFS configuration

Hi,

I had a single-disk zpool (export) and was given two new disks for expanded
storage. All three disks are identically sized, no slices/partitions. My goal is
to create a raidz1 configuration of the three disks, containing the data in the
original zpool.

However, I got off on the wrong foot by doing a "zpool add" of the
first disk. Apparently this has simply increased my storage without creating a
raidz config.

Unfortunately, there appears to be no simple way to just remove that disk now
and do a proper raidz create of the other two. Nor am I clear on how
import/export works and whether that''s a good way to copy content from
one zpool to another on a single host.

Can somebody guide me? What''s the easiest way out of this mess, so that
I can move from what is now a simple two-disk zpool (less than 50% full) to a
three-disk raidz configuration, starting with one unused disk? In the end I want
the three-disk raidz to have the same name (and mount point) as the original
zpool. There must be an easy way to do this.

Thanks for any assistance.

-Bob

P.S. I would appreciate being kept on the CC list for this thread to avoid
digest mailing delays.

IMHO, there is no easy way out for you
1)tape backup and restore
2)find a larger USB SATA disk, copy the data over then restore later 
after raidz1 setup
-LT


On 3/7/2012 4:38 PM, Bob Doolittle wrote:
> Hi,
>
> I had a single-disk zpool (export) and was given two new disks for 
> expanded storage. All three disks are identically sized, no 
> slices/partitions. My goal is to create a raidz1 configuration of the 
> three disks, containing the data in the original zpool.
>
> However, I got off on the wrong foot by doing a "zpool add" of
the
> first disk. Apparently this has simply increased my storage without 
> creating a raidz config.
>
> Unfortunately, there appears to be no simple way to just remove that 
> disk now and do a proper raidz create of the other two. Nor am I clear 
> on how import/export works and whether that''s a good way to copy 
> content from one zpool to another on a single host.
>
> Can somebody guide me? What''s the easiest way out of this mess, so
> that I can move from what is now a simple two-disk zpool (less than 
> 50% full) to a three-disk raidz configuration, starting with one 
> unused disk? In the end I want the three-disk raidz to have the same 
> name (and mount point) as the original zpool. There must be an easy 
> way to do this.
>
> Thanks for any assistance.
>
> -Bob
>
> P.S. I would appreciate being kept on the CC list for this thread to 
> avoid digest mailing delays.
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
-- 
Hung-Sheng Tsao Ph D.
Founder&  Principal
HopBit GridComputing LLC
cell: 9734950840

http://laotsao.blogspot.com/
http://laotsao.wordpress.com/
http://blogs.oracle.com/hstsao/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: laotsao.vcf
Type: text/x-vcard
Size: 608 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20120307/6b54752d/attachment.vcf>

On Thu, Mar 8, 2012 at 4:38 AM, Bob Doolittle <Bob.Doolittle at
oracle.com> wrote:
> Hi,
>
> I had a single-disk zpool (export) and was given two new disks for expanded
> storage. All three disks are identically sized, no slices/partitions. My
> goal is to create a raidz1 configuration of the three disks, containing the
> data in the original zpool.
>
> However, I got off on the wrong foot by doing a "zpool add" of
the first
> disk. Apparently this has simply increased my storage without creating a
> raidz config.
IIRC you can''t convert a single-disk (or striped) pool to raidz. You
can  only convert it to mirror. So even your intended approach (you
wanted to try "zpool attach"?) was not appropriate.
>
> Unfortunately, there appears to be no simple way to just remove that disk
> now and do a proper raidz create of the other two. Nor am I clear on how
> import/export works and whether that''s a good way to copy content
from one
> zpool to another on a single host.
>
> Can somebody guide me? What''s the easiest way out of this mess, so
that I
> can move from what is now a simple two-disk zpool (less than 50% full) to a
> three-disk raidz configuration, starting with one unused disk?
- use the one new disk to create a temporary pool
- copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
- destroy old pool
- create a three-disk raidz pool using two disks and a fake device,
something like http://www.dev-eth0.de/creating-raidz-with-missing-device/
- destroy the temporary pool
- replace the fake device with now-free disk
- export the new pool
- import the new pool and rename it in the process: "zpool import
temp_pool_name old_pool_name"
> In the end I
> want the three-disk raidz to have the same name (and mount point) as the
> original zpool. There must be an easy way to do this.
Nope.

-- 
Fajar

Hi Bob,

Not many options because you can''t attach disks to convert a
non-redundant pool to a RAIDZ pool.

To me, the best solution is to get one more disk (for a total of 4
disks) to create a mirrored pool. Mirrored pools provide more
flexibility. See 1 below.

See the options below.

Thanks,

Cindy

1. Convert this pool to a mirrored pool by using 4 disks. If your
existing export pool looks like this:

# zpool status export
   pool: export
  state: ONLINE
   scan: none requested
config:

         NAME                     STATE     READ WRITE CKSUM
         export                   ONLINE       0     0     0
           disk1                  ONLINE       0     0     0
           disk2                  ONLINE       0     0     0

Then, attach the additional 2 disks:

# zpool attach export disk1 disk3
# zpool attach export disk2 disk4

2. Borrow a couple of disks to temporarily create a pool (export1),
copy over the data from export, destroy export, and rebuild export
as a 3-disk RAIDZ pool. Then, copy over the data to export, destroy
export1, and you can have the same export mount points.




On 03/07/12 14:38, Bob Doolittle wrote:
> Hi,
>
> I had a single-disk zpool (export) and was given two new disks for
> expanded storage. All three disks are identically sized, no
> slices/partitions. My goal is to create a raidz1 configuration of the
> three disks, containing the data in the original zpool.
>
> However, I got off on the wrong foot by doing a "zpool add" of
the first
> disk. Apparently this has simply increased my storage without creating a
> raidz config.
>
> Unfortunately, there appears to be no simple way to just remove that
> disk now and do a proper raidz create of the other two. Nor am I clear
> on how import/export works and whether that''s a good way to copy
content
> from one zpool to another on a single host.
>
> Can somebody guide me? What''s the easiest way out of this mess, so
that
> I can move from what is now a simple two-disk zpool (less than 50% full)
> to a three-disk raidz configuration, starting with one unused disk? In
> the end I want the three-disk raidz to have the same name (and mount
> point) as the original zpool. There must be an easy way to do this.
>
> Thanks for any assistance.
>
> -Bob
>
> P.S. I would appreciate being kept on the CC list for this thread to
> avoid digest mailing delays.
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On 08 March, 2012 - Fajar A. Nugraha sent me these 1,9K bytes:
> > Can somebody guide me? What''s the easiest way out of this
mess, so that I
> > can move from what is now a simple two-disk zpool (less than 50% full)
to a
> > three-disk raidz configuration, starting with one unused disk?
> 
> - use the one new disk to create a temporary pool
> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
> - destroy old pool
> - create a three-disk raidz pool using two disks and a fake device,
> something like http://www.dev-eth0.de/creating-raidz-with-missing-device/
.. copy data from temp to new pool, quite important step ;)
> - destroy the temporary pool
> - replace the fake device with now-free disk
> - export the new pool
> - import the new pool and rename it in the process: "zpool import
> temp_pool_name old_pool_name"
/Tomas
-- 
Tomas Forsman, stric at acc.umu.se, http://www.acc.umu.se/~stric/
|- Student at Computing Science, University of Ume?
`- Sysadmin at {cs,acc}.umu.se

Perfect, thanks. Just what I was looking for.

How do I know how large to make the "fakedisk" file? Any old
"enormous" size will do, since mkfile -n doesn''t actually
allocate the blocks until needed?

To be sure I understand correctly: In theory, instead of this missing disk
approach I could create a two-disk raidz pool and later add the third disk to
it, right? Your method looks much more efficient however so thanks.

It''s too bad we can''t change a 1-volume zpool to raidz before
or while adding disks. That would make this much easier.

Regards,
     Bob

On 03/07/12 17:03, Fajar A. Nugraha wrote:
> On Thu, Mar 8, 2012 at 4:38 AM, Bob Doolittle<Bob.Doolittle at
oracle.com>  wrote:
>> Hi,
>>
>> I had a single-disk zpool (export) and was given two new disks for
expanded
>> storage. All three disks are identically sized, no slices/partitions.
My
>> goal is to create a raidz1 configuration of the three disks, containing
the
>> data in the original zpool.
>>
>> However, I got off on the wrong foot by doing a "zpool add"
of the first
>> disk. Apparently this has simply increased my storage without creating
a
>> raidz config.
> IIRC you can''t convert a single-disk (or striped) pool to raidz.
You
> can  only convert it to mirror. So even your intended approach (you
> wanted to try "zpool attach"?) was not appropriate.
>
>> Unfortunately, there appears to be no simple way to just remove that
disk
>> now and do a proper raidz create of the other two. Nor am I clear on
how
>> import/export works and whether that''s a good way to copy
content from one
>> zpool to another on a single host.
>>
>> Can somebody guide me? What''s the easiest way out of this
mess, so that I
>> can move from what is now a simple two-disk zpool (less than 50% full)
to a
>> three-disk raidz configuration, starting with one unused disk?
> - use the one new disk to create a temporary pool
> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
> - destroy old pool
> - create a three-disk raidz pool using two disks and a fake device,
> something like http://www.dev-eth0.de/creating-raidz-with-missing-device/
> - destroy the temporary pool
> - replace the fake device with now-free disk
> - export the new pool
> - import the new pool and rename it in the process: "zpool import
> temp_pool_name old_pool_name"
>
>> In the end I
>> want the three-disk raidz to have the same name (and mount point) as
the
>> original zpool. There must be an easy way to do this.
> Nope.
>

Wait, I''m not following the last few steps you suggest. Comments
inline:

On 03/07/12 17:03, Fajar A. Nugraha wrote:
> - use the one new disk to create a temporary pool
> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
> - destroy old pool
> - create a three-disk raidz pool using two disks and a fake device,
> something like http://www.dev-eth0.de/creating-raidz-with-missing-device/
Don''t I need to copy the data back from the temporary pool to the new
raidz pool at this point?
I''m not understanding the process beyond this point, can you clarify
please?
> - destroy the temporary pool
So this leaves the data intact on the disk?
> - replace the fake device with now-free disk
So this replicates the data on the previously-free disk across the raidz pool?

What''s the point of the following export/import steps? Renaming? Why
can''t I just give the old pool name to the raidz pool when I create it?
> - export the new pool
> - import the new pool and rename it in the process: "zpool import
> temp_pool_name old_pool_name"
Thanks!

-Bob

>
>> In the end I
>> want the three-disk raidz to have the same name (and mount point) as
the
>> original zpool. There must be an easy way to do this.
> Nope.
>

> In theory, instead of this missing
 > disk approach I could create a two-disk raidz pool and later add the
 > third disk to it, right?

No, you can''t add a 3rd disk to an existing RAIDZ vdev of two disks.
You would want to add another 2 disk RAIDZ vdev.

See Example 4-2 in this section:

http://docs.oracle.com/cd/E23823_01/html/819-5461/gayrd.html#gazgw

Adding Disks to a RAID-Z Configuration

This section describes what you can and can''t do with RAID-Z pools:

http://docs.oracle.com/cd/E23823_01/html/819-5461/gaypw.html#gcvjg

cs

On 03/07/12 15:41, Bob Doolittle wrote:
> Perfect, thanks. Just what I was looking for.
>
> How do I know how large to make the "fakedisk" file? Any old
"enormous"
> size will do, since mkfile -n doesn''t actually allocate the blocks
until
> needed?
>
> To be sure I understand correctly: In theory, instead of this missing
> disk approach I could create a two-disk raidz pool and later add the
> third disk to it, right? Your method looks much more efficient however
> so thanks.
>
> It''s too bad we can''t change a 1-volume zpool to raidz
before or while
> adding disks. That would make this much easier.
>
> Regards,
> Bob
>
> On 03/07/12 17:03, Fajar A. Nugraha wrote:
>> On Thu, Mar 8, 2012 at 4:38 AM, Bob
>> Doolittle<Bob.Doolittle at oracle.com> wrote:
>>> Hi,
>>>
>>> I had a single-disk zpool (export) and was given two new disks for
>>> expanded
>>> storage. All three disks are identically sized, no
slices/partitions. My
>>> goal is to create a raidz1 configuration of the three disks,
>>> containing the
>>> data in the original zpool.
>>>
>>> However, I got off on the wrong foot by doing a "zpool
add" of the first
>>> disk. Apparently this has simply increased my storage without
creating a
>>> raidz config.
>> IIRC you can''t convert a single-disk (or striped) pool to
raidz. You
>> can only convert it to mirror. So even your intended approach (you
>> wanted to try "zpool attach"?) was not appropriate.
>>
>>> Unfortunately, there appears to be no simple way to just remove
that
>>> disk
>>> now and do a proper raidz create of the other two. Nor am I clear
on how
>>> import/export works and whether that''s a good way to copy
content
>>> from one
>>> zpool to another on a single host.
>>>
>>> Can somebody guide me? What''s the easiest way out of this
mess, so
>>> that I
>>> can move from what is now a simple two-disk zpool (less than 50%
>>> full) to a
>>> three-disk raidz configuration, starting with one unused disk?
>> - use the one new disk to create a temporary pool
>> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
>> - destroy old pool
>> - create a three-disk raidz pool using two disks and a fake device,
>> something like
http://www.dev-eth0.de/creating-raidz-with-missing-device/
>> - destroy the temporary pool
>> - replace the fake device with now-free disk
>> - export the new pool
>> - import the new pool and rename it in the process: "zpool import
>> temp_pool_name old_pool_name"
>>
>>> In the end I
>>> want the three-disk raidz to have the same name (and mount point)
as the
>>> original zpool. There must be an easy way to do this.
>> Nope.
>>
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

read the link please
it seems that afmter you create the  radiz1 zpool
you need to destroy the fakedisk so it will have contains data when you to the
copy
copy the data by following the steps in the link

replace the  fakedisk withnthe real disk

this is a good approach that i did not know before
-LT

Sent from my iPad

On Mar 7, 2012, at 17:48, Bob Doolittle <Bob.Doolittle at oracle.com>
wrote:
> Wait, I''m not following the last few steps you suggest. Comments
inline:
> 
> On 03/07/12 17:03, Fajar A. Nugraha wrote:
>> - use the one new disk to create a temporary pool
>> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
>> - destroy old pool
>> - create a three-disk raidz pool using two disks and a fake device,
>> something like
http://www.dev-eth0.de/creating-raidz-with-missing-device/
> 
> Don''t I need to copy the data back from the temporary pool to the
new raidz pool at this point?
> I''m not understanding the process beyond this point, can you
clarify please?
> 
>> - destroy the temporary pool
> 
> So this leaves the data intact on the disk?
> 
>> - replace the fake device with now-free disk
> 
> So this replicates the data on the previously-free disk across the raidz
pool?
> 
> What''s the point of the following export/import steps? Renaming?
Why can''t I just give the old pool name to the raidz pool when I create
it?
> 
>> - export the new pool
>> - import the new pool and rename it in the process: "zpool import
>> temp_pool_name old_pool_name"
> 
> Thanks!
> 
> -Bob
> 
> 
>> 
>>> In the end I
>>> want the three-disk raidz to have the same name (and mount point)
as the
>>> original zpool. There must be an easy way to do this.
>> Nope.
>> 
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On Thu, Mar 8, 2012 at 5:48 AM, Bob Doolittle <Bob.Doolittle at
oracle.com> wrote:
> Wait, I''m not following the last few steps you suggest. Comments
inline:
>
>
> On 03/07/12 17:03, Fajar A. Nugraha wrote:
>>
>> - use the one new disk to create a temporary pool
>> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
>> - destroy old pool
>> - create a three-disk raidz pool using two disks and a fake device,
>> something like
http://www.dev-eth0.de/creating-raidz-with-missing-device/
>
>
> Don''t I need to copy the data back from the temporary pool to the
new raidz
> pool at this point?
Yes, I missed it :)
That''s what you get for writing mail at 5 am :P
> I''m not understanding the process beyond this point, can you
clarify please?
>
>
>> - destroy the temporary pool
>
>
> So this leaves the data intact on the disk?
>
Destroy it after the data is copied back, of course.
>
>> - replace the fake device with now-free disk
>
>
> So this replicates the data on the previously-free disk across the raidz
> pool?
Not really.
The fake disk was never written cause it was destroyed soon after
created (see the link), so the pool was degraded. The replace process
tells zfs to use the new disk to make the pool not degraded anymore by
writing the necessary data (e.g. raidz parity, although this might not
be the most accurate way to describe it) to  the new disk.
>
> What''s the point of the following export/import steps? Renaming?
Yes
> Why can''t I
> just give the old pool name to the raidz pool when I create it?
Cause you can''t have two pools with the same name. You either need to
rename the old pool first, or rename the new pool afterwards.

-- 
Fajar

On 3/7/2012 9:04 PM, Fajar A. Nugraha wrote:
>> Why can''t I
>> just give the old pool name to the raidz pool when I create it?
> Cause you can''t have two pools with the same name. You either need
to
> rename the old pool first, or rename the new pool afterwards.
But in your instructions you have me destroying the old pool before 
creating the new raidz pool, so it seems I can create the new pool with 
the old name.
This means I don''t need the export/import at the end, doesn''t
it?

So I think the steps are:

- use the one new disk to create a temporary pool
- copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
- destroy old pool
- create a three-disk raidz pool (with the old pool name) using two disks and a
fake device,
something like http://www.dev-eth0.de/creating-raidz-with-missing-device/
- copy data to new pool from temp pool
- destroy the temporary pool
- replace the fake device with now-free disk


I think that''s it. Does this look right? I very much appreciate your 
assistance here. Kinda important to me that I get this right :-)

And thanks to Cindy. If I had another disk it would indeed be simpler to 
create two mirrors and add them together. But I had to pay in blood to 
even get these :-)

Thanks,
     Bob

On Thu, Mar 8, 2012 at 10:28 AM, Bob Doolittle <bob.doolittle at
oracle.com> wrote:
> On 3/7/2012 9:04 PM, Fajar A. Nugraha wrote:
>>>
>>> Why can''t I
>>> just give the old pool name to the raidz pool when I create it?
>>
>> Cause you can''t have two pools with the same name. You either
need to
>> rename the old pool first, or rename the new pool afterwards.
>
> But in your instructions you have me destroying the old pool before
creating
> the new raidz pool, so it seems I can create the new pool with the old
name.
You''re probably right :)
> This means I don''t need the export/import at the end,
doesn''t it?
Yup.
>
> So I think the steps are:
>
>
> - use the one new disk to create a temporary pool
> - copy the data ("zfs snapshot -r" + "zfs send -R | zfs
receive")
i''d probably add "verify that your data is copied and accessibe in
the
temp pool", just to be sure.
> - destroy old pool
> - create a three-disk raidz pool (with the old pool name) using two disks
> and a fake device,
> something like http://www.dev-eth0.de/creating-raidz-with-missing-device/
> - copy data to new pool from temp pool
... and here as well, "verify that your data is copied and accessibe
in the new pool", just to be sure.

>
> - destroy the temporary pool
> - replace the fake device with now-free disk
>
yup
>
> I think that''s it. Does this look right? I very much appreciate
your
> assistance here. Kinda important to me that I get this right :-)
-- 
Fajar

Lots of suggestions (not included here), but ...

    With the exception of Cindy''s suggestion of using 4 disks and
mirroring (zpool attach two new disks to existing vdevs), I would
absolutely NOT do anything unless I had a known good backup of the
data! I have seen too many cases described here on this list of people
trying complicated procedures with ZFS and making one small mistake
and loosing their data, or spending weeks or months trying to recover
it.

    Regarding IMPORT / EXPORT, these functions are have two real
purposes in my mind:

1. you want to move a zpool from one host to another. You EXPORT from
the first host, physically move the disks, then IMPORT on the new
host.

2. You want (or need) to physically change the connectivity between
the disks and the host, and implicit in that is that the device paths
will change. EXPORT, change connectivity, IMPORT. Once again I have
seen many cases described on this list of folks who moved disks
around, which ZFS is _supposed_ to handle, but then had a problem.

    I use ZFS first for reliability and second for performance. With
that in mind, one of my primary rules for ZFS is to NOT move disks
around without first exporting the zpool. I have done some pretty rude
things regarding devices underlying vdev disappearing and then much
later reappearing (mostly in test, but occasionally in production),
and I have yet to lose any data, BUT none of the devices changed path
in the process.

On Wed, Mar 7, 2012 at 4:38 PM, Bob Doolittle <Bob.Doolittle at
oracle.com> wrote:
> Hi,
>
> I had a single-disk zpool (export) and was given two new disks for expanded
> storage. All three disks are identically sized, no slices/partitions. My
> goal is to create a raidz1 configuration of the three disks, containing the
> data in the original zpool.
>
> However, I got off on the wrong foot by doing a "zpool add" of
the first
> disk. Apparently this has simply increased my storage without creating a
> raidz config.
>
> Unfortunately, there appears to be no simple way to just remove that disk
> now and do a proper raidz create of the other two. Nor am I clear on how
> import/export works and whether that''s a good way to copy content
from one
> zpool to another on a single host.
>
> Can somebody guide me? What''s the easiest way out of this mess, so
that I
> can move from what is now a simple two-disk zpool (less than 50% full) to a
> three-disk raidz configuration, starting with one unused disk? In the end I
> want the three-disk raidz to have the same name (and mount point) as the
> original zpool. There must be an easy way to do this.
-- 
{--------1---------2---------3---------4---------5---------6---------7---------}
Paul Kraus
-> Senior Systems Architect, Garnet River ( http://www.garnetriver.com/ )
-> Sound Coordinator, Schenectady Light Opera Company (
http://www.sloctheater.org/ )
-> Technical Advisor, Troy Civic Theatre Company
-> Technical Advisor, RPI Players

just note that you can has different zpool name but with the same old 
mount point for export purpose
-LT


On 3/8/2012 8:40 AM, Paul Kraus wrote:
> Lots of suggestions (not included here), but ...
>
>      With the exception of Cindy''s suggestion of using 4 disks and
> mirroring (zpool attach two new disks to existing vdevs), I would
> absolutely NOT do anything unless I had a known good backup of the
> data! I have seen too many cases described here on this list of people
> trying complicated procedures with ZFS and making one small mistake
> and loosing their data, or spending weeks or months trying to recover
> it.
>
>      Regarding IMPORT / EXPORT, these functions are have two real
> purposes in my mind:
>
> 1. you want to move a zpool from one host to another. You EXPORT from
> the first host, physically move the disks, then IMPORT on the new
> host.
>
> 2. You want (or need) to physically change the connectivity between
> the disks and the host, and implicit in that is that the device paths
> will change. EXPORT, change connectivity, IMPORT. Once again I have
> seen many cases described on this list of folks who moved disks
> around, which ZFS is _supposed_ to handle, but then had a problem.
>
>      I use ZFS first for reliability and second for performance. With
> that in mind, one of my primary rules for ZFS is to NOT move disks
> around without first exporting the zpool. I have done some pretty rude
> things regarding devices underlying vdev disappearing and then much
> later reappearing (mostly in test, but occasionally in production),
> and I have yet to lose any data, BUT none of the devices changed path
> in the process.
>
> On Wed, Mar 7, 2012 at 4:38 PM, Bob Doolittle<Bob.Doolittle at
oracle.com>  wrote:
>> Hi,
>>
>> I had a single-disk zpool (export) and was given two new disks for
expanded
>> storage. All three disks are identically sized, no slices/partitions.
My
>> goal is to create a raidz1 configuration of the three disks, containing
the
>> data in the original zpool.
>>
>> However, I got off on the wrong foot by doing a "zpool add"
of the first
>> disk. Apparently this has simply increased my storage without creating
a
>> raidz config.
>>
>> Unfortunately, there appears to be no simple way to just remove that
disk
>> now and do a proper raidz create of the other two. Nor am I clear on
how
>> import/export works and whether that''s a good way to copy
content from one
>> zpool to another on a single host.
>>
>> Can somebody guide me? What''s the easiest way out of this
mess, so that I
>> can move from what is now a simple two-disk zpool (less than 50% full)
to a
>> three-disk raidz configuration, starting with one unused disk? In the
end I
>> want the three-disk raidz to have the same name (and mount point) as
the
>> original zpool. There must be an easy way to do this.
-- 
Hung-Sheng Tsao Ph D.
Founder&  Principal
HopBit GridComputing LLC
cell: 9734950840

http://laotsao.blogspot.com/
http://laotsao.wordpress.com/
http://blogs.oracle.com/hstsao/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: laotsao.vcf
Type: text/x-vcard
Size: 608 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20120308/dcb48365/attachment.vcf>