From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Steven French <sfrench@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: More CIFS problems in 2.5.67
Date: 10 Apr 2003 15:26:12 +0200 [thread overview]
Message-ID: <1049981172.11152.7.camel@tux.rsn.bth.se> (raw)
Hi, I'm back with more problems :)
I think I got this when maintenance work on the network disconnected me
from the server (wasn't home at the time, only saw it in logs later and
I know it wasn't there before I left)
No other CIFS messages or generic kernel errors before this.
CIFS VFS: Send error in Close = -5
CIFS VFS: There are still active MIDs in queue and we are exiting but we can not delete mid_q_entries or TCP_Server_Info structure due to pending requests MEMORY LEAK!!
CIFS VFS: CIFS: caught signal
CIFS VFS: CIFS: caught signal
CIFS VFS: CIFS: caught signal
CIFS VFS: CIFS: caught signal
CIFS VFS: CIFS: caught signal
CIFS VFS: Error 0xfffffffb or (-5 decimal) on cifs_get_inode_info in lookup
CIFS VFS: Error 0xfffffffb or (-5 decimal) on cifs_get_inode_info in lookup
CIFS VFS: Error 0xfffffffb or (-5 decimal) on cifs_get_inode_info in lookup
Accessing or unmounting the fs just hangs but is interruptible.
--
/Martin
reply other threads:[~2003-04-10 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1049981172.11152.7.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.com \
/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 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).