Yep, looks like a bug to me. The libzfs code should be flagging that as
an invalid snapshot name before passing it down to the kernel (which is
returning EINVAL). I''ve filed:
6404609 libzfs misses invalid snapshot name
To track this issue. Thanks for using (and breaking) ZFS.
- Eric
On Sun, Mar 26, 2006 at 01:44:46PM -0800, Thomas Maier-Komor
wrote:> setup:
> # uname -a
> SunOS azalin 5.11 opensol-20060320 sun4u sparc SUNW,Sun-Blade-2500
> # zfs list
> NAME USED AVAIL REFER MOUNTPOINT
> zfs 5,52G 2,78G 10K /zfs
> zfs/bfu 1,52G 2,78G 1,52G /zfs/bfu
> zfs/test 8K 2,78G 8K /zfs/test
> zfs/thomas 2,82G 3,97G 158M /zfs/thomas
> zfs/thomas/mp3s 733M 3,97G 733M /zfs/thomas/mp3s
> zfs/thomas/photos 1,95G 3,97G 1,95G /zfs/thomas/photos
> zfs/thomas/work 8K 3,97G 8K /zfs/thomas/work
>
> problem:
> # zfs snapshot zfs at thomas/mp3s
> internal error: unexpected error 22 at line 2271 of
../common/libzfs_dataset.c
>
> I know this is an invalid input, but the message could be a little bit more
helpful.
>
> Cheers,
> Tom
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
--
Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock