From: Blake Golliher <blake-/eYsKH2uxv5Wk0Htik3J/w@public.gmane.org>
To: David Konerding <dakoner@gmail.com>, <nfs@lists.sourceforge.net>
Subject: Re: [NFS] I/O Errors with hard mounts
Date: Wed, 04 Jun 2008 08:20:03 -0700 [thread overview]
Message-ID: <C46C00B3.1723D%blake@facebook.com> (raw)
In-Reply-To: <4f0f0cb0806040633x74fd0afbm94866cf85810f242-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Can you take a trace on the client when the =8Ci/o error=B9 message sho=
ws up? I
suppose that=B9d be hard, but that=B9d tell us pretty quick where the m=
essage is
coming from. You could also take a trace from the filer if that's easi=
er
using pktt.
-Blake
On 6/4/08 6:33 AM, "David Konerding" <dakoner@gmail.com> wrote:
> Hi,
>=20
> We have a bunch of Linux clients (SLES 10 SP1) which mount a NetApp f=
iler.
>=20
> When the NetApp gets very, very busy, for example, one user is
> deleting 1Tbyte of data
> while another user is doing a 30 client throughput test, it will stop
> responding to some requests.
>=20
> Although we are using hard mounts, some users report that during the
> hammering period, some of their
> file operations produce "I/O Error" messages on their terminal.
>=20
> We checked, and the hosts are indeed using hard mounting. From our
> reading, I/O Errors
> should only ever make it back to the user if are using soft mounting.
>=20
> We're pretty sure the filer is not sending back an NFS_ERR response (=
and we're
> pretty sure that wouldn't get reported to the user as an I/O Error...=
)
>=20
> At this point, we suspect there must be a path in the NFS
> implementation that returns I/O Error to user
> space even with a hard mount.
>=20
> Any ideas?
>=20
> Dave
>=20
> ---------------------------------------------------------------------=
----
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
> _______________________________________________
> Please note that nfs@lists.sourceforge.net is being discontinued.
> Please subscribe to linux-nfs@vger.kernel.org instead.
> http://vger.kernel.org/vger-lists.html#linux-nfs
>=20
-----------------------------------------------------------------------=
--
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-06-04 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 13:33 [NFS] I/O Errors with hard mounts David Konerding
[not found] ` <4f0f0cb0806040633x74fd0afbm94866cf85810f242-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-04 15:20 ` Blake Golliher [this message]
2008-06-04 16:17 ` Jeff Layton
[not found] ` <20080604121723.5b6a53e6-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-06-04 17:00 ` David Konerding
[not found] ` <4f0f0cb0806041000m7926d1e7m93f71ebaacd6c976-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-04 17:58 ` Jeff Layton
[not found] ` <20080604135817.0608273a-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-06-04 21:07 ` David Konerding
2008-06-04 18:19 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2008-06-04 22:45 Ricardo Labiaga
[not found] ` <927260.87785.qm-KtJlQ5K7SlOvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-06-04 22:56 ` David Konerding
2008-06-05 0:40 Ricardo Labiaga
2008-06-06 1:00 Ricardo Labiaga
[not found] <505115.86554.qm@web31405.mail.mud.yahoo.com>
[not found] ` <4f0f0cb0806061638i35ae4f9bp423148d6acbb953b@mail.gmail.com>
[not found] ` <4f0f0cb0806061638i35ae4f9bp423148d6acbb953b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-09 17:02 ` David Konerding
[not found] ` <4f0f0cb0806091002w7f0110fh17e40568c7eb5bb8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-09 23:20 ` Trond Myklebust
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=C46C00B3.1723D%blake@facebook.com \
--to=blake-/eyskh2uxv5wk0htik3j/w@public.gmane.org \
--cc=dakoner@gmail.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.