On Tue, 26 Jun 2007 [EMAIL PROTECTED] wrote: > In particular zfs sometimes takes a while to return from zfs snapshot -r > tank/[EMAIL PROTECTED] in the case where there are a great many iscsi shared > volumes underneath. A little progress feedback would go a long way.
This would certainly be nice to have. There is work being done to make mounting at boot time more observable (see PSARC/2007/273) but a more general mechanism would be good. Note that the actual snapshot is a single ioctl call, but the iscsi and sharenfs fiddling would be user-level observable. > In general I feel the zfs tools lack sufficient feedback and/or logging > of actions, and this'd be a great start. Have you played with 'zpool history'? > 2. LUN management and/or general iscsi integration enhancement [this I have to leave to those more knowledgable] > 3. zfs rollback on clones. It should be possible to rollback a clone to > the origin snapshot, yes? Right now the tools won't allow it. I know you already know this, but anyway... you can do it in two steps: # zfs destroy pool/clone # zfs clone pool/[EMAIL PROTECTED] pool/clone Of course, this means briefly unmounting your clone filesystem, but the rollback does that now anyway (see 6472202), so even the snapshot-after-rollback workaround you proposed would have the same problem. Any properties you set on the original clone would have to be set again on the new clone. > Similarly the ability to do zfs send -i [clone origin snapshot1] snapshot2 > in order to efficiently transmit/backup clones would be terrific. I'm not sure exactly what you mean here. Could you give an example of the way it works now vs. the way you want it to work? Regards, markm _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
