[lkml]   [2009]   [Jul]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: mounting cifs filesystems not possible
See my original post to LKML at
You can see kernel version, and dmesg output (including cifsFYI set to
7) there.
I did file a bug report to gentoo bug list and lkml. Shall I also do
so for ? I think it's more kernel related.

The DebugData of the share I'm trying to mount (fortunaltely I got a
successful mount after several tries):

brklev2b ~ # cat /proc/fs/cifs/DebugData
Display Internal CIFS Data Structures for Debugging
CIFS Version 1.57
Active VFS Requests: 0
1) Name: Domain: EUROPE Uses: 1 OS: Windows Server 2003
R2 3790 Service Pack 1
NOS: Windows Server 2003 R2 5.2 Capability: 0x1f3fd
SMB session status: 1 TCP status: 1
Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0
1) \\BRKVN05\AtlasPM Mounts: 1 Type: NTFS DevInfo: 0x20
Attributes: 0x700ff
PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED



On Thu, Jul 23, 2009 at 8:10 AM, Steve French<> wrote:
> On Thu, Jul 23, 2009 at 12:26 AM, Gerhard
> Hintermayer<> wrote:
>> Well this is indeed strange. First I thought the problem was solved
>> because I had an old version of mount installed, but the successful
>> mount with latest version of mount.cifs was only by chance. I get 1
>> successful mount out of ~ 30 tries (each time unloading the cifs
>> module). And looking at the source in export.c I discovered, that
>> reexporting cifs- mount points is still not supported :-( : This seems
>> to be very tricky. If you need more information to track the tainting
>> problem down, pls give me a note.
> What is kernel version?
> What is symptom?
> Have you opened a bug against the project bugzilla (
> The dmesg (Linux message log) will show certain serious errors, but
> enabling additional cifs debugging flags can increase the debug
> output. Setting /proc/fs/cifs/DebugData to 1 will cause additional
> cifs informational messages to be logged, and setting
> it to 3 (“echo 3 > /proc/fs/cifs/cifsFYI”) will also log return codes
> from most cifs entry points to dmesg.
> One of the most powerful tools for analyzing networking or network
> filesystem problems is “Wireshark."
> shows instructions how
> to do wireshark captures.
> --
> Thanks,
> Steve
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-07-23 08:27    [W:0.047 / U:9.640 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site