Jump to content

Recommended Posts

i observe two kinds of errors when performing backups to file sets and duplicate volumes.

 

the first is sporadic media error claims, eg:

 

- 3/25/2003 7:56:06 AM: Copying osx.tschichold?

Can't write file ?pgsql-7.3.bom?, error -36 (i/o error, bad media?), path: ?osx.tschichold/Library/Receipts/pgsql-7.3.pkg/Contents/Resources/pgsql-7.3.bom?.

 

this although subsequent examination with filemerge indicates that the original and the duplicate are identical

 

 

the second is claimed differences in modification time, eg:

 

- 3/25/2003 8:44:10 AM: Copying raidin.tschichold?

3/25/2003 10:15:13 AM: Comparing raidin.tschichold on backup.tschichold?

File ?xml-parser.lisp?: different modification date/time (src: 10/27/2002 1:12:30 AM, dest: 10/27/2002 2:12:30 AM), path: ?raidin.tschichold/Backups/Development/xml/xml-20021028/code/xparser/xml-parser.lisp?.

 

whereby a subsequent examination of the respective files indicates that their modification times are, "in fact" identical:

 

[tschichold:~] janson% ls -l /Volumes/raidin.tschichold/Backups/Development/xml/xml-20021028/code/xparser/xml-parser.lisp

-rw-r--r-- 1 janson staff 42067 Oct 27 01:12 /Volumes/raidin.tschichold/Backups/Development/xml/xml-20021028/code/xparser/xml-parser.lisp

[tschichold:~] janson% ls -l /Volumes/backup.tschichold/raidin.tschichold/Backups/Development/xml/xml-20021028/code/xparser/xml-parser.lisp

-rw-r--r-- 1 janson staff 42067 Oct 27 02:12 /Volumes/backup.tschichold/raidin.tschichold/Backups/Development/xml/xml-20021028/code/xparser/xml-parser.lisp

[tschichold:~] janson%

 

does anyone know what could be causing this?

...

 

Link to comment
Share on other sites

Quote:

- 3/25/2003 7:56:06 AM: Copying osx.tschichold?

 

Can't write file ?pgsql-7.3.bom?, error -36 (i/o error, bad media?), path: ?osx.tschichold/Library/Receipts/pgsql-7.3.pkg/Contents/Resources/pgsql-7.3.bom?.

 


 

 

 

This is actually an Apple OS generated error message.

 

 

 

Apple's TIL entry for this error:

 

 

 

Type -36 error (I/O Errors) This file is having difficulty while either reading from the drive or writing to the drive. The file may have been improperly written data to the drive or the hard drive or disk may be damaged. This is almost always indicative of a media error (hard error on

 

the disk). Sometimes (rarely) it is transient.

 

 

 

Solutions: Try copying the file to another drive. Use a disk recovery software, such as Disk First Aid to examine the disk. Once in a while this will allow you to read the data. The file in question should be restored from a backup that was stored on a different disk. Regular backups can reduce the time to recover from this error.

 

 

 

Quote:

3/25/2003 10:15:13 AM: Comparing raidin.tschichold on backup.tschichold?

 

File ?xml-parser.lisp?: different modification date/time (src: 10/27/2002 1:12:30 AM, dest: 10/27/2002 2:12:30 AM), path: ?

 


 

 

 

From the Knowledgebase:

 

 

 

TITLE: I noticed that the creation date on some of my files changes by exactly 1 hour when duplicating from disk to disk with Retrospect 5.0. Can this be avoided?

 

 

 

Article ID: 27306

 

Date Created: 2002-07-18

 

Date Modified: 2002-07-18

 

 

 

Discussion

 

This can happen to some files that are created on the day we switch to Daylight Savings Time. Dantz has reported the problem to Apple and we are working with Apple forward a resolution.

 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...