[Pluto-help] archivio tar.gz

[Aljosa Karamazov]

sono ancora qua :-)
l'altr giorno avevo postato un problema con un archivio tar.gz 
danneggiato...
ho apprezzato le risposte ma, ahime, non sono servite. Ho trovato questo 
metodo in rete, pero' ho un po di difficolta' a metterlo in pratica. Non e' 
che qualcuno mi da una mano ad interpretarlo?

ecco cosa dice


                Recovering a damaged .gz file

Here is how you can try to recover your data if it is extremely
valuable to you. Do this only if it's worth it, because it will
certainly take a lot of time, and it is not even guaranteed to get
back all the data correctly.  First, make copies of all the files you
still have, to avoid deleting them by mistake. Then work only on the
copies. You will also have to patch the gzip sources.

You must hope that all the bad sectors are somewhat grouped
together. You can recover the portion before the bad sectors, and you
may be able to recover some data after all bad sectors. You can't
recover data bewteen those bad sectors, unless they are very far apart
from each other.

To recover the portion before the bad sectors, just do:

  gunzip < damaged.gz > part1

gunzip will stop when it sees the bad data. All data in the file "part1"
is guaranteed to be correct, but of course the rest will be missing.
If the file "damaged" is a .tar file, you can recover some files with:

  gunzip < damaged.tar.gz | tar xvf -

gunzip and tar will complain at some point, but tar may have recovered
some files already.

%%%fino qui tutto bene

Now let's try to recover something after the bad sectors.  You first
have to find the boundary of the first undamaged compression block
after the damaged portion.  The boundary is bit aligned. To find the
damaged portion, add
            fprintf(stderr, "bytes_in %ld\n", bytes_in);
before:
            error("invalid compressed data--format violated");

in unzip.c.

%%% anche qua riesco

Then round bytes_in this to the next disk block boundary
and create a new .gz file by concatenating a valid .gz header and
the data believed to be undamaged. Then try repeatedly "gzip -t"
on the new .gz file, removing from 1 bit to 8*64K bits from the
compressed data portion, until you get a crc error instead of
a "format violated" error. At this point do

  gunzip < damaged.gz > damaged

The gzip CRC will always fail because you will miss some 'history',
but after some time, the history effect will be reduced and you might
be able to recover part of the data. You will have no guarantee that
the data will be correct except by manual inspection.

%%%come faccio a fare sto pezzo?

To get a valid .gz header, look at the file algorithm.doc in the gzip
distribution, or just copy the header from any valid .gz file. The
header ends at the zero terminated file name.  To speed up the search
for a block header, the first 3 bits should be 0,0,1 (starting from
least significant bit) so that when aligned on a byte boundary you get
first_byte & 7 == 4. So you only have to test about 1/8 of all
possible bit alignments. Of course if your block was not byte aligned
you have to bit-shift the entire file.

As you can see, all this is not a trivial task, so you should attempt
it only if your data is very valuable. gzip 2.0 will have a new
blocksize option, allowing to recover easily all undamaged blocks
after the damaged portion.

%%%grazie a tutti,
trilin

P.S. vista la gravita' della mia situazione vado contro le regole di 
Linux.... offro una bottiglia di rosso di Valtellina (vino) a chi solvera' 
il mio dilemma ;-)




Apollione: ...riesca o fallisca,
           il progetto non è men bello.

           Jost van den Vondel, LUCIFERO
            Atto II, scena IV


_________________________________________________________________
Scarica GRATUITAMENTE MSN Explorer dall'indirizzo 
http://explorer.msn.it/intl.asp.