From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andreas Amann <amann@physik.tu-berlin.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.6 breaks kmail (nfs related?)
Date: Sun, 16 May 2004 15:10:12 -0400 [thread overview]
Message-ID: <1084734612.6331.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0405161149430.25502@ppc970.osdl.org>
På su , 16/05/2004 klokka 14:50, skreiv Linus Torvalds:
> Agreed. But the kmail message is apparently "(No space left on device?)",
> which may be just kmail itself reacting to a truncated write rather than
> any actual ENOSPC error. A "strace" would help clarify exactly what goes
> wrong..
Right...
One possible suspect might be open(O_EXCL) since, AFAICS, Andreas is
using maildir-style mailboxes. Perhaps that SETATTR call in
nfs3_proc_create() is failing? We recently fixed so that it always sets
MTIME/ATIME...
Andreas: when you do the "strace" could you first run
echo "16" >/proc/sys/sunrpc/nfs_debug
and then record the output from "dmesg" immediately after the kmail
crash?
Cheers,
Trond
next prev parent reply other threads:[~2004-05-16 19:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 12:11 Andreas Amann
2004-05-16 4:46 ` Linus Torvalds
2004-05-16 17:59 ` Trond Myklebust
2004-05-16 18:10 ` Trond Myklebust
2004-05-16 18:19 ` Linus Torvalds
2004-05-16 18:47 ` Trond Myklebust
2004-05-16 18:50 ` Linus Torvalds
2004-05-16 19:10 ` Trond Myklebust [this message]
2004-05-17 11:31 ` Andreas Amann
2004-05-17 15:55 ` Trond Myklebust
2004-05-21 15:27 ` Andreas Amann
2004-05-21 16:40 ` Trond Myklebust
2004-05-21 23:05 ` Andreas Amann
2004-05-22 3:40 ` J. Bruce Fields
2004-05-17 21:35 ` Matthias Urlichs
2004-05-17 6:35 ` Norberto Bensa
2004-05-17 7:14 ` Andrew Morton
2004-05-17 17:35 ` Andrew Morton
2004-05-17 18:01 ` Trond Myklebust
2004-05-17 16:17 ` Frank van Maarseveen
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=1084734612.6331.8.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=amann@physik.tu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®