Amanda-Users

Re: Trap for the unwary user: split_diskbuffer

2009-05-11 10:47:55
Subject: Re: Trap for the unwary user: split_diskbuffer
From: "Dustin J. Mitchell" <dustin AT zmanda DOT com>
To: Uwe Menges <uwe.menges AT web DOT de>
Date: Mon, 11 May 2009 10:12:46 -0400
On Thu, Mar 5, 2009 at 10:32 PM, Uwe Menges <uwe.menges AT web DOT de> wrote:
> Another quick check with "ls -l /proc/`pidof taper`/fd/" showed me it was
> really true, the taper was happily reading its own amanda-split-buffer-* files
> (marked as (deleted) but it nevertheless had the file handles), writing them
> again as amanda-split-buffer-* files...

Now that I've been over this code several times with a
fine-toothed-comb (I've rewritten it to use Perl and the transfer
architecture), I can't figure out what happened here.  It makes sense
that the *taper* was reading and writing from its split-buffer files
-- that's what they're for!  If *gnutar* were reading the split files,
there would be a problem, since those files are created with mkstemp
and immediately unlinked.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

<Prev in Thread] Current Thread [Next in Thread>