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@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
