[linux-cifs-client] files disappearing randomly - kernel 2.6.27 cifs.ko 1.54 - VFS: No response for cmd 50

[Jodok Ole Muellers]

Hi,

I put a tcpdump of the problem here ftp://vam-emp.aschendorff.de/pub/prod-fs.cap
This was running on the client:
tcpdump -i bond0 -p -s 1500 -C1 -w prod-fs.cap port 445 or port 139 and host 10.2.1.155

10.2.1.45  is client
10.2.1.155 is server

This is what i've done while capturing 

vam-uti3:/root # umount /data/dpa2msu/red-fs2
vam-uti3:/root # mount /data/dpa2msu/red-fs2

vam-uti3:/root # cd /data/dpa2msu/red-fs2/bild/agentur/DPA


vam-uti3:/data/dpa2msu/red-fs2/bild/agentur/DPA # ls -1 | wc -l
748
vam-uti3:/data/dpa2msu/red-fs2/bild/agentur/DPA # ls -1 | wc -l
1348

vam-uti3:/data/dpa2msu/red-fs2/bild/agentur/DPA # ls -1 | wc -l
148

vam-uti3:/data/dpa2msu/red-fs2/bild/agentur/DPA # ls -1 | wc -l
298

vam-uti3:/data/dpa2msu/red-fs2/bild/agentur/DPA # ls -1 | wc -l
298
vam-uti3:/data/dpa2msu/red-fs2/bild/agentur/DPA # ls -1 | wc -l
148


Looks odd. 
148 seems to be a magic number somehow and shows up very often.


TIA
Jodok

> Sounds like the server is timing out and you're not getting the latter
> FIND_NEXT responses. You may want to sniff traffic on the wire and see
> if you can determine which (if any) requests aren't getting responses.
> Either way, it's probably a bug if the kernel isn't returning an error
> in this situation.
> 
> You may want to open one at samba.org (particularly if you can come up
> with a way to reproduce this).