I think it's related to the Samba version in use on Time Capsule:
# cat /proc/fs/cifs/DebugData
Display Internal CIFS Data Structures for Debugging
---
CIFS Version 1.54
Active VFS Requests: 0
Servers:
1) Name: 192.168.0.2 Domain: SM-HOME Uses: 1
After adding nodfs to my kernel at boot time did NOT change anything.
My MS Windows shares that use to mount automatically under 8.04 still do
not mount automatically after adding that option. Yet, after boot, I can
issue sudo mount /shares/windows_f and the share is mounted without
incident
Thank you for the clarification, Thierry. I changed my fstab entry like
this:
//192.168.4.10/NetworkShare /shares/windows_f cifs
nodfs,auto,rw,credentials=/root/.creds,uid=ttwaro,gid=ttwaro 0 0
and rebooted. Still does NOT work. However, when manually running sudo
mount /shares/windows_f I now
On Tue, Dec 23, 2008 at 5:54 AM, Tom ttw...@gmail.com wrote:
After adding nodfs to my kernel at boot time did NOT change anything.
My MS Windows shares that use to mount automatically under 8.04 still do
not mount automatically after adding that option. Yet, after boot, I can
issue sudo mount
I have just upgraded to kernel 2.6.27-11-generic and running nodfs
as a mount option as previously posted. I no longer get the error
message but the mount still does not happen automatically during/after
boot. I still need to mount the share manually. This worked every time
in 8.04 and 7.10.
I tried this but it didn't work. Isn't this for nfs fstype only? I have
CIFS. I could be misunderstanding something, though.
Vide wrote:
Tom, but your mount at bootime issue it's a completely different topic
(do you put the _netdev label in the fstab options? it's mandatory for
network
One more thing, this is on my laptop connecting wirelessly to the
shares. This worked perfectly EVERY time under 8.04 but never has worked
under 8.10. I'm sure it is a timing issue (waiting for the wireless
connection) but it had to do this under 8.04 too.
To reiterate:
* Window XP share
*
Thanks for the clarification, Thierry. I am, alas, in the last position, so
am very interested in knowing when the new kernel will be published. I
can't find any target dates on this bug report and it's the lack of any
visibility on when the fix might be released that's so frustrating. How
does
Just to summarize again:
1) A few versions of Samba server had a bug parsing DFS paths (fixed
in Samba server 3.0.26). You can see which version of server you have
mounted to by doing cat /proc/fs/cifs/Debug
Data on the client). When the Linux CIFS client added support for
DFS last year, those
