From: Dave Chinner <david@fromorbit.com>
To: Ivan.Novick@emc.com
Cc: xfs@oss.sgi.com
Subject: Re: inode64 mount option added after data exists
Date: Tue, 14 Dec 2010 15:43:55 +1100 [thread overview]
Message-ID: <20101214044355.GB16267@dastard> (raw)
In-Reply-To: <C92BDD2E.1C75%ivan.novick@emc.com>
On Mon, Dec 13, 2010 at 05:24:46PM -0500, Ivan.Novick@emc.com wrote:
> Hi all,
>
> Quick question about the inode64 mount option.
>
> Is it safe to add this mount option to a file system that was
> already created and wrote lots of data without it.
Yes.
> Will it still work as intended in this case (use 64 bit inodes)?
Yes, for newly created inodes and data.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-14 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 22:24 inode64 mount option added after data exists Ivan.Novick
2010-12-14 4:43 ` Dave Chinner [this message]
2010-12-14 7:19 ` Michael Monnerie
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=20101214044355.GB16267@dastard \
--to=david@fromorbit.com \
--cc=Ivan.Novick@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