Xref: utzoo comp.unix.xenix.misc:223 comp.unix.xenix.sco:2615 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!yonder!michael From: michael@yonder.UUCP (Michael E. Haws) Newsgroups: comp.unix.xenix.misc,comp.unix.xenix.sco Subject: Re: Need assistance with afio problem. Keywords: afio Message-ID: <447@yonder.UUCP> Date: 27 May 91 17:24:15 GMT References: <446@yonder.UUCP> <1991May26.203103.19212@chinacat.unicom.com> Organization: Redstone Enterprises, Lakewood, Co Lines: 33 In article <1991May26.203103.19212@chinacat.unicom.com>, chip@chinacat.unicom.com (Chip Rosenthal) writes: > In article <446@yonder.UUCP> michael@yonder.UUCP (Michael E. Haws) writes: > >find /usr /u -print | afio -oZ -L/back/log | dd of=/dev/rct0 ibs=10b obs=1000b > I'm concerned that the `Z' option > might be compressing the backup. It is. > If this is the case, methinks you > are making a *big* mistake. For all intents and purposes, if one bit > is corrupt in an LZW compressed file, the following contents are > unrecoverable. Using compress on backup volumes is penny-wise and > megatons-foolish. > > -- > Chip Rosenthal | Don't play so > Unicom Systems Development 512-482-8260 | loud, Mr. Collins. It is my impression that you are suggesting that I never keep compressed data on my hard disk, since this data would be subject to the same potential problem when trying to recover it from a tape archive. Or have I missed something? As for the contents following a corrupt bit being unrecoverable, I intentionally corrupted a random bit in a compressed file and was able to successfully uncompress the file and although it did have the random character corrupted, the remainder of the file was intact. -- Michael E. Haws "Keep the blue side up" w - (303) 986-2370 boulder!yonder!michael h - (303) 232-0628 michael%yonder@csn.org