Prev: -1080 Error and Interrupted TM Backup
Next: -10810 Error and Interrupted TM Backup (was "-1080 Error andInterrupted TM Backup")
From: Nick Naym on 9 Apr 2010 10:35
Typo: Subject should read "-10810 Error" not "-1080 Error." The body of the
post is correct.

--
iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)

From: Kevin McMurtrie on 10 Apr 2010 01:19
In article <C7E4B382.585F2%nicknaym@_remove_this_gmail.com.invalid>,
Nick Naym <nicknaym@_remove_this_gmail.com.invalid> wrote:

> Typo: Subject should read "-10810 Error" not "-1080 Error." The body of the
> post is correct.

This is a bug that has been with OS X since day one. Unix processes
have an "uninterruptible I/O" mode. Only two things can get a process
out of that mode - the I/O finishing or a forced reboot. When a volume
goes offline, a monitor is supposed detect it and cause all of its I/O
operations to return with an error. That monitor often becomes stuck in
uninterruptible I/O itself. Any process that attempts to look at the
volume that went offline also becomes stuck. Rebooting is the only
escape.

Error -10810 is what happens with you Force-Quit Finder but it's in
uninterruptible I/O. Force-Quit removes Finder from the Dock and the
GUI but it's powerless to actually shut it down. Only one Finder may be
running at once so you keep getting an error trying to launch it.

The original problem that gets you snagged on this OS bug will have to
be tracked down. For USB and Firewire disks, make sure the volume is
formatted correctly, the cables are good, and the firmware isn't
obsolete. For network disks, make sure they really are Time Machine
compatible and watch out for unreliable network hardware.
--
I won't see Google Groups replies because I must filter them as spam
 | 
Pages: 1
Prev: -1080 Error and Interrupted TM Backup
Next: -10810 Error and Interrupted TM Backup (was "-1080 Error andInterrupted TM Backup")