Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: Bug in when_overwrite() usage in planner.c

  1. #11


    Quote Originally Posted by ckeasling View Post
    I encountered two additional bugs and have rolled back to 3.3.9.

    The first is a HEADER_DONE not set error on a single dataset of a ZFS pool. We're dumping in the neighborhood of 20 small datasets (one per user) on a server running zfsonlinux, and each run resulted in precisely one of these failing with the HEADER_DONE not set error. It was not the same dataset each time. I've never encountered this error before, and digging into the code it wasn't immediately apparent why this was happening. The error did not occur with last night's 3.3.9 run.

    The other error, which was a (literal) showstopper, was a taper hang. The run two nights ago never finished. At the time of investigation there were 8 idle dumper threads and 3 taper threads, with the driver reporting that the taper was writing. Two of the tapers were in a futex wait channel and the third was in a poll_s... wchan. I ultimately sent sigterm to this last taper and amanda immediately wrapped things up with a taper protocol error. The logs didn't report anything unusual prior to the hang and there's no evidence of any i/o problems with the hardware or network. And the problem did not occur with 3.3.9.

    So it seems 3.4 is not ready for primetime, at least not for us.
    So I think you should use 3.3.2, to avoid trouble

  2. #12
    Join Date
    Nov 2005


    Which application are you using to do the backup? amzfs-sendrecv?
    Are you using amanda-3.4on both server and client?

    Can you post the dumper.<datatstamp>.debug file from the server and the amandad, sendbackup and amzfs-sendrecv debug files from the client?
    The taper hang can be related to the first issue, are you using a holding disk? or dumping directly to tape?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts