LKML Archive on
help / color / mirror / Atom feed
From: Steven French <>
To: Eric Lacombe <>
Cc: linux-kernel <>
Subject: Re: Linux Freeze with CIFS mount
Date: Tue, 30 Jan 2007 21:51:35 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

The cifs entries in the dmesg log do not indicate any errors, much less 
show the cause of this
particular problem.

The repeated entry:
        CIFS VFS: Send error in SETFSUnixInfo = -5
is expected on connection to certain older versions of Samba servers (or 
other servers that 
only partially support the current CIFS Unix Extensions).  It is harmless.

It would be useful to know (e.g. if it is possible to trace the network 
traffic on the server side on your NAS box) whether
any network traffic from the client is being sent when (or just before) 
the hang occurs.

It is possible that the restarting of the NAS box allows reconnection of 
the smb/cifs session to proceed
which presumably could be hanging or looping in the network adapter 
driver, the tcp stack or cifs on
the client, but it is hard to tell without more information.   I don't 
know much about either of the
GigE drivers loaded on your system to determine if there is an easy way to 
tell their state.

There are various ways to analyze system hangs including (at least in some 
cases) getting a system dump which
can be used to isolate the failing location - hopefully wrote on 01/30/2007 06:37:48 AM:

> Hello,
> I report a problem that occurs on a Core2 system (x86_64 used) with a 
>, when i use a NAS : Maxtor Shared Storage II 320Go (Linux 
> inside).
> In fact, this NAS can be web-configured to sleep after 30 min. Also,i 
mount a 
> partition of this device through this kind of entry inside the fstab :
> ------------
> //   /home/tuxico/NAS/Archive   cifs 
> noauto,users,iocharset=iso8859-1,noperm,nosetuids,noacl,sfu,
> file_mode=0600,dir_mode=0755,uid=tuxico,gid=users,
> credentials=/root/.credentials 
> 0 0
> ------------
> Under those circumstances, the Core2 system which is connected to it, 
> sometimes completely (mouse, keyboard are frozen, no connection possible 
> an external system - sshd not respond).
> This occurs regularly (within 3-4 days) and it seems that the problem 
> from the awakening of the NAS device.
> Indeed I have disable the sleep feature of the device (via its web 
> panel), then i was unable to trigger the problem for at least 7 days of 
> uptime of the Core2 system.
> I join the .config, the result of lspci, and the CIFS logs that have 
> written to /var/log/messages (i don't know if there are relevant or not 
> in the doubt...).
> Thanks in advance for the help.
> Best regards,
>    Eric
> [attachment "lspci" deleted by Steven French/Austin/IBM] [attachment
> "dotconfig" deleted by Steven French/Austin/IBM] [attachment 
> "cifslog" deleted by Steven French/Austin/IBM] 

Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench at-sign us dot ibm dot com

  reply	other threads:[~2007-01-31  3:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 12:37 Eric Lacombe
2007-01-31  3:51 ` Steven French [this message]
2007-01-31 14:51   ` Eric Lacombe
2007-02-13 13:52   ` Linux maybe a bug inside the r8169 network driver (was Re: Linux Freeze with CIFS mount) Eric Lacombe
2007-02-13 20:30     ` Francois Romieu
2007-02-14 10:49       ` Eric Lacombe
2007-03-05 21:19         ` Eric Lacombe
2007-03-05 22:16           ` Francois Romieu
2007-03-06 16:42             ` Eric Lacombe
2007-03-07 19:48               ` Eric Lacombe
2007-03-09  9:30                 ` Eric Lacombe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Linux Freeze with CIFS mount' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).