search for: zfs_create

Author: maybee Repository: /hg/zfs-crypto/gate Revision: 2dd24a5efe8bb703f8a0b96d0cbaab6d4f744456 Log message: 6413573 deadlock between fsflush() and zfs_create() 6416101 du inside snapshot produces bad sizes and paths Files: update: usr/src/uts/common/fs/zfs/sys/zfs_znode.h update: usr/src/uts/common/fs/zfs/zfs_dir.c update: usr/src/uts/common/fs/zfs/zfs_vnops.c update: usr/src/uts/common/fs/zfs/zfs_znode.c

...t;turing>. Creating list of files to copy from the global zone. [...] ----8<---- The install continues and succeeds, but no ZFS dataset was created. I traced the error message in the latest ON source and located it in create_zfs_zonepath() in usr/src/cmd/zoneadm/zfs.c: ----8<---- if (zfs_create(g_zfs, zfs_name, ZFS_TYPE_FILESYSTEM, props) != 0 || (zhp = zfs_open(g_zfs, zfs_name, ZFS_TYPE_DATASET)) == NULL) { (void) fprintf(stderr, gettext("cannot create ZFS dataset %s: " "%s\n"), zfs_name, libzfs_error_description(g_zfs)); nvlist_free(props); return;...

...rt works just fine. The last thing that dsl_crypto_key_gen() does is place the encryption key into ds>ds_key so it can be used later. When keyscope=pool the only difference with the above is that the wrapping key is already present in spa->spa_key. The problem occurs when the userland zfs_create() attempts to mount the newly created dataset. The dsl_dataset_t* that was valid during the creation isn''t available anymore and since there is no key we can''t mount the dataset. Have I done something fundamentally wrong by hanging the crypto key off the dsl_dataset_t ? Is...

...ysource=raw,file:///ds2.key tank/ds2 cannot open /ds2.key free(80d6c98): invalid or corrupted buffer stack trace: libumem.so.1''umem_err_recoverable+0x39 libumem.so.1''process_free+0xe1 libumem.so.1''free+0x17 libzfs.so.1''zfs_crypto_create+0x1c3 libzfs.so.1''zfs_create+0x25c zfs''zfs_do_create+0x495 zfs''main+0x265 zfs''_start+0x7a The above file didn''t exist - but needs to for that command to succeed. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ---...

...0.0 Msg| 21582 | 1: Testing with keychange delegated, a non-root user can do ''zfs k ey -c'' Msg| 21582 | stdout| 21582| /usr/sbin/zpool create -f pool_21582 /export/home/vdev_file_1 stdout| 21582| /usr/bin/expect /export/home/zfscrypto-tests/proto/suites/securi ty/zfs-crypto/lib/zfs_create.exp /usr/sbin/z fs pool_21582 fs on hex,prompt 9adf6ac44655ccc414a5e9197a34c52731f5fe08d9191a7c d3811ab6f69f1078 stdout| 21582| spawn /usr/sbin/zfs create -o encryption=on -o keyscope=dataset -o keysource=hex,prompt pool_21582/fs^M stdout| Enter hexadecmial key fo...

I have a few clients that have more than one user in the same mailbox. I have my setup using fctrl for mailbox and index locking. My mail is stored on a network file system (gluster) and my indexes are stored on the local drive. I have a few issues: - My users mailboxes have issues where messages will be mixed up (you go to open a message and it gets a different message) - messages will

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org