similar to: 6351004 capacity of pool in zfs gui is not consistent with the output of zpool list

Author: talley Repository: /hg/zfs-crypto/gate Revision: ee193c0b713e5b433df62de6679214ea81efd17b Log message: 6285992 JNI should make use of dm_inuse() when 6343802 is fixed 6399767 JNI: pools without root datasets are not modeled in JNI Files: update: usr/src/lib/libzfs_jni/common/libzfs_jni_dataset.c update: usr/src/lib/libzfs_jni/common/libzfs_jni_dataset.h update:

http://defect.opensolaris.org/bz/show_bug.cgi?id=631 Summary: zpool get with no pool name dumps core in zfs-crypto Classification: Development Product: zfs-crypto Version: unspecified Platform: Other OS/Version: Solaris Status: NEW Severity: minor Priority: P4 Component: other AssignedTo:

Author: eschrock Repository: /hg/zfs-crypto/gate Revision: 7ab8044a52af78e3519796a7778d4111a6ed7caf Log message: 6424405 zpool import destroyed_pool can damage existing pool using same devices Files: update: usr/src/uts/common/fs/zfs/spa.c update: usr/src/uts/common/fs/zfs/sys/vdev.h update: usr/src/uts/common/fs/zfs/sys/vdev_impl.h update: usr/src/uts/common/fs/zfs/vdev.c

*Synopsis*: "set once" / "create time only" properties can''t be set for pool level dataset Due to a change requested by <User 1-5Q-12446>, <User 1-5Q-12446> is now the responsible engineer for: CR 6647661 changed on Jan 7 2008 by <User 1-5Q-12446> === Field ============ === New Value ============= === Old Value ============= Responsible Engineer

*Synopsis*: "set once" / "create time only" properties can''t be set for pool level dataset CR 6647661 changed on Apr 15 2009 by <User 1-ERV-6> === Field ============ === New Value ============= === Old Value ============= See Also 6828754 ====================== ===========================

I just ran zpool scrub on an active pool on an x4170 running S10U7 with the latest patches and iostat immediately dropped to 0 for all the pool devices and all processes associated with that device where hard locked, e.g., kill -9 on a zpool status processes was ineffective. However, other zpool on the system, such as the root pool, continued to work. Neither init 6 nor reboot where able to take

I''m pretty sure this is my fault but I need some help in fixing the system. It was installed at one point with snv_29 with the pre integration SUNWzfs package. I did a live upgrade to snv_42 but forgot to remove the old SUNWzfs before I did so. When the system booted up got complaints about kstat install because I still had an old zpool kernel module lying around. So I did pkgrm

Thies C. Arntzen wrote: > Hi, > > I’m new here so apologies if this has been answered before. > > I have a box that uses ZFS for everything (ubuntu 17.04) and I want to > create a libvirt pool on that. My ZFS pool is named „big" > > So i do: > > > zfs create big/zpool > > virsh pool-define-as --name zpool --source-name big/zpool --type zfs > >

Hi, I’m new here so apologies if this has been answered before. I have a box that uses ZFS for everything (ubuntu 17.04) and I want to create a libvirt pool on that. My ZFS pool is named „big" So i do: > zfs create big/zpool > virsh pool-define-as --name zpool --source-name big/zpool --type zfs > virsh pool-start zpool > virsh pool-autostart zpool > virsh pool-list >

Thank you for your reply. I have managed to create a virtual machine on my ZFS-filesystem using virt-install:-) It seems to me that my version of libvirt (Ubuntu 17.04) has problems enumerating the devices when "virsh vol-list“ is used. The volumes are available for virt-install but not thru virsh or virt-manager. As to when the volumes disappear in virsh vol-list - I have no idea. I’m not

When I first started using ZFS I tried to create a pool from my disks /dev/c8d1 and /dev/c8d1 . I could see the slices though. I could not see those disks with out being root and all though I get it ZFS didnt. It could not find the disks and did not tell me I needed to be root. That is all... Web...

Hi all, I moved from Sol 10 Update4 to update 6. Before doing this I exported both of my zpools, and replace the discs containing the ufs root on with two new discs (these discs did not have any zpool /zfs info and are raid mirrored in hardware) Once I had installed update6 I did a zpool import, but it only shows (and was able to) import one of the two pools. Looking at dmesg it appears as

http://defect.opensolaris.org/bz/show_bug.cgi?id=752 Summary: zfs set keysource no longer works on existing pools Classification: Development Product: zfs-crypto Version: unspecified Platform: Other OS/Version: Solaris Status: NEW Severity: blocker Priority: P1 Component: other AssignedTo:

Hi List, As a ZFS newbie, I foolishly copied my data set to the root zpool file system (a large iSCSI SAN array). Thus: # zpool create -f iscsi c4t19d0 c4t20d0 c4t21d0 c4t22d0 c4t23d0 c4t24d0 # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT iscsi 9.53T 64.5K 5.34T 0% ONLINE - # zfs set mountpoint=/mydisks/iscsi iscsi Then copied

Hi All, over the last couple of weeks, I had to boot from my rpool from various physical machines because some component on my laptop mainboard blew up (you know that burned electronics smell?). I can''t retrospectively document all I did, but I am sure I recreated the boot-archive, ran devfsadm -C and deleted /etc/zfs/zpool.cache several times. Now zpool status is referring to a

Hi all, I recently created a RAID-Z1 pool out of a set of 7 SCSI disks, using the following command: # zpool create magicant raidz c5t0d0 c5t1d0 c5t2d0 c5t3d0 c5t4d0 c5t5d0 c5t6d0 It worked fine, but I was slightly confused by the size yield (99 GB vs the 116 GB I had on my other RAID-Z1 pool of same-sized disks). I thought one of the disks might have been to blame, so I tried swapping it out

Hello, Experts. I''ve got a problem. I''m trying to expand my main zpool (rpool), but don''t know how to do that. (i''m 100% newbie in non-windows world) I use Osol under Vmware on Windows. I had a pretty small vhdd -> only 12gb. Yesterday i decided to expand my virtual drive to 20gb. (After several tries to upgrade the OS to a newest dev-releases and

Hi all, I have a RAID-Z zpool made up of 4 x SATA drives running on Nexenta 1.0.1 (OpenSolaris b85 kernel). It has on it some ZFS filesystems and few volumes that are shared to various windows boxes over iSCSI. On one particular iSCSI volume, I discovered that I had mistakenly deleted some files from the FAT32 partition that is on it. The files were still in a ZFS snapshot that was made earlier

There are several possibilities depending upon what you mean. Personally, I have a zpool on the host that I carve off individual zfs filesystems that each guest uses. I put one qcow2 or raw image per zfs filesystem. I do this for backup and replication purposes. Then I have a recursive replication from this host to another so that I can boot up any of the VMs should the primary VM server goes

I am seeing this issue posted a lot in the forums: A zpool add/replace command is run, for example: zpool add archive spare c2t0d2 invalid vdev specification use ''-f'' to override the following errors: /dev/dsk/c2t1d7s0 is part of active ZFS pool archive. Please see zpool(1M). (-f just says: the following errors must be manually repaired:) Also, when running format and