How to forceably unmount stuck network share in Mac OS X?

Posted by Kyle Lowry on Super User See other posts from Super User or by Kyle Lowry
Published on 2011-02-23T23:18:30Z Indexed on 2011/02/23 23:27 UTC
Read the original article Hit count: 355

Filed under:
|
|
|
|

Not long ago my Xserve failed (power loss) while an iMac was working with files on a particular network share (called "Work Share"). This volume, "Work Share", is now stuck. It can't be seen in the GUI, you can only detect it using the Terminal. Even after power cycling over the course of several days, ls -a still shows that it's there, but I can't unmount it using any command - not even as root in single user mode.

Every time I attempt to unmount that volume, I get the message that the resource is busy (which it can't possibly be since nothing is using it), and error code 4915.

The issue is that when I mount the real "Work Share", it internally is renamed to "Work Share-1", which breaks all my links, and several files in the share. If I can't unmount the false "Work Share", then that computer would be unuseable without a reformat, I would imagine - and I don't want it to have to come to that.

I've tried everything I can think of - it looks like sudo can't save me now.

Any ideas on how to unmount this stuck volume?

© Super User or respective owner

Related posts about mac

Related posts about network-shares