Hello > This seems like a reasonable proposal to enhance zfs list. But it would > also be good to add as few new options to zfs list as possible. So it > probably makes sense to add at most one of these new options. Or > perhaps add an optional depth argument to the -r option instead? > > As you point out, the -c option is user friendly while the -depth (or > maybe -d) option is more general. There have been several requests for > the -c option. Would anyone prefer the -depth option? In what cases > would this be used?
I'd have a few more proposals how to improve zfs list if they don't contravene the concept of zfs list command. Currently zfs list returns error "operation not applicable to datasets of this type" if you try to list for ex.: "zfs list -t snapshot file/system" returns above error while it could return what you actually asked - the list of all snapshots of "file/system". Similar case is if you try "zfs list file/sys...@snapshot" - can zfs be more smart to return the snapshot instead of error message if dataset name contains "@" in its name? Other thing is zfs list performance... even if you want to get the list of snapshots with no other properties "zfs list -oname -t snapshot -r file/system" it still takes quite long time if there are hundreds of snapshots, while "ls /file/system/.zfs/snapshot" returns immediately. Can this also be improved somehow please? Thanks Mike _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
