public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Bernard Chan <bernard@goanimate.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: ENOSPC and filesystem shutdowns
Date: Fri, 9 Sep 2011 04:00:51 -0400	[thread overview]
Message-ID: <20110909080051.GB31050@infradead.org> (raw)
In-Reply-To: <CAKxAxjFUMrQpb5kQUdpRdt2wx83oKxaLZPTVTR_j43dkhcOyyw@mail.gmail.com>

On Thu, Sep 08, 2011 at 07:09:55PM +0800, Bernard Chan wrote:
> So should we bother with inode64 and 64-bit servers with NFS4, and should we
> anticipate any other issues running on this setup with a 4TB volume without
> enabling inode64?

I would absolutely recommend using inode64 if your are running a pure
64-bit environment.  Even if you are not running out of inodes it will
give you a much better allocation pattern.

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

      parent reply	other threads:[~2011-09-09  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04  6:09 ENOSPC and filesystem shutdowns Bernard Chan
2011-09-05  7:47 ` Christoph Hellwig
2011-09-08 11:09   ` Bernard Chan
2011-09-09  7:19     ` Michael Monnerie
2011-09-09  8:00     ` Christoph Hellwig [this message]

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=20110909080051.GB31050@infradead.org \
    --to=hch@infradead.org \
    --cc=bernard@goanimate.com \
    --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