Re: Duplicate/False Mount Points

In article <C69CF6E5.42B9D%nicknaym@[remove_this].gmail.com>,
Nick Naym <nicknaym@[remove_this].gmail.com> wrote:

Does anyone have experience with this? I do believe it has recently added to
the performance problems I¹ve been experiencing, especially with Time
Machine (see my recent post, ³Re: Finder Problem? (Update)²). But not fully
understanding ³mount points,² I¹m not quite sure how to deal with it safely
-- or whether it needs to be dealt with at all.

The problem appears to be that my external Time Machine volume¹s mount point
recently had a ³1² appended to its name, showing up that way both in Disk
Utility as well as in my system log, along with ominous error messages as
Time Machine has spent days _unsuccessfully_ attempting to complete any
backups. For some reason, Time Machine just suddenly finally succeeded in
creating a backup, but the log still is chock full of error messages.

I¹m not sure if it¹s something that will take care of itself over time, or
if I need to take proactive action to delete one of the supposedly two
folders that refer to the Time Machine drive. If the latter, I understand
that it must be done with great care to be sure the ³correct² one is
selected, lest I lose the contents of my TM drive.

I have looked for the supposed folders, but have only succeeded in finding
one (it has the name of the TM drive) in /Volumes; next to it is an alias
with the same name, except that it has the appended ³1.² The folder can¹t be
opened (no access privileges); the alias opens the actual TM hard drive.

TIA for any explanations/suggestions/guidance.

For 10.5, the trick seems to be waking from sleep and having the volume
become unavailable. Software keeps writing to the old file path as if
there was still a volume there. When it remounts as a new volume, it
gets '.1' in the name to avoid a conflicting title. I've seen it with
Firewire and AFP volumes so far.

Cleanup without a reboot can be done as root in Terminal.app with:

umount -f /Volumes/volumename
rm -Rf /Volumes/volumename

Make very sure that 'umount' works before issuing the second command to
erase everything.

In rare cases, anything that touches the old volume will hang forever in
the dreaded 'uninterruptible I/O' state. "Uninterruptible" is not an
understatement. Apps will start showing the beachball and nothing
except cutting the power can kill them. Not Force-Quit, not 'kill -9',
and the computer will refuse to shut down gracefully.

--
I will not see your reply if you use Google.
.

Relevant Pages

  • Re: Check permissions on Folder
    ... "FileSystemAccessRules" and accumulate what's allowed and denied. ... My understanding is that explicit rules take precedence over inherited rules ... you try to create, delete, modify files and folders. ... SecurityIdentifier secId = acc.Translate) ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: irresponsible dumbledore (hbp spoilers)
    ... > Troels Forchhammer wrote: ... >> Dumbledore not stopping Draco's attempts to kill him: ... >> understanding of the primary reality, ...
    (alt.fan.harry-potter)
  • Re: Front End Plastic Parts
    ... My understanding was (at least in the state I was in when I ... heard this) that the opposite is true -- you kill a deer with your car (at ...
    (rec.autos.makers.saturn)
  • Re: New Mexico trip a bust
    ... This statement of understanding that they can kill somebody if they ... drive drunk is then used as evidence in their trial and influences the ... and that they didn't intend to harm anybody. ...
    (rec.motorcycles)
  • Re: Re: Re: Re: Front End Plastic Parts
    ... My understanding was (at least in the state I was in when I ... heard this) that the opposite is true -- you kill a deer with your car (at ...
    (rec.autos.makers.saturn)
Loading