Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Apr 2013 17:30:58 -0500
From:      Larry Rosenman <ler@lerctr.org>
To:        <mm@freebsd.org>, <freebsd-fs@freebsd.org>, <freebsd-current@frreebsd.org>
Subject:   Fwd: Re: [CRASH] ZFS recv (fwd)/CURRENT
Message-ID:  <289c2c9fdee18a5acefcb225e28b9310@webmail.lerctr.org>

next in thread | raw e-mail | index | archive | help
Anyone have any ideas on how to debug this?



-------- Original Message --------
Subject: Re: [CRASH] ZFS recv (fwd)/CURRENT
Date: 2013-04-07 17:04
 From: Larry Rosenman <ler@lerctr.org>
To: Martin Matuska <mm@freebsd.org>

I updated to 249241, and got:

backups/TBH/home/unofficial-dbs@2013-04-07
received 33.2MB stream in 14 seconds (2.37MB/sec)
receiving incremental stream of vault/home/spolk@2013-04-07 into 
zroot/backups/TBH/home/spolk@2013-04-07
received 103KB stream in 1 seconds (103KB/sec)
receiving incremental stream of vault/home/cb3law@2013-04-07 into 
zroot/backups/TBH/home/cb3law@2013-04-07
received 18.5KB stream in 1 seconds (18.5KB/sec)
receiving incremental stream of vault/home/raymie@2013-04-07 into 
zroot/backups/TBH/home/raymie@2013-04-07
received 25.8KB stream in 1 seconds (25.8KB/sec)
receiving incremental stream of vault/home/ekb@2013-04-07 into 
zroot/backups/TBH/home/ekb@2013-04-07
received 1.63MB stream in 2 seconds (833KB/sec)
receiving incremental stream of vault/ldyer@2013-04-07 into 
zroot/backups/TBH/ldyer@2013-04-07
received 13.0KB stream in 1 seconds (13.0KB/sec)
receiving incremental stream of vault/tmp@2013-04-07 into 
zroot/backups/TBH/tmp@2013-04-07
received 214KB stream in 3 seconds (71.2KB/sec)
receiving incremental stream of vault/var@2013-04-07 into 
zroot/backups/TBH/var@2013-04-07
cannot receive incremental stream: invalid backup stream
#


I've seen this before, but have not been able to solve it....

I have copies of both streams.....

# cat backup-TBH-ZFS.sh
#!/bin/sh
DATE=`date "+%Y-%m-%d"`
DATE2=2013-03-24
#DATE2=`date -v "-1d" "+%Y-%m-%d"`
# snap the source
ssh root@tbh.lerctr.org zfs snapshot -r vault@${DATE}
# zfs copy the source to here.
ssh root@tbh.lerctr.org "zfs send  -R -D  -I vault@${DATE2} 
vault@${DATE} | \
      tee /tmp/backup.stream.send.${DATE} | \
      ssh home.lerctr.org \"tee /tmp/backup.stream.receive.${DATE} | \
          zfs recv -F -u -v -d zroot/backups/TBH\""
# make sure we NEVER allow the backup stuff to automount.
/sbin/zfs list -H -t filesystem -r zroot/backups/TBH| \
     awk '{printf "/sbin/zfs set canmount=noauto %s\n",$1}' | sh
#

is the script I ran.

HELP.




On 2013-04-05 15:52, Martin Matuska wrote:
> Hi larry,
> so if you desperatedly need a solution, use the attached patch
> against -CURRENT, it should work correctly.
>  A fix in Illumos + a backport to current will follow soon.
> Cheers,
>  mm
> On 5.4.2013 21:52, Matthew Ahrens wrote:
> 
>> Yep, that's basically what I'll be pushing to illumos.
>> --matt
>> On Fri, Apr 5, 2013 at 12:33 PM, Martin Matuska <mm@freebsd.org> 
>> wrote:
>> 
>>> Yes, you are right. What about the attached updated patch? Here I 
>>> use
>>> gmep for both holds and releases.
>>> Thanks,
>>> mm
>>> On 5.4.2013 21:07, Matthew Ahrens wrote:
>>>> I am working on integrating a fix into illumos. FYI, the patch you
>>>> attached will not quite work, because you are using different tags 
>>>> to
>>>> hold and release the dataset (FTAG is a macro which has a
>>>> calling-function-specific value).
>>>> --matt
>>> --
>>> Martin Matuska
>>> FreeBSD committer
>>> http://blog.vx.sk [1]
> --
> Martin Matuska
> FreeBSD committer
> http://blog.vx.sk [1]
> 
> Links:
> ------
> [1] http://blog.vx.sk

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c)     E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?289c2c9fdee18a5acefcb225e28b9310>