All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 3.1rc7+ FSX failure over NFS
Date: Thu, 29 Sep 2011 15:05:19 -0400	[thread overview]
Message-ID: <20110929190519.GA15165@redhat.com> (raw)
In-Reply-To: <1317322772.8708.30.camel@lade.trondhjem.org>

On Thu, Sep 29, 2011 at 02:59:32PM -0400, Trond Myklebust wrote:
 
 > 1) What filesystem are you using on the server, and does that filesystem
 > support high resolution timestamps?

ext3

 > 2) Does the file length on the server match the reported erroneous file
 > length on the client?

No. Server side is 213853 bytes (0x3435d)

 > 3) Do the mtime and ctime on the erroneous file match on the client and
 > server?
 
both show..
Modify: 2011-09-29 13:50:00.000000000 -0400

	Dave


  reply	other threads:[~2011-09-29 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 18:41 3.1rc7+ FSX failure over NFS Dave Jones
2011-09-29 18:59 ` Trond Myklebust
2011-09-29 19:05   ` Dave Jones [this message]
2011-09-29 19:22     ` Trond Myklebust
2011-09-29 20:11       ` Dave Jones

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=20110929190519.GA15165@redhat.com \
    --to=davej@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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 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.