From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Adam Olsen <arolsen@gmail.com>
Cc: Jeff Layton <jlayton@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: NFS+GD issues on kernel 2.6.24, but not 2.6.22
Date: Thu, 15 May 2008 13:04:43 -0700 [thread overview]
Message-ID: <1210881883.7796.3.camel@localhost> (raw)
In-Reply-To: <2473b43f0805151300q19d23bddy612e1978864669de-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, 2008-05-15 at 14:00 -0600, Adam Olsen wrote:
> On Thu, May 15, 2008 at 12:37 PM, Trond Myklebust
> <trond.myklebust@fys.uio.no> wrote:
> > Looks as if you've got a 32-bit application that doesn't like 64-bit
> > inode numbers. Try booting with the kernel parameter
> > 'nfs.enable_ino64=0'.
>
> Sorry if this is a dumb question, but is that going to hurt me in the
> long run? This filesystem has the capability of being rather huge
> (it's currently at 27TB).
Some applications (e.g. backup apps) may gripe at the fact that the
inode numbers are no longer guaranteed to be unique, but the only
alternative solution to that would be to convert your apps to be 64-bit
safe.
Trond
next prev parent reply other threads:[~2008-05-15 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:06 NFS+GD issues on kernel 2.6.24, but not 2.6.22 Adam Olsen
[not found] ` <2473b43f0805150706g5be9918cu3c77d9135cded912-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-15 15:46 ` Jeff Layton
[not found] ` <20080515084610.4e5161bc-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2008-05-15 15:55 ` Adam Olsen
[not found] ` <2473b43f0805150855o59a14e34h82b20f847c53f392-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-15 16:08 ` James Pearson
[not found] ` <482C600F.3040909-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
2008-05-15 16:20 ` Adam Olsen
2008-05-15 18:37 ` Trond Myklebust
2008-05-15 20:00 ` Adam Olsen
[not found] ` <2473b43f0805151300q19d23bddy612e1978864669de-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-15 20:04 ` Trond Myklebust [this message]
2008-05-15 20:06 ` Adam Olsen
2008-05-15 20:15 ` Adam Olsen
[not found] ` <2473b43f0805151315m3547bc17o57ca14c46a636671-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-15 20:49 ` Jeff Layton
[not found] ` <20080515164913.7e161c30-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2008-05-15 20:56 ` Jeff Layton
[not found] ` <20080515165639.40e92911-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2008-05-15 21:19 ` Adam Olsen
2008-05-15 21:29 ` James Pearson
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=1210881883.7796.3.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=arolsen@gmail.com \
--cc=jlayton@redhat.com \
--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.