Re: Bad news re: new (20080817) ZFS patches and send/recv (broken again)

On Aug 17, 2009, at 17:24, Thomas Backman wrote:

> On Aug 17, 2009, at 15:25, Thomas Backman wrote:
>
>> So, I've got myself a source tree almost completely free of patches  
>> after today's batch of ZFS patches merged - all that remains is  
>> that I uncommented ps -axl from /usr/sbin/crashinfo, since it only  
>> coredumps anyway, and added CFLAGS+=-DDEBUG=1 to zfs/Makefile.
>>
>> One of the changes I didn't already have prior to this must have  
>> broken something, though, because this script worked just fine  
>> before the merges earlier today.
>> The script below is the exact same I linked in http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009174.html 
>>  back in July (URL to the script: http://exscape.org/temp/zfs_clone_panic.sh 
>>  ) - I made some local changes, thus the name invoked below.
>>
>> Now that all the patches are merged, you should need nothing but  
>> the script, bash, and the ~200MB free space on the partition  
>> containing /root/ to reproduce this problem.
>> (Note that the "no such pool" in the FIRST script is normal; it  
>> simply tries to clean up something that isn't there, without error/ 
>> sanity checking.)
>>
>> [...]
>> + zpool create -f -R /slave slave ggate666
>> ++ date +backup-%Y%m%d-%H%M
>> + NOW=backup-20090817-1522
>> + echo 'Creating snapshots'
>> Creating snapshots
>> + zfs snapshot -r tank_at_backup-20090817-1522
>> + echo 'Cloning pool'
>> Cloning pool
>> + zfs send -R tank_at_backup-20090817-1522
>> + zfs recv -vFd slave
>> cannot receive: invalid stream (malformed nvlist)
>> warning: cannot send 'tank_at_backup-20090817-1522': Broken pipe
>>
>>
>> Regards,
>> Thomas
> This is perhaps more troubling...
> [...]
> [root_at_chaos ~]# zpool create testpool ad0s1d
> [root_at_chaos ~]# zpool export testpool
> [root_at_chaos ~]# zpool import testpool
> cannot import 'testpool': no such pool available
>
> Regards,
> Thomas

OK, I tried to reproduce this in a VM... And I have to say I was a bit  
surprised: after doing an installkernel/installworld, but BEFORE  
REBOOTING (I install in "multi"-user (one user via ssh), never had a  
problem with that), the same issue has appeared, so I'm guessing  
zfs.ko can't be to blame here?
What the heck?

Regards,
Thomas