Package: autofs
Version: 4.1.3+4.1.4beta2-3
Severity: critical
Justification: breaks unrelated software
Using Kernel 2.6.10-6 or 2.6.11-1 I see spurious locks of processes
(inside Kernel, e.g the pocesses cannot be killed) when they attempt
to acces an automounted cifs volume. This does not happen on the
initial mount but only after the initial mount has expired.
The problem occurs on the server itself (mounting a cifs share
locally on the same machine) and remote (mounting a cifs share
exported by the Debian Server on another machine).
It might be interesting that the (remote) problem shows up too when
the client runs a SuSE 2.6.5 kernel - so it might be some interference
between automount and cifs.
The server needs a reboot after such an incident.
Unfortunately the problem is complex and two other components could
cause the problem (here: cifs and subfs, see below). Therefor I describe
the scenario in more detail:
(1) On the server side some of the cifs exports live on volumes that are
mounted via subfs. I do not believe that subfs causes the problem
because that sort of automount still works.
(2) On the client side the automounter is used.
If I try locally (on the server beeing in the "lock" state) to connect
to the cifs share via smbclient the programm pauses for a while and
then says:
Error in dskattr: Call timed out: server did not respond after 20000
milliseconds
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-amd
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages autofs depends on:
ii debconf 1.4.30.11 Debian configuration management sy
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- debconf information excluded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
