Tom Parrott

Ah yes, sorry, its block.filesystem. See the tip at the bottom of https://linuxcontainers.org/lxd/docs/master/reference/storage_zfs/#storage-pool-configuration that links to https://linuxcontainers.org/lxd/docs/master/howto/storage_volumes/#storage-configure-vol-default

Although block.filesystem and block.mount_options are missing from https://linuxcontainers.org/lxd/docs/master/reference/storage_zfs/#storage-volume-configuration @ru-fu / @monstermunchkin are you able to add it based on the one from https://linuxcontainers.org/lxd/docs/master/reference/storage_lvm/#storage-volume-configuration

Right, so I've taken a look at whats going on here, and the behaviour is that when using instances on the `dir` pool the storage subsystem invokes `CreateInstanceFromCopy`, this then...

Also see here https://discuss.linuxcontainers.org/t/lxc-query-not-showing-disk-stats-for-all-containers/16440

The instance placement scriptlet feature could help achieve what is desired here.

@gabrielmougard fancy seeing if you can shed any light on this?

Confirmed this is still an issue.

OK so I figured it out, and am not sure if its actually a bug. This depends on your perspective of what is being asked with `lxc info ` or...

We can see the output from the underlying btrfs tool: After initial launch: ``` sudo btrfs qgroup show -e -f /var/lib/lxd/storage-pools/btrfs/containers/c1 qgroupid rfer excl max_excl -------- ---- ---- -------- 0/274...

I've confirmed the steps above do create the error reported. Reverting this change (which doesn't make sense to me because it ignores the `--project` flag): https://github.com/lxc/lxd/blob/master/lxc/image.go#L189-L197 Avoids the not found...