Re: gzip / compression problems
- From: "Andy Savidge" <asavidge@xxxxxxxxx>
- Date: 28 Feb 2007 10:43:40 -0800
Is the entire file bad?
No... the tgz's will untar to a certain extent (always the same point
on each different archive)
First: Are the files closed which are being backed up? For example, I
have seen an error issued by rsync which states, "file changed as we read
it," or something to that effect. If your files are open, then you may
need to use a device mapper (snapshot-origin) solution to freeze your
backup.
We thought this at first, but I've duplicated the problem with files
that are definitely not being used.
Also, I have seen some Microsoft Access databases not be backed up because
of a restrictive file lock (that is, they are simply omitted from the
backup, but not corrupted.) This is something which must also be watched
for, lest the backup be incomplete.
If we ever get this sorted, this will be something we'll watch out
for. Thanks for the heads-up.
Another possibility:
Since you are using a recent GNU/Linux distribution, file sizes greater
than 4G should be okay. However, it might be worth checking that the
corruption doesn't occur when a certain file size is reached.
Like I said... we have a 175MB gzip that also dies. Yet ISTR we have
some of 300MB that WILL gunzip.
Very confusing.
.
- References:
- gzip / compression problems
- From: Andy Savidge
- Re: gzip / compression problems
- From: Douglas Mayne
- gzip / compression problems
- Prev by Date: Re: Ubuntu Screen Resolution!! SORTED!
- Next by Date: IceWM: Changing the color of the mouse pointer in IceWM
- Previous by thread: Re: gzip / compression problems
- Next by thread: modinfo searching
- Index(es):
Relevant Pages
|
