3.10 Access U-boot Environment from Linux.(hypothetically, unlimited amount of data can be lost, it could be a 100GB file. Wors case (maximal loss): Each corrupted block contains the header of a big file. #ANDROID WIKI READER FOR BZ2 FILES ARCHIVE#If your archive gets corrupted, you loose a multiple of 100kb, against a multiple of 900kb if you use 900kb block-size, which could actually make a BIG difference!Īddendum : Expected Minimal Data Loss Best case (minimal loss): No file has its header within a corrupted block and its data block in others. If you are saving critical stuff, you could tell BZip2 to use 100kb block-size. To sum it up: we lost one block, and any file with either its header or a part of the body in that block. tar.bz2 file, EXCEPT what was within the corrupted bzip block, and everything until the first clean header after the corrupted block. Here, we could restore everything from a. Sad story, huh ? Second thing, tar archives are quite fine with data corrupting, at least, they are better than gzipped files. For instance, thou shall not use gzip compressed archives for relatively critical stuffs, because if it ever gets corrupted, well, it's just lost. Yoodelihoo ! You did it !! Food for thoughts. We will just bunzip all the small archives into one recovery1.tar file: Here, we have the beginning of a tar file, nothing's corrupted, but the tar file is not complete. Let's tackle everything up to the first corrupted block ! Copy all blocks from block 11 to the last block into recovery2. Copy all blocks from block 1 to block 9 (our "clean" blocks until our corrupted block) into recovery1. Lets create 2 directories, well call it "recovery1" and "recovery2". We'll have to work on these 2 parts separately. ("2") So, you have blocks 1-9 fine, then a dumb corrupted block, then everything is fine again. Ok, let's say you have a corrupted block, which is block no. Let's focus on the recovery process, now. , and finally from 15th to the end of file. The process would be the same if you had 15 corrupted blocks, but you had to restore from begining of file to first corrupted block, then from 1st corrupted block to 2nd, then from 2nd to 3d. Note: We are here restoring from a file with only 1 corrupted block. guess what, corrupted files don't generate this kind of candid output ).(this actually parses the output of bzip2 -t to extract only files which don't end up with a candid "ok" That's why it's generating soooo many small files. What bzip2recover does, is splitting a bzip2 archive into many smaller bzip2 archives (one per block, actually). , 900k bytes big, depending on what compression options you used - default is 900k). Bzip2 compressed file are divided into blocks (each block being 100k, 200k. Hey, but what's that bzip2recover command. Here, we'll use the magic bzip2recover command. Getting the data blocks out of the bzip2 archive.Ĭd into recovery. Let's assume you did that, and that you called that folder recovery/. You might want to create a folder dedicated to that purpose, and copy your 2 in it. Note: The next step will generate A LOT of files. Instead, we'll unleash the power of Bzip2 and its builtin Blockwise CRC checks. You can't fix archives with ropes, nor with guns. Should I go for the rope or the gun ? General Information. If it's fine, well, enjoy your day Otherwise, read on, we'll recover it. This will tell you if your bzipped archive is fine, or not.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |