Input/output error - LSMMap2.corrupt
 

Hi Dave,

Chronic backup failure.... Here's the log:

|12:43:19 PM|Info| WARNING: Caught I/O exception(5): Input/output error
|12:43:19 PM|Info| WARNING: Source: /Users/Farm/Library/Mail/LSMMap2.corrupt,
lstat(): 0
|12:43:19 PM|Info| WARNING: Target: /Volumes/iMandala
Clone/Users/Farm/Library/Mail/LSMMap2.corrupt, lstat(): 0
|12:43:19 PM|Info| Logging attributes for item:
/Users/Farm/Library/Mail/LSMMap2.corrupt of type: 8
|12:43:19 PM|Info| Type:
|12:43:19 PM|Info| Creator:
|12:43:19 PM|Info| kIsOnDesk: NO
|12:43:19 PM|Info| kColor: NO
|12:43:19 PM|Info| kIsShared: NO
|12:43:19 PM|Info| kHasNoINITs: NO
|12:43:19 PM|Info| kHasBeenInited: NO
|12:43:19 PM|Info| kHasCustomIcon: NO
|12:43:19 PM|Info| kIsStationery: NO
|12:43:19 PM|Info| kNameLocked: NO
|12:43:19 PM|Info| kHasBundle: NO
|12:43:19 PM|Info| kIsInvisible: NO
|12:43:19 PM|Info| kIsAlias: NO
|12:43:19 PM|Error| SVUclone: Error: Couldn't create
|12:43:19 PM|Error| : Input/output error
|12:43:19 PM|Error| SVUclone: Error copying /Users/Farm/Library/Mail/LSMMap2.corrupt to
/Volumes/iMandala Clone/Users/Farm/Library/Mail/LSMMap2.corrupt of type 8
|12:43:19 PM|Error| : Input/output error
|12:43:19 PM|Info| Error copying /Users/Farm/Library/Mail/LSMMap2.corrupt to
/Volumes/iMandala Clone/Users/Farm/Library/Mail/LSMMap2.corrupt of type 8


We had some issues with mail recently and have reinstalled/updated it. any ideas? Thanks!

rg

Given that the file itself has ".corrupt" in the extension, my guess is that this file is bad. I'd remove it and empty your trash.

what i figured, but wanted to be sure as my partner is running the backup at home (where I am not) and I am not able to do a detailed search on the machine right now to be sure that this is an actual file extension or if this is something that is part of the log message.

Thanks! I will give it a try.

Yeah, that's an actual file extension... it might be easiest to just use Finder's "Go To Folder" command to open /Users/Farm/Library/Mail -- that's where the file is.

new errors!
 

The remove of the .corrupt file worked, but now file after file seems to be giving issue. These are illustrator files (that are relatively new)...

here is the latest log:

|02:55:32 PM|Info| Ignoring /.Trashes
|03:03:14 PM|Info| WARNING: Caught I/O exception(5): Input/output error
|03:03:14 PM|Info| WARNING: Source: /Users/Farm/Mandala Farm Stuff/CSA/CSA
2006/newsletters 2006/#2 2006front.ai, lstat(): 0
|03:03:14 PM|Info| WARNING: Target: /Volumes/iMandala Clone/Users/Farm/Mandala
Farm Stuff/CSA/CSA 2006/newsletters 2006/#2 2006front.ai, lstat(): 0
|03:03:14 PM|Info| Logging attributes for item: /Users/Farm/Mandala Farm
Stuff/CSA/CSA 2006/newsletters 2006/#2 2006front.ai of type: 8
|03:03:14 PM|Info| Type: PDF
|03:03:14 PM|Info| Creator: ART5
|03:03:14 PM|Info| kIsOnDesk: NO
|03:03:14 PM|Info| kColor: NO
|03:03:14 PM|Info| kIsShared: NO
|03:03:14 PM|Info| kHasNoINITs: NO
|03:03:14 PM|Info| kHasBeenInited: NO
|03:03:14 PM|Info| kHasCustomIcon: YES
|03:03:14 PM|Info| kIsStationery: NO
|03:03:14 PM|Info| kNameLocked: NO
|03:03:14 PM|Info| kHasBundle: NO
|03:03:14 PM|Info| kIsInvisible: NO
|03:03:14 PM|Info| kIsAlias: NO
|03:03:14 PM|Info| Error copying /Users/Farm/Mandala Farm Stuff/CSA/CSA
2006/newsletters 2006/#2 2006front.ai to /Volumes/iMandala Clone/Users/Farm/Mandala Farm
Stuff/CSA/CSA 2006/newsletters 2006/#2 2006front.ai of type 8
|03:03:14 PM|Error| SVUclone: Error: Couldn't create
|03:03:14 PM|Error| : Input/output error
|03:03:14 PM|Error| SVUclone: Error copying /Users/Farm/Mandala Farm Stuff/CSA/CSA
2006/newsletters 2006/#2 2006front.ai to /Volumes/iMandala Clone/Users/Farm/Mandala Farm
Stuff/CSA/CSA 2006/newsletters 2006/#2 2006front.ai of type 8
|03:03:14 PM|Error| : Input/output error

we're performing smart-update and it's been while. Would a normal complete update make a difference?

OK -- it looks like another problematic file. Take a look at the Troubleshooting section of the User's Guide (Help > User's Guide). It goes into detail about how to diagnose these types of problems, and should help you determine whether the error is on the source or destination, and how to take care of it...