Jump to content

possible causes for surprising "volume corrupt" error?


Recommended Posts

hello;

 

an attempt to perform a duplicate of a remote volume led to an error with assertion that the volume was corrupt. yet disk first aid sees no problem when run on the volume. can anyone suggest casues and solutions?

 

--- the excerpt from retrospect's log ---

 

? Retrospect version 5.0.238

launched at 2003.04.18 10:01

+ Retrospect Driver Update, version 3.1.105

While scanning volume www@bataille,

Folder www@bataille/System Folder/Extensions/Scripting Additions/,

Duplicate dirid detected: 0x00000243

Folder www@bataille/System Folder/Extensions/,

Scanning incomplete, error -127 (volume corrupt?).

Folder www@bataille/System Folder/Preferences/Word-Startordner (6)/,

Duplicate dirid detected: 0x00000755

Folder www@bataille/System Folder/Preferences/,

Scanning incomplete, error -127 (volume corrupt?).

Error: Scanning incomplete, error -35 (volume doesn't exist).

Quit at 2003.04.18 10:28

 

 

? Retrospect version 5.0.238

launched at 2003.04.18 10:33

+ Retrospect Driver Update, version 3.1.105

While scanning volume www@bataille,

Folder www@bataille/System Folder/Extensions/Scripting Additions/,

Duplicate dirid detected: 0x00000243

Folder www@bataille/System Folder/Extensions/,

Scanning incomplete, error -127 (volume corrupt?).

Folder www@bataille/System Folder/Preferences/Word-Startordner (6)/,

Duplicate dirid detected: 0x00000755

Folder www@bataille/System Folder/Preferences/,

Scanning incomplete, error -127 (volume corrupt?).

While scanning volume www@bataille,

Folder www@bataille/System Folder/Extensions/Scripting Additions/,

Duplicate dirid detected: 0x00000243

Folder www@bataille/System Folder/Extensions/,

Scanning incomplete, error -127 (volume corrupt?).

Folder www@bataille/System Folder/Preferences/Word-Startordner (6)/,

Duplicate dirid detected: 0x00000755

Folder www@bataille/System Folder/Preferences/,

Scanning incomplete, error -127 (volume corrupt?).

--------

 

the first passage recounts an attempt to duplicate a desktop-mounted volume. the last message (error -35) is because i tried to unmount the volume what retrospect still had its scan window open. not good. i had to kill the finder as a consequence.

 

the second passage recounts an attempt to duplicate the volume as retrospect-mounted.

 

the intended script is a volume-to-folder duplicate, set to replace the entire folder contents.

 

the source volume is one of six present on a system running macos Z1-9.1 (that international os 9) on a 7300/200Mhz/128M with the original 2G qunatum fireball on scsi bus 0

 

the destination folder is present on a system running Mac OS X 10.2.5 (6L29) on a G4/2x1.25Ghz/1,5G.

it is located on an external 200G lacie firewire drive.

 

retrospect is the 5.0.238 update.

 

the scan was started by explicitly activating the select files action from the backup configuration dialog.

 

?

Link to comment
Share on other sites

as the next step, i decided to use the retrospect client on the remote workstation. i had wanted to avoid this, suspecting i might have problems as it is still a 4.2 client.

 

turns out it executed the backup noting any corruption problems.

 

so, what is retrospect seeing where it mounts the volume on the desktop, or uses the odx-mounted volume on the desktop, which is does not see when it works through the retrospect client?

 

...

Link to comment
Share on other sites

the remote workstation, as noted, is os9.1. the volumes are shared partitions with client access over tcp/ip enabled

 

for the first passage (the "desktop-mounted" case) i suspect it was appleshare over tcp/ip as tcp/ip connections are enabled in the remote file sharing control panel and i mounted the volume with "connect to server" on the osx workstation. i just mounted it again to check and the volume's fileinfo says nothing more than "format: appelshare".

 

for the second passage it's however retrospect mounts it, but with the same proviso as to the tcp/ip-enabled remote.

 

...

 

Link to comment
Share on other sites

We created the Retrospect Client to avoid this type of strange behavior when doing backups via filesharing. Mac OS X just complicates the entire Filesharing process. Some files that are in use by the OS or have special file characters can not be handled via filesharing.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...