Ian,

The first error is correct in that zpool-create will not, unless
forced, create a file system if it knows that another filesystem
presides in the target vdev.

The second error was caused by your removal of the slice.

What I find discerning is that the zpool created.
Can you provide the result of "zpool status" and list of the disk
partition table?  If it's indeed carved from c1d0s6, can you destroy
the pool and see if the same creation sequence indeed creates the
zpool?


--
Just me,
Wire ...

On 12/6/06, Ian Brown <[EMAIL PROTECTED]> wrote:
Hello,
I try to create a zfs file system according to
"Creating a Basic ZFS File System" section of
"Creating a Basic ZFS File System" document of SUN.

The problem is that the device has a ufs filesystem the partiotion
I am trying to work with; it is in fact empty and does not contain any
file which I need.

So:

zpool create tank /dev/dsk/c1d0s6
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c1d0s6 contains a ufs filesystem.
/dev/dsk/c1d0s6 is normally mounted on /MyPartition according to
  /etc/vfstab. Please remove this entry to use this device.

So I removed this entry from /etc/vfstab and also unmounted the
/MyPartition partition.

than I tried:

zpool create -f tank /dev/dsk/c1d0s6
internal error: No such device
Abort (core dumped)

But:
 "zpool list" gives:
NAME                    SIZE    USED   AVAIL    CAP  HEALTH     ALTROOT
tank                   1.94G   51.5K   1.94G     0%  ONLINE     -

is there any reason for this "internal error: No such device" ?
Is there something wrong here which I should do in a different way ?


from "man zpool create -f"
 The command  verifies  that  each  device  specified  is
         accessible  and  not currently in use by another subsys-
         tem. There  are  some  uses,  such  as  being  currently
         mounted, or specified as the dedicated dump device, that
         prevents a device from ever being  used  by  ZFS.  Other
         uses,  such as having a preexisting UFS file system, can
         be overridden with the -f option.
                                 ...
                                 ...
  -f

             Forces use of vdevs, even if they appear in  use  or
             specify  a  conflicting  replication  level. Not all
             devices can be overridden in this manner.

Ian


This message posted from opensolaris.org
_______________________________________________
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

Reply via email to