From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Robottom Reis <kiko@async.com.br>
Cc: <NFS@lists.sourceforge.net>, <reiserfs-list@namesys.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [NFS] NFS Insanity, v2
Date: 23 Jun 2001 00:58:15 +0200 [thread overview]
Message-ID: <shs66do3ywo.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.32.0106221643210.183-100000@blackjesus.async.com.br>
In-Reply-To: Christian Robottom Reis's message of "Fri, 22 Jun 2001 16:52:09 -0300 (BRT)"
>>>>> " " == Christian Robottom Reis <kiko@async.com.br> writes:
> Every day at the same time I pull mozilla-latest through http,
> and untar it into a directory that is served by nfs. The file
> isn't too big - around 9MB. It creates a set of files inside
> /mondo/local/mozilla. One of the files (same one for some
> reason), components/libgkcontent.so, always ends up corrupted
> on the client side. There is no server-side corruption.
> Remounting (and thus rebooting) the client mount gets things
> back to normal. Anyone willing to track this down with me? Or
> is it something known (and being worked on, hopefully)?
Is libgkcontents.so in use on the client? If so it's a known problem:
mmap() screws up the page cache invalidation routine
invalidate_inode_page(). If you do the untar on the client, then all
will be fine...
However the last time your report was of a problem in which the server
was corrupted, and the client was good. Was that a typo, or is it
still the case?
Cheers,
Trond
next prev parent reply other threads:[~2001-06-22 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 19:52 Christian Robottom Reis
2001-06-22 22:58 ` Trond Myklebust [this message]
2001-06-22 23:15 ` [NFS] " Christian Robottom Reis
2001-06-22 23:36 ` 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=shs66do3ywo.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=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 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®