From: Bernd Schubert <bernd-schubert@web.de>
To: Brian Tinsley <btinsley@emageon.com>, reiserfs-list@namesys.com
Cc: nfs@lists.sourceforge.net
Subject: Re: Strange NFS/reiserfs errors
Date: Fri, 15 Aug 2003 13:23:16 +0200 [thread overview]
Message-ID: <200308151323.16172.bernd-schubert@web.de> (raw)
In-Reply-To: <3F3C7341.4020503@emageon.com>
Hi,
searching the archives of the reiserfs-ML and I guess also a general web
search would show that this is fixed in 2.4.21!
Regards,
Bernd
On Friday 15 August 2003 07:44, Brian Tinsley wrote:
> Hi! I've posted this to the NFS mailing list, but wanted to drop it here
> as well to see if anyone may provide further insight.
>
> ---------------------------
> Can anyone elaborate on what may have caused the following error:
>
> Aug 14 22:09:09 clarc02 kernel: nfsd-fh: found a name that I didn't
> expect: files/19
> Aug 14 22:09:40 clarc02 last message repeated 2314 times
> Aug 14 22:15:56 clarc02 last message repeated 1088 times
> Aug 14 22:17:10 clarc02 last message repeated 138 times
> Aug 14 22:19:03 clarc02 last message repeated 138 times
> Aug 14 22:20:53 clarc02 last message repeated 2 times
> Aug 14 22:21:30 clarc02 last message repeated 73 times
>
> The underlying filesystem is reiserfs and there was a high volume of
> writing taking place (or trying to) during this time. None of the writes
> succeeded as the client was returned EEXIST errors. However, the writes
> were reissued in full shortly after the last occurence and everything
> automagically started working properly again.
>
> I'm trying to decipher the source code, but it's a bit out of my area of
> expertise ;-)
>
> Thanks!
next prev parent reply other threads:[~2003-08-15 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 5:44 Strange NFS/reiserfs errors Brian Tinsley
2003-08-15 11:23 ` Bernd Schubert [this message]
2003-08-15 12:13 ` Oleg Drokin
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=200308151323.16172.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=btinsley@emageon.com \
--cc=nfs@lists.sourceforge.net \
--cc=reiserfs-list@namesys.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 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.