Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!unido!tools!fl From: fl@tools.uucp (Frank Lancaster) Newsgroups: comp.sys.acorn Subject: Re: TAR & Disk Corruption. Message-ID: Date: 24 Jun 91 09:20:43 GMT References: <1991Jun19.142743.5299@imada.ou.dk> Sender: news@tools.UUCP Distribution: comp Organization: TooLs GmbH, Bonn, Germany Lines: 21 In-reply-to: jho@imada.ou.dk's message of 19 Jun 91 14:27:43 GMT Well, the heat has now steamed off... The problem with these 'bug' reports is that I am mostly unable to reproduce them. If someone reports that his hard disk has been mangled, I try to understand what happened and try to reproduce it. But up to now I haven't a clue as how something like breaking directories should be caused by tar. The one time this happened to me wasn't with tar. I did a *compact before I wanted to do a backup (I don't know why, maybe I'm becoming senile). After the compact about 20% of the hard disc was garbage. I was somewhat upset. This happened twice without using tar, only using the OS. It was with 80MB hard discs. Once even the disk map got corrupted but there were no bad sectors on the disc. With a 20MB disc I never had problems. I have the feeling that the problem may be in the adfs code. Tar only reads and writes files and creates directories all with OS routines (actually mostly the C library). Frank Lancaster