Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset Post: 302700509

Sponsored Content

Operating Systems BSD Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset Post 302700509 by bstring on Thursday 13th of September 2012 01:21:44 PM

09-13-2012

Registered User

Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset

I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error:

Code:

[root@vm-fbsd82-64 /]# zpool create zfspool /dev/da0s1a
cannot create 'zfspool': no such pool or dataset

[root@vm-fbsd82-64 /]# zpool create zfspool /dev/da0
cannot create 'zfspool': no such pool or dataset

I was not sure what to put for the device, so I tried both da0s1a and da0, due to this output:

Code:

[root@vm-fbsd82-64 /]# egrep 'da[0-9]' /var/run/dmesg.boot
da0 at mpt0 bus 0 scbus0 target 0 lun 0
da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
da0: Command Queueing enabled
da0: 204800MB (419430400 512 byte sectors: 255H 63S/T 26108C)
Trying to mount root from ufs:/dev/da0s1a
da0 at mpt0 bus 0 scbus0 target 0 lun 0
da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
da0: Command Queueing enabled
da0: 204800MB (419430400 512 byte sectors: 255H 63S/T 26108C)
Trying to mount root from ufs:/dev/da0s1a
da0 at mpt0 bus 0 scbus0 target 0 lun 0
da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
da0: Command Queueing enabled
da0: 204800MB (419430400 512 byte sectors: 255H 63S/T 26108C)
Trying to mount root from ufs:/dev/da0s1a

Just wondering if I am missing a step or doing something wrong.
edit: I'm starting to wonder if it's because I only have 1 'disk' in this VM, and perhaps the entire disk has been formatted to ufs and so I can't create a zpool on that disk? Do I need to add another disk in VMware?

Also, does anyone know what filesystems are natively supported in FBSD 6.x and 8.x? I believe 6.x supports ufs and 8.x supports ufs and zfs, but I am not positive.

Thank you for any help

Last edited by bstring; 09-13-2012 at 03:27 PM..

bstring

View Public Profile for bstring

Find all posts by bstring

10 More Discussions You Might Find Interesting

1. Solaris

ZFS Pool Mix-up

Hi all I plan to install Solaris 10U6 on some SPARC server using ZFS as root pool, whereas I would like to keep the current setup done by VxVM: - 2 internal disks: c0t0d0 and c0t1d0 - bootable root-volume (mirrored, both disks) - 1 non-mirrored swap slice - 1 non-mirrored slices for Live...

2. Solaris

unable to import zfs pool

# zpool import pool: emcpool1 id: 5596268873059055768 state: UNAVAIL status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: Sun Message ID: ZFS-8000-3C config: emcpool1 ...

3. Infrastructure Monitoring

zfs - migrate from pool to pool

Here are the details. cnjr-opennms>root$ zfs list NAME USED AVAIL REFER MOUNTPOINT openpool 20.6G 46.3G 35.5K /openpool openpool/ROOT 15.4G 46.3G 18K legacy openpool/ROOT/rds 15.4G 46.3G 15.3G / openpool/ROOT/rds/var 102M ...

4. Solaris

zfs pool migration

I need to migrate an existing raidz pool to a new raidz pool with larger disks. I need the mount points and attributes to migrate as well. What is the best procedure to accomplish this. The current pool is 6x36GB disks 202GB capacity and I am migrating to 5x 72GB disks 340GB capacity.

5. Solaris

Best way to rename a ZFS Pool?

Other than export/import, is there a cleaner way to rename a pool without unmounting de FS? Something like, say "zpool rename a b"? Thanks.

6. Solaris

flarecreate for zfs root dataset and ignore multiple dataset

Hi All, I want to write a script to create flar images on multiple servers. In non zfs filesystem I am using -X option to refer a file to exclude mounts on different servers. but on ZFS -X option is not working. I want multiple mounts to be ignore on ZFS base system during flarecreate. I...

7. Solaris

ZFS - overfilled pool

installed Solaris 11 Express on my server machine a while ago. I created a Z2 RAID over five HDDs and created a few ZFS filesystems on it. Once I (unintentionally) managed to fill the pool completely with data and (to my surprise) the filesystems stopped working - I could not read/delete any...

8. Solaris

ZFS - Dataset / pool name are the same...cannot destroy

I messed up my pool by doing zfs send...recive So I got the following : zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT rpool 928G 17.3G 911G 1% 1.00x ONLINE - tank1 928G 35.8G 892G 3% 1.00x ONLINE - So I have "tank1" pool. zfs get all...

9. Solaris

Zpool with 3 2-way mirrors in a pool

I have a single zpool with 3 2-way mirrors ( 3 x 2 way vdevs) it has a degraded disk in mirror-2, I know I can suffer a single drive failure, but looking at this how many drive failures can this suffer before it is no good? On the face of it, I thought that I could lose a further 2 drives in each...

10. Solaris

How to clear a removed single-disk pool from being listed by zpool import?

On an OmniOS server, I removed a single-disk pool I was using for testing. Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore. # zpool import pool: fido id: 7452075738474086658 state: FAULTED status: The pool was last...

LEARN ABOUT FREEBSD

gshsec

GSHSEC(8)						    BSD System Manager's Manual 						 GSHSEC(8)

NAME

     gshsec -- control utility for shared secret devices

SYNOPSIS

     gshsec label [-hv] name prov prov ...
     gshsec stop [-fv] name ...
     gshsec clear [-v] prov ...
     gshsec dump prov ...
     gshsec list
     gshsec status
     gshsec load
     gshsec unload

DESCRIPTION

     The gshsec utility is used for setting up a device which contains a shared secret.  The secret is shared between the given providers.  To
     collect the secret, all providers are needed.  If one of the components is missing, there is no way to get any useful data from the rest of
     them.  The first argument to gshsec indicates an action to be performed:

     label    Set up a shared secret device from the given components with the specified name.	Metadata are stored in the last sector of every
	      component.

     stop     Turn off an existing shared secret device by its name.  This command does not touch on-disk metadata!

     clear    Clear metadata on the given providers.

     dump     Dump metadata stored on the given providers.

     list     See geom(8).

     status   See geom(8).

     load     See geom(8).

     unload   See geom(8).

     Additional options:

     -f  Force the removal of the specified shared secret device.

     -h  Hardcode providers' names in metadata.

     -v  Be more verbose.

EXIT STATUS

     Exit status is 0 on success, and 1 if the command fails.

EXAMPLES

     The following example shows how to create a shared secret device.	The secret will be split between a slice on a local disk and a USB Pen
     drive.

	   gshsec label -v secret /dev/ada0s1 /dev/da0
	   newfs /dev/shsec/secret

     From now on, when the USB Pen drive is inserted, it will be automatically detected and connected, making the secret available via the
     /dev/shsec/secret device.

SEE ALSO

     geom(4), gbde(8), geom(8), newfs(8)

HISTORY

     The gshsec utility appeared in FreeBSD 5.4.

AUTHORS

     Pawel Jakub Dawidek <pjd@FreeBSD.org>

BSD
								  October 1, 2013							       BSD

10 More Discussions You Might Find Interesting

1. Solaris

ZFS Pool Mix-up

Discussion started by: blicki

2. Solaris

unable to import zfs pool

Discussion started by: fugitive

3. Infrastructure Monitoring

zfs - migrate from pool to pool

Discussion started by: pupp

4. Solaris

zfs pool migration

Discussion started by: jac