Yes! Adding this mount option enables me to see files and directories
after a mount, I was also able to read and write successfully to the
mounted filesystem. I'm not clear why having the client generate inode
numbers corrects the problem or is necessary, but it's at least a
workaround. Thanks for
. The
Music directory was a directory that I knew to be there. My /etc/fstab
entry for this device is:
//192.168.6.33/public /mnt/NAS cifs
user=WVH/wvh%password,uid=1000,noauto0 0
The second tcpdump output file (broken-cifs-9.04-wvh.pcap) was produced
by using the same tcpdump
Hmmm - I wasn't able to attach multiple files for some reason., I've
attached the 9.04 output to this comment. See previous comment for
details.
** Attachment added: tcpdump output from 9.04 UNR system
http://launchpadlibrarian.net/33648144/broken-cifs-9.04-wvh.pcap
--
2.6.31 - Can't see
$ ls
public on 192.168.6.33
$ ls public\ on\ 192.168.6.33
Music Software Video
# grep NAS /etc/fstab
//192.168.6.33/public /mnt/NAS cifs
user=WVH/wvh%password,uid=1000,noauto0 0
# smbclient //192.168.6.33/public -W WVH -U wvh
Enter wvh's password:
Domain=[R] OS=[R] Server
As shown in comment #10, I am running 2.6.31-11.38. This is the kernel
version from which I submitted the output previously requested by Chuck,
and attached to comment #9.
--
2.6.31 - Can't see files in CIFS-mounted directories
https://bugs.launchpad.net/bugs/406466
You received this bug
I've attached script output containing the information that you
requested. I can see the share fine if I mount it using Places
Connect to Server... and can even cd around and list things through
~/.gvfs:
$ ls ~/.gvfs/public\ on\ 192.168.6.33/
Music/Software/ Video/
$ ls ~/.gvfs/public\ on\
BTW, I'm running the following kernel:
Linux u910 2.6.31-11-generic #38-Ubuntu SMP Fri Oct 2 11:06:40 UTC 2009
x86_64 GNU/Linux
I'm running up-to-date karmic code, last updated this morning. I can
also mount and explore this share using smbclient, with no problems.
It's only via a vanilla CIFS
