|
#1
|
|||
|
|||
Hmm, I removed the offending file from the source drive and re-ran the script (in Smart Update mode). This time it gave the same error but on another file. There is definitely enough space (source = 32 Gb, target = 120 Gb).
I've now tried running a full erase and then backup and this has got passed the problem files. Keith P.S. Both these files were possibly being modified at the time I first tried backing them up and getting the error. |
#2
|
||||
|
||||
Well, I was wondering if the disk -- at the time you got that error -- had enough space on it. I'm guessing it was actually full.
There's a bug in a low-level Apple routine we use where, if certain files are written to at the same moment we're copying it -- typically over and over -- it'll look larger than it really is, and get copied until the disk is full. This happens at a point where we don't have control, and while we've reported it to Apple, it's hard to work around... but we're trying...
__________________
--Dave Nanian |
#3
|
|||
|
|||
Spotlight is the problem
I think Spotlight is the problem. I found it refused to make the backup volume private. Then, I found I had to run Disk Utility and repair the volume...it found many errors.
I just could not get Spotlight to stop indexing the volume. Finally, I just erased the entire backup, and I'm copying fresh. The backup showed less space than it should have; it's identical in size to the original yet showed no space free. Last edited by Mimetic; 07-17-2007 at 02:28 AM. Reason: update |
Currently Active Users Viewing This Thread: 3 (0 members and 3 guests) | |
|
|