From: Brian Tinsley <btlists@emageon.com>
To: nfs@lists.sourceforge.net
Subject: Unexpected error
Date: Fri, 15 Aug 2003 01:04:19 -0500 [thread overview]
Message-ID: <3F3C77E3.4070509@emageon.com> (raw)
Hi!
Can anyone elaborate on what may have caused the following errors:
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!
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-08-15 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 6:04 Brian Tinsley [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-01 9:15 Unexpected Error Toni Marí
2007-08-14 15:55 Unexpected error shacky
2007-08-14 16:25 ` shacky
2003-08-15 5:40 Brian Tinsley
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=3F3C77E3.4070509@emageon.com \
--to=btlists@emageon.com \
--cc=nfs@lists.sourceforge.net \
/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.