On Tue, 23 May 2006, Ian Turner wrote:
> On Tuesday 23 May 2006 16:28, Jon LaBadie wrote:
> > But running out of disk space caused me to look more
> > closely at the situation and I realized that the failed
> > taping is left on the disk. This of course mimics what
> > happens on physical tape. H
On Tue, May 23, 2006 at 04:28:31PM -0400, Jon LaBadie wrote:
> But running out of disk space caused me to look more
> closely at the situation and I realized that the failed
> taping is left on the disk. This of course mimics what
> happens on physical tape. However with the file:driver
> if this
Jon,
There is no good short-term solution to this problem. Sorry. :-( Tape spanning
helps, but is not a panacea.
This is one of the limitations of the vtape API that I was talking about -- it
tries to reimplement tape semantics on a filesystem, even when that doesn't
make sense.
When the Devi
I'm running vtapes on a new server. The vtapes
are split across two external disk drives.
Realizing that some tapes would not fill completely,
I decided that rather than define the tape size to be
exactly disk/N, I would add a fudge factor to the size.
Things worked exactly as anticipated. The
