From: Jakob Oestergaard <jakob@unthought.net>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS io errors on transfer from system running 2.4 to system running 2.5
Date: Tue, 3 Jun 2003 14:52:47 +0200 [thread overview]
Message-ID: <20030603125247.GD14947@unthought.net> (raw)
In-Reply-To: <200306032043.28141.mflt1@micrologica.com.hk>
On Tue, Jun 03, 2003 at 08:43:28PM +0800, Michael Frank wrote:
> On Tuesday 03 June 2003 20:24, Jakob Oestergaard wrote:
> > > When doing rsync or cp _from_ system running 2.4 _to_ system running 2.5
> > > get Input/output error errors with random files.
> >
> > Do you use soft mounts?
>
> Yes
Then this is why you get the error
>
> >
> > If so, try hard instead. soft will fail, sooner or later.
>
> I don't like hard mounts because these do not timeout.
You get what you ask for, then: timeouts
>
> Also, this does not explain why 2.5 > 2.4 (and 2.4 > 2.4) is OK - _never_ had any problem
Leave it running for a million years, and I'm sure a sporadic error will
show up in those two situations as well.
You just now found a case where sporadic errors show up more often.
soft-mount = fail upon (sporadic) error
hard-mount = retry (forever or until interrupted if used with 'intr') upon error
I always use hard,intr so that I can manually interrupt hanging jobs,
but also know that they do not randomly fail just because a few packets
get dropped on my network. This seems to be the common setup, as far as
I know.
Cheers,
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2003-06-03 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 11:12 Michael Frank
[not found] ` <20030603122411.GB14947@unthought.net>
2003-06-03 12:43 ` Michael Frank
2003-06-03 12:52 ` Jakob Oestergaard [this message]
2003-06-03 13:01 ` Michael Frank
2003-06-03 13:26 ` Jakob Oestergaard
2003-06-16 0:56 ` Michael Frank
2003-06-03 14:42 ` Andrew Ryan
2003-06-03 15:09 ` Michael Frank
2003-06-03 16:10 ` Trond Myklebust
2003-06-03 16:35 ` Michael Frank
2003-06-04 20:57 ` Andrew Ryan
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=20030603125247.GD14947@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
/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®