> 
> On May 10, 2007, at 10:04 PM, Matthew Flanagan wrote:
> 
> > Hi,
> >
> > I have a test server that I use for testing my
> different jumpstart  
> > installations. This system is continuously
> installed and  
> > reinstalled with different system builds.
> > For some builds I have a finish script that creates
> a zpool using  
> > the utility found in the Solaris 10 update 3
> miniroot.
> >
> > I have found an issue where the zpool command fails
> to create a new  
> > zpool if the system previously had a UFS filesystem
> on the same slice.
> >
> > The command and error is:
> >
> > zpool create -f -R /a -m /srv srv c1t0d0s6
> > cannot create 'srv': one or more vdevs refer to the
> same device
> >
> 
> Works fine for me:
> # df -kh
> Filesystem             size   used  avail capacity
>  Mounted on
> dev/dsk/c1t1d0s0       17G   4.1G    13G    24%    /
> ...
> /dev/dsk/c1t1d0s6       24G    24M    24G     1%
>    /zfs0
> mount /zfs0
> # zpool create -f -R /a -m /srv srv c1t1d0s6
> # zpool status
>    pool: srv
> te: ONLINE
> scrub: none requested
> config:
> 
>          NAME        STATE     READ WRITE CKSUM
> srv         ONLINE       0     0     0
>            c1t1d0s6  ONLINE       0     0     0
>  known data errors
> 
> 
> eric
> 
> 

That works for me too. Perhaps you should actually follow my steps to reproduce 
the issue?

matthew

> 
> > The steps to reproduce are:
> >
> > 1. build a Solaris 10 Update 3 system via jumpstart
> with the  
> > following partitioning and only UFS filesystems:
> >
> > partitioning explicit
> > filesys rootdisk.s0 6144 / logging
> > filesys rootdisk.s1 1024 swap
> > filesys rootdisk.s3 4096 /var logging,nosuid
> > filesys rootdisk.s6 free /srv logging
> > filesys rootdisk.s7 50 unnamed
> >
> > 2. Then rebuild the same system via jumpstart with
> the following  
> > partitioning with slice 6 left unnamed so that a
> finish script may  
> > create a zpool with the command 'zpool create -f -R
> /a -m /srv srv  
> > cntndns6':
> >
> > partitioning explicit
> > filesys rootdisk.s0 6144 / logging
> > filesys rootdisk.s1 1024 swap
> > filesys rootdisk.s3 4096 /var logging,nosuid
> > filesys rootdisk.s6 free unnamed
> > filesys rootdisk.s7 50 unnamed
> >
> > Has anyone hit this issue and is this a known bug
> with a workaround?
> >
> > regards
> >
> > matthew
> >
> >
> > This message posted from opensolaris.org
> > _______________________________________________
> > zfs-discuss mailing list
> > zfs-discuss@opensolaris.org
> >
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
>
 
 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to