On 26/06/2007, at 12:08 PM, [EMAIL PROTECTED] wrote:
I've been saving up a few wishlist items for zfs. Time to share.
1. A verbose (-v) option to the zfs commandline.
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. In general I feel the zfs tools lack
sufficient feedback and/or logging of actions, and this'd be a
great start.
Since IIRC snapshot -r is supposed to be atomic (one TXG) I'm not
sure that progress reports would be meaningful.
Have you seen zpool history?
2. LUN management and/or general iscsi integration enhancement
Some of these iscsi volumes I'd like to be under the same target
but with different LUNs. A means for mapping that would be
excellent. As would a means to specify the IQN explicitly, and the
set of permitted initiators.
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 I can hack in a race-sensitive snapshot of the new
volume immediately after cloning, but I already have many hundreds
of entities and I'm trying not to proliferate them.
Yes, since rollback only takes the snapshot as an argument there
seems not to be a way to rollback a clone to the "fork" snapshot.
You could, of course just blow away the clone and make a new one from
the same snapshot
Similarly the ability to do zfs send -i [clone origin snapshot1]
snapshot2 in order to efficiently transmit/backup clones would be
terrific.
It seems that a way to use [EMAIL PROTECTED] as an alias for
[EMAIL PROTECTED] would solve both of these problems, at least at the
user interface level.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
