pmooney helped me out on IRC. This is caused by:
8130 /usr/node/bin/node --abort_on_uncaught_exception /usr/sbin/imgadm list
8139 /usr/sbin/zfs list -t filesystem,volume,snapshot -pH -o
name,origin,mountpoint,
[root@adm1 ~]# pargs 8139
8139: /usr/sbin/zfs list -t filesystem,volume,snapshot -pH -o
name,origin,mountpoint,
argv[0]: /usr/sbin/zfs
argv[1]: list
argv[2]: -t
argv[3]: filesystem
argv[4]: -pH
argv[5]: -o
argv[6]: name
So on systems with many snapshots this command may take .. quite some time.
On this particular system, there is a backups ZFS pool attached to the system,
but I tested on other systems, and managed to just hit ones that had many
snapshots on the zones pool.
An RFE, at least to mitigate some of this, would be to limit this `zfs list` to
`-r $SYSPOOL`?
Sorry for the noise.
--
bdha
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
