Hello All,
For the past couple months I’ve had one host consistently fail when
all the hosts (28 total) are backed up. But if I run the backup
manually for just that host, or delete every other host from the
disklist, it works fine!
Here’s the latest dump summary, with just the host “manganese”
to remove the alias from the disklist. The
alias came first in the list and was backing up normally, while
manganese was not.
Thanks anyway. Apparently all this time I just needed to post to the
list to figure it out!
-- Michael
On Wed, Dec 7, 2011 at 3:27 PM, Michael Burk bur...@gmail.com wrote
Hi,
When I try to restore larger zip ( 4GB?) files from Windows backups,
they are corrupted.
The Amanda server is Solaris 10 running Amanda 2.6.1p1. The client is
Windows Server 2003, and I used the ZWCInstaller-Community-26.zip from
April 10.
I used amfetchdump with -l on the Amanda server to
- unforced, with compression and index
Thanks,
Michael
On Mon, Sep 28, 2009 at 2:46 PM, Michael Burk bur...@gmail.com wrote:
Hi Dustin,
Great analysis; thanks for sharing the details of the problem.
On Mon, Sep 28, 2009 at 12:11 PM, Dustin J. Mitchell dus...@zmanda.com
wrote:
while putting
Hi Dustin,
Great analysis; thanks for sharing the details of the problem.
On Mon, Sep 28, 2009 at 12:11 PM, Dustin J. Mitchell dus...@zmanda.com wrote:
while putting together the patch
(attached),
I patched the 0928 snapshot, but it didn't compile:
util.c: In function `openbsd_fd_inform':
Hi Dustin,
I hope you have recovered from your shock regarding threads on OpenBSD ;-)
Here's an idea for a partial fix; I have no idea how easy or difficult
it would be.
Until threads on OpenBSD work the way you expect, would it be possible
to remove the thread dependencies when doing a build
Hi Dustin - one question before I post on the OpenBSD list. In reviewing a
post Stan made a couple weeks ago to the OpenBSD list, someone asked if
Amanda uses pthreads. I noticed that ldd reports that the binaries link to
libpthread. Does Amanda use pthreads, either directly or through some other
Hi Dustin,
Thanks again for your help. Here's the output of the test prog:
bu...@selenium$ ./test parent
pipe = r...@3 w...@4
parent closing
parent sleeping
child closing p[0]
child exec'ing
child duping
child closing B
child writing
child write done
parent reading
parent got 4 bytes
yes gzip strange, index tee strange, dump failed
yes * * success, nothing strange
On Fri, Sep 4, 2009 at 3:01 PM, Nathan Stratton Treadway natha...@ontko.com
wrote:
On Wed, Sep 02, 2009 at 11:11:39 -0600, Michael Burk wrote:
This was a good idea; I tried
Stratton Treadway natha...@ontko.com
wrote:
On Fri, Sep 04, 2009 at 16:41:31 -0600, Michael Burk wrote:
Nathan, I think the following truth table will answer all your questions!
(view in monospace font)
Patch gzipIndex Result
no no no dump failed (end of tape
On Fri, Sep 4, 2009 at 6:21 PM, Nathan Stratton Treadway natha...@ontko.com
wrote:
snip
But it sounds like you are saying that the one-line patch, which touched
only datafd, actually fixed both problems as well
Exactly.
at 1:43 PM, Nathan Stratton Treadway natha...@ontko.com
wrote:
On Tue, Sep 01, 2009 at 11:31:26 -0600, Michael Burk wrote:
I applied the 3-line patch to the 0831 snapshot and ran a full backup on
both machines, with 4 file systems each. All 8 completed successfully
with
no strange messages
I modified sendbackup-dump.c to run ktrace, e.g.:
/usr/bin/ktrace -id -t censw -f /tmp/sendbackup.trc /sbin/dump 0usf 1048576
- /dev/rsd0d
Unfortunately, I don't get a backup, even with the patch applied. The trace
output shows write errors because of a broken pipe with or without the
patches,
I checked the errata for OpenBSD 4.5, but saw nothing that looked related.
I applied the patch to the 0831 snapshot and am building it now. After we
find the minimal patch, as Jean-Louis said, I'll post on the OpenBSD-misc
list to see if anyone has an explanation.
Thanks guys for working on this
that helps.
-- Michael
On Tue, Sep 1, 2009 at 11:31 AM, Michael Burk bur...@gmail.com wrote:
I applied the 3-line patch to the 0831 snapshot and ran a full backup on
both machines, with 4 file systems each. All 8 completed successfully with
no strange messages.
Next, I commented out the 3
fix the problem somehow.
Anything else you want to try before I ask for help on the OpenBSD list?
Thanks,
Michael
On Tue, Sep 1, 2009 at 9:32 AM, Michael Burk bur...@gmail.com wrote:
I checked the errata for OpenBSD 4.5, but saw nothing that looked related.
I applied the patch to the 0831
instead of the data path. The backup is
correct but your index is empty. That's why you get a STRANGE result instead
of a failure.
Can you post a sendbackup.*.debug for a dle that failed?
Jean-Louis
Michael Burk wrote:
Hello,
I applied the patches to the 20090827 snapshot. I tried it on two
on this system?
The patch check before and after the write if the pipe is in O_NONBLOCK or
not and give an error if it is.
I'm totally lost since it is in blocking mode and you get EAGAIN, which is
impossible
Jean-louis
Michael Burk wrote:
Here are the two sendbackup.*.debug files
Sun Aug 30 22:29:14
2009
-- Michael
On Fri, Aug 28, 2009 at 5:22 AM, stan st...@panix.com wrote:
On Thu, Aug 27, 2009 at 03:35:47PM -0600, Michael Burk wrote:
Cool - can you send me the patch? Or is it already in the 0826 snapshot?
FYI - I got 2.5.0p2 working, but could never get 2.5.1p3
I'm using bsdtcp auth.
I'll try 2.5.1 today or tomorrow, to see if I can narrow down the range of
releases in which OpenBSD support broke.
-- Michael
On Mon, Aug 24, 2009 at 5:17 AM, stan st...@panix.com wrote:
On Fri, Aug 21, 2009 at 03:53:13PM -0600, Michael Burk wrote:
Stan's not alone
Stan's not alone on this one. I have two OpenBSD 4.5 machines also on Sun
SPARC hardware. I had this same trouble a couple months ago with 2.6.1, but
didn't have time to look deeper. After seeing this discussion, I built
amanda-2.6.2alpha-20090812 (can't get 0820 to compile). I'm getting exactly
21 matches
Mail list logo
