All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Shyam Kaushik <shyam@zadarastorage.com>,
	bfoster@redhat.com, Yair Hershko <yair@zadarastorage.com>,
	xfs@oss.sgi.com, Danny Shavit <danny@zadarastorage.com>,
	Alex Lyakas <alex@zadarastorage.com>
Subject: Re: xfs_iext_realloc_indirect and "XFS: possible memory allocation deadlock"
Date: Tue, 7 Jul 2015 02:05:11 -0700	[thread overview]
Message-ID: <20150707090511.GA21863@infradead.org> (raw)
In-Reply-To: <20150707000911.GT7943@dastard>

On Tue, Jul 07, 2015 at 10:09:11AM +1000, Dave Chinner wrote:
> server crash. i.e. the client side commit is an "fsync" to the
> server, and until the server responds with a success to the client
> commit RPC the client side will continue to retry sending the data
> to the server.
> 
> For the persepctive of metadata (i.e. directory entries) the use of
> the "dirsync" mount option is sufficient for HA failover servers to
> work correctly as it ensures that directory structure changes are always
> committed to disk before the RPC response is sent back to the
> client.
> 
> i.e. the "sync" mount option doesn't actually improve data integrity
> of an NFS server when you look at the end-to-end NFS protocol
> handling of async write data....


You don't need dirsync either.  NFS does the right sync usin the
commit_metadata export operation without using that big hammer.

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

  reply	other threads:[~2015-07-07  9:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:18 xfs_iext_realloc_indirect and "XFS: possible memory allocation deadlock" Alex Lyakas
2015-06-23 20:18 ` Dave Chinner
2015-06-27 21:01   ` Alex Lyakas
2015-06-28 18:19     ` Alex Lyakas
2015-06-29 11:43     ` Brian Foster
2015-06-29 17:59       ` Alex Lyakas
2015-06-29 19:02         ` Brian Foster
2015-06-29 22:26     ` Dave Chinner
2015-07-06 18:47       ` Alex Lyakas
2015-07-07  0:09         ` Dave Chinner
2015-07-07  9:05           ` Christoph Hellwig [this message]
2015-07-23 15:39             ` Alex Lyakas
2015-07-23 23:09               ` Dave Chinner
2016-04-05 18:10                 ` Alex Lyakas
2016-04-05 20:41                   ` Dave Chinner
2016-04-06 16:39                     ` Alex Lyakas
2016-04-06 20:57                       ` Dave Chinner

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=20150707090511.GA21863@infradead.org \
    --to=hch@infradead.org \
    --cc=alex@zadarastorage.com \
    --cc=bfoster@redhat.com \
    --cc=danny@zadarastorage.com \
    --cc=david@fromorbit.com \
    --cc=shyam@zadarastorage.com \
    --cc=xfs@oss.sgi.com \
    --cc=yair@zadarastorage.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.