From: Dave Chinner <david@fromorbit.com>
To: Ivan.Novick@emc.com
Cc: Timothy.Heath@emc.com, xfs@oss.sgi.com
Subject: Re: clarifications on inode64 mount option
Date: Mon, 22 Nov 2010 11:49:57 +1100 [thread overview]
Message-ID: <20101122004957.GF13830@dastard> (raw)
In-Reply-To: <C90EF576.118F%ivan.novick@emc.com>
On Sun, Nov 21, 2010 at 07:12:38PM -0500, Ivan.Novick@emc.com wrote:
> Hi all,
>
> My understanding from the documentation is that inode64 allows
> inode numbers to be 64 bits in size rather than the default of
> 32.
>
> Is this correct?
Yes.
> Will the option work fine on 32 bit X86 builds?
Yes, with a few caveats - all userspace applications, libraries, etc
need to use stat64() rather than stat() so that 64 bit inode numbers
can be correctly exported to userspace.
> The documentation also says:
> "This is provided for backwards compatibility, but causes problems
> for backup applications that cannot handle large inode numbers."
> Is this a current issue? Any examples of backup applications that
> have trouble reading a file system that uses this option?
See this discussion:
http://oss.sgi.com/archives/xfs/2010-04/msg00111.html
EMC Networker is one of the backup programs that has historically
not supported 64 bit inodes. Whether that is still true or not,
maybe you can find out for us. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-11-22 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 0:12 clarifications on inode64 mount option Ivan.Novick
2010-11-22 0:49 ` Dave Chinner [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=20101122004957.GF13830@dastard \
--to=david@fromorbit.com \
--cc=Ivan.Novick@emc.com \
--cc=Timothy.Heath@emc.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