search for: zfs_ioctl

...bzfs_crypto.c update: usr/src/lib/libzfs_jni/common/libzfs_jni_property.c update: usr/src/lib/pam_modules/Makefile update: usr/src/pkgdefs/SUNWcsl/prototype_com update: usr/src/pkgdefs/SUNWcsl/prototype_i386 update: usr/src/pkgdefs/SUNWcsl/prototype_sparc update: usr/src/uts/common/fs/zfs/sys/zfs_ioctl.h update: usr/src/uts/common/fs/zfs/sys/zio_crypt.h update: usr/src/uts/common/fs/zfs/zfs_ioctl.c update: usr/src/uts/common/fs/zfs/zio.c update: usr/src/uts/common/fs/zfs/zio_crypt.c update: usr/src/uts/common/sys/crypto/common.h update: usr/src/uts/intel/Makefile.intel.shared update: usr/s...

...l key -u export Key error in ''export'': crypto key failure --- /1 at 1: <- libzfs:zpool_disable_datasets() = 0 /1 at 1: -> libzfs:unload_key(0x80bb548, 0x8042580) /1 at 1: -> libzfs:crypto_key_ioctl(0x80bb548, 0x8042580) /1 at 1: -> libzfs:zfs_ioctl(0x80bb548, 0x5a2f, 0x8042580) /1: ioctl(3, ZFS_IOC_CRYPTO, 0x08042580) Err#1 EPERM [sys_config] /1 at 1: <- libzfs:zfs_ioctl() = -1 /1 at 1: <- libzfs:crypto_key_ioctl() = 1 /1 at 1: <- libzfs:unload_key() = 1 /1 at 1: <- libzfs:zpool_unload_ke...

...ed information. but after reboot it is not there. If i was able to access before reboot so it must be in memory. I think i need to save it to disk. how does one force zfs znode to disk. right now i dont do anything special for it. Just made an ioctl, accessed znode and made changes. example in zfs_ioctl case add_new: zp = VTOZ(vp); zp->z_phys->new_field = 2; return(0); -- This message posted from opensolaris.org

I contacted the author of ''lsof'' regarding the missing ZFS support. The command works but fails to display any files that are opened by the process in a ZFS filesystem. He indicates that the required ZFS kernel structure definitions (header files) are not shipped with the OS. He further indicated that he rummaged through the OpenSolaris source tree and the files doesn''t

We have finished a beta version of the feature. A webrev for it can be found here: http://cr.illumos.org/~webrev/sensille/fits-send/ It adds a command ''zfs fits-send''. The resulting streams can currently only be received on btrfs, but more receivers will follow. It would be great if anyone interested could give it some testing and/or review. If there are no objections,

In another thread recursive snapshot creation was found atomic so that it is done quickly, and more important, all at once or nothing at all. Do you know if recursive destroying and renaming of snapshots are atomic too? Regards Henrik Heino

.../zfs/zpool_prop.c update: usr/src/lib/libzfs/common/libzfs.h update: usr/src/lib/libzfs/common/libzfs_crypto.c update: usr/src/lib/libzfs/common/libzfs_dataset.c update: usr/src/lib/libzfs/common/libzfs_pool.c update: usr/src/uts/common/fs/zfs/sys/zio_crypt.h update: usr/src/uts/common/fs/zfs/zfs_ioctl.c update: usr/src/uts/common/sys/fs/zfs.h

.../uts/common/fs/zfs/sys/zio.h update: usr/src/uts/common/fs/zfs/sys/zio_impl.h update: usr/src/uts/common/fs/zfs/vdev.c update: usr/src/uts/common/fs/zfs/vdev_mirror.c update: usr/src/uts/common/fs/zfs/vdev_raidz.c update: usr/src/uts/common/fs/zfs/vdev_root.c update: usr/src/uts/common/fs/zfs/zfs_ioctl.c update: usr/src/uts/common/fs/zfs/zio.c update: usr/src/uts/common/fs/zfs/zio_checksum.c update: usr/src/uts/common/sys/fs/zfs.h

System: snv_151a 64 bit on Intel. Error: panic[cpu0] assertion failed: zvol_get_stats(os, nv) == 0, file: ../../common/fs/zfs/zfs_ioctl.c, line: 1815 Failure first seen on Solaris 10, update 8 History: I recently received two 320G drives and realized from reading this list it would have been better if I would have done the install on the small drives but I didn''t have them at the time. I added the two 320G drives and cr...

.../dmu_tx.c usr/src/uts/common/fs/zfs/dsl_pool.c usr/src/uts/common/fs/zfs/dsl_scrub.c usr/src/uts/common/fs/zfs/spa.c usr/src/uts/common/fs/zfs/sys/dsl_pool.h usr/src/uts/common/fs/zfs/sys/spa.h usr/src/uts/common/fs/zfs/sys/zio.h usr/src/uts/common/fs/zfs/zfs_acl.c usr/src/uts/common/fs/zfs/zfs_ioctl.c usr/src/uts/common/fs/zfs/zfs_vfsops.c usr/src/uts/common/fs/zfs/zil.c usr/src/uts/common/fs/zfs/zio.c usr/src/uts/common/inet/ipf/fil.c usr/src/uts/common/inet/ipf/ip_compat.c usr/src/uts/common/inet/ipf/ip_fil_solaris.c usr/src/uts/common/inet/ipf/ip_nat.c usr/src/uts/common/inet/ipf/ip...

It wouldn''t be proper to start my first post here without congratulations and thanks to the ZFS team for such an impressive piece of work. Anyway, on to my query. I''ve been trying out ZFS, with a particular focus in reducing latency in a specific application. This application has a fair amount of random writing going on in the background (which, of course, ZFS will make