A colleague just asked if zfs delegation worked with zvols too. Thought I'd give it a go and got myself in a mess (tank/linkfixer is the delegated dataset):
[EMAIL PROTECTED] / # zfs create -V 500M tank/linkfixer/foo cannot create device links for 'tank/linkfixer/foo': permission denied cannot create 'tank/linkfixer/foo': permission denied Ok, so we'll try a normal filesystem: [EMAIL PROTECTED] / # zfs create tank/linkfixer/foo cannot create 'tank/linkfixer/foo': dataset already exists [EMAIL PROTECTED] / # zfs list NAME USED AVAIL REFER MOUNTPOINT tank 2.09G 33.8G 24.5K legacy tank/linkfixer 36.3M 9.96G 24.5K legacy tank/linkfixer/foo 22.5K 9.96G 22.5K - [EMAIL PROTECTED] / # zfs destroy -f tank/linkfixer/foo cannot remove device links for 'tank/linkfixer/foo': permission denied [EMAIL PROTECTED] / # zfs list NAME USED AVAIL REFER MOUNTPOINT tank 2.09G 33.8G 24.5K legacy tank/linkfixer 36.3M 9.96G 24.5K legacy tank/linkfixer/foo 22.5K 9.96G 22.5K - I can destroy it ok from the global zone, and I know I could just create a top-level zvol and grant the zone access. Not sure if the 'fix' is : a) prevent attempts to create zvols in non-global zones b) somehow allow it (?) or c) Don't do That I vote for a) myself - should I raise an RFE? -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
