 |
 |
Rant: OS X and network volume suckiness
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
I've seen sooo many variants of this problem: volumes that won't eject, OS X alerts offering to eject the volume only to freeze the Finder completely, volumes going away, volumes remaining there between sleeps and unable to reconnect or unmount, unable to umount or umount -f, even complete freezes of the terminal session doing a tab completion of volumes in /Volumes that need to be reconnected. I'm sure I could think of more variants of this overall general annoyance if I sat down and thought about it, this has been going on for *years*.
It's incredible how this has been so incredibly elusive for so long. Have you guys found any useful tricks and voodoo to work around some of these problems?
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
My latest (and most aggravating) problem required a machine reboot, lots of broken pipe error messages logged.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status:
Offline
|
|
I'm not encountering a lot of your problems, maybe because I'm just not doing the stuff you do.
My networking is pretty simple (just at home), and with SL, it really got good. I had more issues beore SL, but most of these are gone.
-t
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
It seems to have gotten better for me too, although marginally.
I use MacFuse/SSHfs heavily, and I realize that the MacFuse implementation is not perfect and some of my problems are not Apple's fault. However, what is Apple's fault is the Finder not recovering gracefully from sleep wakes and noticing the unresponsive network volume. The error checking seems pretty weak. To the Finder a Fuse volume (and anything other network volume mounted in /Volumes) is recognized as a network volume and given the appropriate icon. I can forgive some reconnection difficulties or something as a problem with MacFuse, but causing the whole Finder and even OS at times to implode is not cool.
It's also weird that sometimes it detects a request reached its timeout limit and offers to eject the volume (and usually blows up when it tries to do so), but sometimes it doesn't offer this at all. I can't figure out why at times there seems to be something monitoring activity and enforcing timeouts while other times there is seemingly nothing at all.
I don't understand why they couldn't just fix this timeout enforcer, make you reconnect, make the unmounting work. I would be *much* happier than this less-than-perfect workaround as opposed to the Finder just completely wigging out.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
I'm entertaining going back to using Netatalk instead of MacFUSE, although I'd hate to do so as AFP is so incredibly slow having to write all of that dual fork crap that is completely irrelevant to what I do.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
It's been a long time, but I recall there being a Netatalk option to not write the .Appledouble directories... Maybe I should look into that.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
