search for: dmu_objset_create_sync

I''ve noticed that the dsl_dataset_t that points to a given dataset changes during the life time of a ''zfs create'' command. We start out with one dsl_dataset_t* during dmu_objset_create_sync() but by the time we are later mounting the dataset we have a different in memory dsl_dataset_t* referring to the same dataset. This causes me a big issue with per dataset provided encryption keys, but not with a per pool provided encryption key. When keyscope=dataset we pass the key value use...

...../common/fs/zfs/dmu_objset.c, line: 628 000002a100a675a0 genunix:assfail+78 (7b3036a0, 7b3031a8, 274, 1853800, 1361000, 0) %l0-3: 0000030004e520c0 0000060010edd830 000000007b303400 0000060011409328 %l4-7: 000000007b303400 0000000000000000 00000000018a2000 0000000000000000 000002a100a67650 zfs:dmu_objset_create_sync+100 (30004eb8600, 2a1006216f0, 60010c6e448, 600103c7880, 60010bac200, 15) %l0-3: 0000000000000002 0000000000000002 000000007b303000 000000007b303400 %l4-7: 0000060011399ce8 000002a100621800 0000000000000001 00000600117fea80 000002a100a67710 zfs:dsl_sync_task_group_sync+11c (600103cd5d8, 600103c...

Hi, In migrating from **VM to ZFS am I going to have an issue with Major/Minor numbers with NFS mounts? Take the following scenario. 1. NFS clients are connected to an active NFS server that has SAN shared storage between the active and standby nodes in a cluster. 2. The NFS clients are using the major/minor numbers on the active node in the cluster to communicate to the NFS active server. 3.