From: Alain Fauconnet <alain@ait.ac.th>
To: linux-kernel@vger.kernel.org
Subject: smbfs broken in 2.4.25? (Too many open files in system)
Date: Thu, 26 Feb 2004 18:09:03 +0700 [thread overview]
Message-ID: <20040226110903.GC621@ait.ac.th> (raw)
Hello,
Hope I won't get flamed for this, I've spent a fair amount of time
searching archives and news without finding anything close enough.
Since I've updated my Slackware 8.0 desktop to the 2.4.25 kernel (from
source, loaded .config from .24) I can't access shares off Win9x
systems reliably (98/98SE tested). smbfs is loaded as a module.
I get random 'Too many open files in system'. E.g.:
# /usr/local/samba/bin/smbmount //w98box/c /dosc -o password=xxxxx
# ls /dosc
/bin/ls: /dosc: Too many open files in system
(command repeated several times: hit up arrow and enter... and then:)
# ls /dosc
ASD.LOG* BIN/ CONFIG.TXT* MSDOS.SYS* SUHDLOG.---*
AUTOEXEC.001* BOOTLOG.DMA* CONFIG.W95* MSDOS.W95* SUHDLOG.BAK*
(...works!)
It seems to randomly succeed or fail, with a majority of failures.
I've been able to catch messages like the following in syslog:
Feb 26 13:42:27 alain kernel: smb_lookup: find windows/MSDFMAP.INI failed, error=-23
This used to work flawlessly in 2.4.24.
The Gods of Linux forgive me, I've copied ./fs/smbfs/* and
./include/linux/smb*.h from the 2.4.24 tree, "make modules" and
reloaded smbfs.o: now it works all the time!
Some background: Samba is v2.2.8a built from source.
Any hints? I've tried rebuilding smbfs with debug options in the
Makefile, SMBFS_PARANOIA on and off, I haven't been able to
make much sense out of it. It keeps failing in every configuration.
Greets,
_Alain_
next reply other threads:[~2004-02-26 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 11:09 Alain Fauconnet [this message]
2004-02-26 19:24 ` smbfs broken in 2.4.25? (Too many open files in system) Urban Widmark
2004-02-27 2:23 ` Alain Fauconnet
2004-02-27 9:45 ` Urban Widmark
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040226110903.GC621@ait.ac.th \
--to=alain@ait.ac.th \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.