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
[email protected] 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
Linux
> 2.6.19.2, when i use a NAS : Maxtor Shared Storage II 320Go (Linux
2.6.12
> 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 :
>
> ------------
> //192.168.1.60/Archive /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,
freeze
> sometimes completely (mouse, keyboard are frozen, no connection possible
from
> an external system - sshd not respond).
>
> This occurs regularly (within 3-4 days) and it seems that the problem
results
> from the awakening of the NAS device.
>
> Indeed I have disable the sleep feature of the device (via its web
control
> 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
been
> written to /var/log/messages (i don't know if there are relevant or not
but
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
