public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christian Herzog <horeizo@phys.ethz.ch>
Cc: xfs@oss.sgi.com
Subject: Re: XFS errors on large Infiniband fileserver setup
Date: Thu, 23 Sep 2010 06:38:02 -0400	[thread overview]
Message-ID: <20100923103802.GA16984@infradead.org> (raw)
In-Reply-To: <eb1b2cfa58cddc44c92c3a87a0e0a6c4@phys.ethz.ch>

On Thu, Sep 23, 2010 at 12:01:55PM +0200, Christian Herzog wrote:
> 
> Dear list,
> 
> my colleague has been running tests without ISER all morning, and so
> far we haven't encountered an error, even though we have copied > twice
> as much data as for the other tests. Is it possible that a problem in
> the transport layer remains undetected and only manifests itself in the
> filesystem?

Yes, that could very well possible.  While I'm not an expert on iSER it
looks like it doesn't use the software crc32c checksums in iscsi over
TCP but relies on the RDMA protocols guaranteeing it.

Btw, what target do you use?  According to
http://www.spinics.net/lists/linux-stgt/msg02038.html it seems like the
stgt iser target has some issues that look quite similar to yours.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-09-23 10:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23  7:22 XFS errors on large Infiniband fileserver setup Christian Herzog
2010-09-23 10:01 ` Christian Herzog
2010-09-23 10:38   ` Christoph Hellwig [this message]
2010-09-23 11:52     ` Christian Herzog
2010-09-23 13:54       ` Christoph Hellwig
2010-09-23 14:10         ` Christian Herzog
2010-09-23 23:53 ` Dave Chinner
2010-09-24  5:41   ` Christian Herzog
2010-09-24  8:56     ` Stan Hoeppner
2010-09-24 13:19     ` Emmanuel Florac
2010-09-24 13:19   ` Emmanuel Florac
2010-09-27  5:49 ` Christian Herzog

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=20100923103802.GA16984@infradead.org \
    --to=hch@infradead.org \
    --cc=horeizo@phys.ethz.ch \
    --cc=xfs@oss.sgi.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