zfs discuss - Sep 2010 - Information lost? Does zpool create erase volumes

Those of you who have read my previous post know that I was trying to reassemble
a raidz after a complete reinstall of the OS on a Mac running zfs-119. In a fit
of impatience, I executed the zpool create command on the three volumes, two of
which were part of the old raidz, the third one having replaced the third old
one, which had died. This did succeed in creating a raidz on my system, but all
the original information is gone, leading me to believe that I caused the old
information to be erased or at least inaccessible.

Can any of you please clue me in?
-- 
This message posted from opensolaris.org

Dominik,

You overwrite your data when you recreated a pool with the same
name and the same disks with zpool create.

If I try to recreate a pool that already exists, at least exported,
I will see a message similar to the following:

# zpool create tank c3t3d0
invalid vdev specification
use ''-f'' to override the following errors:
/dev/dsk/c3t3d0s0 is part of exported or potentially active ZFS pool 
tank. Please see zpool(1M).

Did you attempt to import the pool prior to the zpool create?

Thanks,

Cindy

On 09/02/10 14:17, Dominik Hoffmann wrote:
> Those of you who have read my previous post know that I was trying to
reassemble a raidz after a complete reinstall of the OS on a Mac running
zfs-119. In a fit of impatience, I executed the zpool create command on the
three volumes, two of which were part of the old raidz, the third one having
replaced the third old one, which had died. This did succeed in creating a raidz
on my system, but all the original information is gone, leading me to believe
that I caused the old information to be erased or at least inaccessible.
> 
> Can any of you please clue me in?

Yes, I did try to import the pool. However, the response of the command was
"no pools available to import".
-- 
This message posted from opensolaris.org

> Yes, I did try to import the pool. However, the
> response of the command was "no pools available to
> import".
I''m not sure what happened to your pool, but I think it is possible
that the pool information on these disks was removed accidentally. 
I''m not sure what the diskutil command does but if it was run on
the wrong disk, then possibly all the pool info was removed from
the disks'' labels. This is just a guess.

Then, when you reissued the zpool create command, it didn''t 
complain that the disks were already in use because the pool info 
was already removed.

Cindy
-- 
This message posted from opensolaris.org