Re: Problem with compression?
2003-02-21 18:36:49
On Fri, Feb 21, 2003 at 01:08:10PM -0800, John Oliver wrote:
> On Fri, Feb 21, 2003 at 03:46:44PM -0500, Joshua Baker-LePain wrote:
> > On Fri, 21 Feb 2003 at 11:51am, John Oliver wrote
> >
> > > I got this report from amanda. It looks to me like it's reporting that
> > > it used 48.9% of the tape (a DLT 4000 20/40GB), but that it ran out of
> > > space.
> >
> > Not quite. 48.9% of the tape was filled successfully. However...
> >
> > > FAILURE AND STRANGE DUMP SUMMARY:
> > > backup /dev/hda1 lev 1 FAILED [out of tape]
> > > backup /dev/hda1 lev 1 FAILED [dump to tape failed]
> > *snip*
> > > taper: tape Indyme008 kb 20040128 fm 19 writing file: No space left on
> > > device
> >
> > It actually wrote 20040128 KB to the tape before hitting EOT. IOW, it was
> > dumping /dev/hda1 straight to tape b/c it thought it would fit. But it
> > didn't.
>
> Why is it, then, that 17 filesystems compressed to 10GB, but this one
> filesystem isn't being compressed at all, apparently?
>
> [root@backup root]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/hda1 72572444 21325164 47560768 31% /
> none 256976 0 256976 0% /dev/shm
> /dev/hda2 2522076 80892 2313068 4% /var
>
> The whole thing is 21GB, and this is supposed to be a Level 1 backup.
> It doesn't seem reasonable to me that 20GB should be written to tape
> here.
I don't get that impression. Joshua did not mean "going straight" to
mean with no compression, he meant without going to your holding disk.
Only about 10GB of /dev/hda1 data (possibly the 10GB is after compression)
was sent to the tape but did not fit because there was already 10GB there
from the other 18 file systems.
jl
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
|
|