From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "F. Baker" <baker@deslab.mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs errors with xfs filesystem (2.4.x kernel)
Date: Mon, 29 Mar 2004 19:57:24 -0500 [thread overview]
Message-ID: <1080608244.2410.295.camel@lade.trondhjem.org> (raw)
In-Reply-To: <200403292051.i2TKp9dd027008@deslab.mit.edu>
På må , 29/03/2004 klokka 15:51, skreiv F. Baker:
> PS: Interestingly:
>
> cp file1 file2
> where file1 is sufficiently large (1 MB or bigger) always fails the
> first time, but often does a partial write.
>
> If you then delete file2 and try the command anew, it works fine.
> Very strange indeed.
Have you read the FAQ entry on http://nfs.sourceforge.net/#faq_e4
Cheers,
Trond
prev parent reply other threads:[~2004-03-30 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 20:51 F. Baker
2004-03-30 0:57 ` Trond Myklebust [this message]
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=1080608244.2410.295.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=baker@deslab.mit.edu \
--cc=linux-kernel@vger.kernel.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®