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:
I was not sure what to put for the device, so I tried both da0s1a and da0, due to this output:
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.
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)
# 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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT FREEBSD
mknod
MKNOD(8) BSD System Manager's Manual MKNOD(8)NAME
mknod -- build special file
SYNOPSIS
mknod name
mknod name [b | c] major minor [owner:group]
DESCRIPTION
The mknod utility is deprecated on modern FreeBSD systems.
The mknod utility creates device special files. To make nodes manually, the arguments are:
name Device name, for example /dev/da0 for a SCSI disk or /dev/pts/0 for pseudo-terminals.
b | c Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the
type is b. All other devices are character type devices, such as terminal and pseudo devices, and are type c.
major The major device number is an integer number which tells the kernel which device driver entry point to use.
minor The minor device number tells the kernel which subunit the node corresponds to on the device; for example, a subunit may be a file
system partition or a tty line.
owner:group
The owner group operand pair is optional, however, if one is specified, they both must be specified. The owner may be either a
numeric user ID or a user name. If a user name is also a numeric user ID, the operand is used as a user name. The group may be
either a numeric group ID or a group name. Similar to the user name, if a group name is also a numeric group ID, the operand is used
as a group name.
Major and minor device numbers can be given in any format acceptable to strtoul(3), so that a leading '0x' indicates a hexadecimal number,
and a leading '0' will cause the number to be interpreted as octal.
The mknod utility can be used to recreate deleted device nodes under a devfs(5) mount point by invoking it with only a filename as an argu-
ment. Example:
mknod /dev/cd0
where /dev/cd0 is the name of the deleted device node.
COMPATIBILITY
The chown(8)-like functionality is specific to FreeBSD.
As of FreeBSD 4.0, block devices were deprecated in favour of character devices. As of FreeBSD 5.0, device nodes are managed by the device
file system devfs(5), making the mknod utility superfluous. As of FreeBSD 6.0 device nodes may be created in regular file systems but such
nodes cannot be used to access devices.
SEE ALSO mkfifo(1), mknod(2), devfs(5), chown(8)HISTORY
A mknod utility appeared in Version 6 AT&T UNIX.
BSD January 31, 2010 BSD