From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Mason <mason@suse.com>
Cc: Christian Robottom Reis <kiko@async.com.br>,
NFS@lists.sourceforge.net, linux-kernel@vger.kernel.org,
reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] NFS insanity
Date: 21 Jun 2001 16:58:52 +0200 [thread overview]
Message-ID: <shselsdyj4j.fsf@charged.uio.no> (raw)
In-Reply-To: <424880000.993131958@tiny>
In-Reply-To: Chris Mason's message of "Thu, 21 Jun 2001 09:59:18 -0400"
>>>>> " " == Chris Mason <mason@suse.com> writes:
> Sounds like some of the problems fixed in 2.4.5 and 2.4.6pre
> kernels, where NFS data didn't get flushed right away, but I
> thought that only involved mmap'd files.
Ordinary 'cp' should work fine: it uses 'read' and 'write' - not mmap.
Cheers,
Trond
next prev parent reply other threads:[~2001-06-21 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 23:23 NFS insanity Christian Robottom Reis
2001-06-21 13:59 ` [reiserfs-list] " Chris Mason
2001-06-21 14:58 ` Trond Myklebust [this message]
2001-06-21 15:10 ` [NFS] " Trond Myklebust
2001-06-21 22:43 ` Christian Robottom Reis
2001-06-22 12:58 ` Trond Myklebust
2001-06-22 15:57 ` Christian Robottom Reis
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=shselsdyj4j.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=NFS@lists.sourceforge.net \
--cc=kiko@async.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--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.