griggs@cory.Berkeley.EDU (Ted Griggs) (12/02/88)
I was wondering if this is a bug in DiskSalv1.3 (or just that I'm doing something wrong): When disksalv'ing a crashed ffs partition to another ffs partition, I noticed that every large file was truncated to 36864 bytes. I believe "large file" in this case means any file greater than 36864 bytes, since smaller files restored perfectly. I used the recently posted disksalv1.3 from binaries. Does this mean its back to DiskDoctor? Thanks in advance for any information, Ted Griggs ucbvax!cory!griggs
daveh@cbmvax.UUCP (Dave Haynie) (12/03/88)
in article <7891@pasteur.Berkeley.EDU>, griggs@cory.Berkeley.EDU (Ted Griggs) says: > Keywords: large files truncated > When disksalv'ing a crashed ffs partition to another ffs partition, > I noticed that every large file was truncated to 36864 bytes. I believe > "large file" in this case means any file greater than 36864 bytes, since > smaller files restored perfectly. The magic 36864 number is 72 * 512. The number 72 represents the number of data block keys in a file header, 512 of course being the length of an FFS block. Something in DiskSalv V1.3 causes the extension block to be missed somehow with FFS recoveries. > I used the recently posted disksalv1.3 from binaries. > Does this mean its back to DiskDoctor? No, cause fortunately, DiskSalv V1.32 should be available from binaries soon. This version, according to all the beta testers reporting, fixes this bug. I could never reproduce it myself. There are several more minor bugs also fixed. > Thanks in advance for any information, Thanks for the message, anyway. I am interested in hearing of any problems in DiskSalv. > Ted Griggs > ucbvax!cory!griggs -- Dave Haynie "The 32 Bit Guy" Commodore-Amiga "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: D-DAVE H BIX: hazy Amiga -- It's not just a job, it's an obsession