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
Old 09-13-2012
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..
 

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... (1 Reply)
Discussion started by: blicki
1 Replies

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 ... (7 Replies)
Discussion started by: fugitive
7 Replies

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 ... (3 Replies)
Discussion started by: pupp
3 Replies

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. (2 Replies)
Discussion started by: jac
2 Replies

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. (2 Replies)
Discussion started by: verdepollo
2 Replies

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... (0 Replies)
Discussion started by: uxravi
0 Replies

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... (3 Replies)
Discussion started by: RychnD
3 Replies

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... (8 Replies)
Discussion started by: eladgrs
8 Replies

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... (4 Replies)
Discussion started by: fishface
4 Replies

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... (11 Replies)
Discussion started by: priyadarshan
11 Replies
BSDLABEL(8)						    BSD System Manager's Manual 					       BSDLABEL(8)

NAME
bsdlabel -- read and write BSD label SYNOPSIS
bsdlabel [-A] disk | -f file bsdlabel -w [-An] [-B [-b boot]] [-m machine] disk | -f file [type] bsdlabel -e [-An] [-B [-b boot]] [-m machine] disk | -f file bsdlabel -R [-An] [-B [-b boot]] [-m machine] [-f] disk | -f file protofile DESCRIPTION
The bsdlabel utility installs, examines or modifies the BSD label on a disk partition, or on a file containing a partition image. In addi- tion, bsdlabel can install bootstrap code. Disk Device Name When specifying the device (i.e., when the -f option is not used), the /dev/ path prefix may be omitted; the bsdlabel utility will automati- cally prepend it. General Options The -A option enables processing of the historical parts of the BSD label. If the option is not given, suitable values are set for these fields. The -f option tells bsdlabel that the program will operate on a file instead of a disk partition. The -n option stops the bsdlabel program right before the disk would have been modified, and displays the result instead of writing it. The -m machine argument forces bsdlabel to use a layout suitable for a different architecture. Current valid values are i386, amd64, and pc98. If this option is omitted, bsdlabel will use a layout suitable for the current machine. Reading the Disk Label To examine the label on a disk drive, use the form bsdlabel [-A] [-m machine] disk disk represents the disk in question, and may be in the form da0 or /dev/da0. It will display the partition layout. Writing a Standard Label To write a standard label, use the form bsdlabel -w [-An] [-m machine] disk [type] If the drive type is specified, the entry of that name in the disktab(5) file is used; otherwise, or if the type is specified as 'auto', a default layout is used. Editing an Existing Disk Label To edit an existing disk label, use the form bsdlabel -e [-An] [-m machine] disk This command opens the disk label in the default editor, and when the editor exits, the label is validated and if OK written to disk. Restoring a Disk Label From a File To restore a disk label from a file, use the form bsdlabel -R [-An] [-m machine] disk protofile The bsdlabel utility is capable of restoring a disk label that was previously saved in a file in ASCII format. The prototype file used to create the label should be in the same format as that produced when reading or editing a label. Comments are delimited by '#' and newline. Installing Bootstraps If the -B option is specified, bootstrap code will be read from the file /boot/boot and written to the disk. The -b boot option allows a different file to be used. FILES
/boot/boot Default boot image. /etc/disktab Disk description file. SAVED FILE FORMAT
The bsdlabel utility uses an ASCII version of the label when examining, editing, or restoring a disk label. The format is: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 16 4.2BSD 2048 16384 5128 b: 1091994 81936 swap c: 1173930 0 unused 0 0 # "raw" part, don't edit If the -A option is specified, the format is: # /dev/da1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 51 tracks/cylinder: 19 sectors/cylinder: 969 cylinders: 1211 sectors/unit: 1173930 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 16 4.2BSD 1024 8192 16 b: 160000 81936 swap c: 1173930 0 unused 0 0 # "raw" part, don't edit Lines starting with a '#' mark are comments. The partition table can have up to 8 entries. It contains the following information: # The partition identifier is a single letter in the range 'a' to 'h'. By convention, partition 'c' is reserved to describe the entire disk. size The size of the partition in sectors, K (kilobytes - 1024), M (megabytes - 1024*1024), G (gigabytes - 1024*1024*1024), % (percentage of free space after removing any fixed-size partitions other than partition 'c'), or * (all remaining free space after fixed-size and percentage partitions). For partition 'c', a size of * indicates the entire disk. Lowercase versions of suffixes K, M, and G are allowed. Size and suffix should be specified without any spaces between them. Example: 2097152, 1G, 1024M and 1048576K are all the same size (assuming 512-byte sectors). offset The offset of the start of the partition from the beginning of the drive in sectors, or * to have bsdlabel calculate the correct off- set to use (the end of the previous partition plus one, ignoring partition 'c'). For partition 'c', * will be interpreted as an off- set of 0. The first partition should start at offset 16, because the first 16 sectors are reserved for metadata. fstype Describes the purpose of the partition. The above example shows all currently used partition types. For UFS file systems and ccd(4) partitions, use type 4.2BSD. For Vinum drives, use type vinum. Other common types are swap and unused. By convention, partition 'c' represents the entire slice and should be of type unused, though bsdlabel does not enforce this convention. The bsdlabel utility also knows about a number of other partition types, none of which are in current use. (See the definitions starting with FS_UNUSED in <sys/disklabel.h> for more details.) fsize For 4.2BSD file systems only, the fragment size; see newfs(8). bsize For 4.2BSD file systems only, the block size; see newfs(8). bps/cpg For 4.2BSD file systems, the number of cylinders in a cylinder group; see newfs(8). EXAMPLES
Display the label for the first slice of the da0 disk, as obtained via /dev/da0s1: bsdlabel da0s1 Save the in-core label for da0s1 into the file savedlabel. This file can be used with the -R option to restore the label at a later date: bsdlabel da0s1 > savedlabel Create a label for da0s1: bsdlabel -w /dev/da0s1 Read the label for da0s1, edit it, and install the result: bsdlabel -e da0s1 Read the on-disk label for da0s1, edit it, and display what the new label would be (in sectors). It does not install the new label either in-core or on-disk: bsdlabel -e -n da0s1 Write a default label on da0s1. Use another bsdlabel -e command to edit the partitioning and file system information: bsdlabel -w da0s1 Restore the on-disk and in-core label for da0s1 from information in savedlabel: bsdlabel -R da0s1 savedlabel Display what the label would be for da0s1 using the partition layout in label_layout. This is useful for determining how much space would be allotted for various partitions with a labeling scheme using %-based or * partition sizes: bsdlabel -R -n da0s1 label_layout Install a new bootstrap on da0s1. The boot code comes from /boot/boot: bsdlabel -B da0s1 Install a new label and bootstrap. The bootstrap code comes from the file newboot in the current working directory: bsdlabel -w -B -b newboot /dev/da0s1 Completely wipe any prior information on the disk, creating a new bootable disk with a DOS partition table containing one slice, covering the whole disk. Initialize the label on this slice, then edit it. The dd(1) commands are optional, but may be necessary for some BIOSes to properly recognize the disk: dd if=/dev/zero of=/dev/da0 bs=512 count=32 fdisk -BI da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 bsdlabel -w -B da0s1 bsdlabel -e da0s1 This is an example disk label that uses some of the new partition size types such as %, M, G, and *, which could be used as a source file for ``bsdlabel -R ada0s1 new_label_file'': # /dev/ada0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 400M 16 4.2BSD 4096 16384 75 # (Cyl. 0 - 812*) b: 1G * swap c: * * unused e: 204800 * 4.2BSD f: 5g * 4.2BSD g: * * 4.2BSD DIAGNOSTICS
The kernel device drivers will not allow the size of a disk partition to be decreased or the offset of a partition to be changed while it is open. COMPATIBILITY
Due to the use of an uint32_t to store the number of sectors, BSD labels are restricted to a maximum of 2^32-1 sectors. This usually means 2TB of disk space. Larger disks should be partitioned using another method such as gpart(8). The various BSDs all use slightly different versions of BSD labels and are not generally compatible. SEE ALSO
ccd(4), geom(4), md(4), disktab(5), boot0cfg(8), fdisk(8), gpart(8), newfs(8) BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 12:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy