search

mahinthjoe / macfuse

Automatically exported from code.google.com/p/macfuse
0 stars 0 forks source link

SMB mounts behave strange / bork #104

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
SMB mounts behave strangely since I use MacFUSE. They will either disappear and 
remain usable, 
or remain visible on the desktop but are no longer usable (don't react to 
clicks or saves), or get 
partially duplicated into / on the local filesystem.

The last point is quite interesting, and I have to elaborate on that: If you 
had a working SMB 
mount at /Volumes/TheSMBStuff/, it will stop working after a while, as 
described above. 
However, double-clicking onto my local volume will reveal a folder named after 
the SMB share, 
directly under my local volume's root (in this example, there will be 
/TheSMBStuff/). This 
directory has sometimes contained some of the stuff I've used from the SMB 
mount, but not 
always.

What steps will reproduce the problem?
1. Use MacFUSE 0.2.1 with sshfs 0.1.0 and mount some sshfs share
2. Mount a Windoze share via Apple-K -> smb://blah/share
3. Use both for a while

I have a Powerbook G4 with OSX 10.4.8.

Original issue reported on code.google.com by thor...@googlemail.com on 19 Feb 2007 at 1:50

GoogleCodeExporter commented 8 years ago 
Oh, and I forgot to mention: The SMB share cannot be re-mounted, only a reboot 
helps. These problems only 
occured after installing MacFUSE; nothing else has been installed or 
reconfigured in the meantime.

Original comment by thor...@googlemail.com on 19 Feb 2007 at 5:12

GoogleCodeExporter commented 8 years ago 
I can't think of anything MacFUSE would or could do to SMB. Is your SMB 
connection to the same host as the 
SSHFS connection? Is the same directory hierarchy on the remote host being 
accessed both through SMB and 
SSHFS?

Original comment by si...@gmail.com on 20 Feb 2007 at 4:02

GoogleCodeExporter commented 8 years ago 
Sorry for the delay, I wasn't notified of your reply even though I starred this 
issue. :(

No, the SMB connection is to a completely different machine which even is on 
another subnet (SMB goes to 
192.168.6.n while the sshfs connections are all on 192.168.4.n). The machines I 
connect to via sshfs don't offer 
SMB at all (those are web servers).

Original comment by thor...@googlemail.com on 12 Mar 2007 at 4:29

GoogleCodeExporter commented 8 years ago 
> I wasn't notified of your reply even though I starred this issue. :(

Anyone who reports that problem (which is/was *not* related to the 
MacFUSE Project area) can change the defaults that Google Code may have set for 
them: 
<http://code.google.com/hosting/settings>

To their credit: Google Code support resolved an underlying issue quickly, but 
there remains a possibility/
likelihood that a number of users were or still are in :( mode about not 
receiving notifications, so I have 
suggested to them 
<http://code.google.com/p/support/issues/detail?id=253>

Original comment by grahampe...@gmail.com on 16 May 2007 at 11:36

GoogleCodeExporter commented 8 years ago 
FYI, the problem hasn't resurfaced since I updated from 0.2.1 to the next 
version
(don't remember which it was). I tried to reproduce it again under 0.3.0 but it 
seems
to have been a heisenbug. So you can close this issue as far as I am concerned. 
;)

Original comment by thor...@googlemail.com on 30 May 2007 at 10:40

GoogleCodeExporter commented 8 years ago 
Heisenbug, apparently.

Original comment by si...@gmail.com on 4 Jun 2007 at 8:28