From: <Ivan.Novick@emc.com>
To: xfs@oss.sgi.com
Subject: inode64 mount option added after data exists
Date: Mon, 13 Dec 2010 17:24:46 -0500 [thread overview]
Message-ID: <C92BDD2E.1C75%ivan.novick@emc.com> (raw)
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.
Will it still work as intended in this case (use 64 bit inodes)?
Cheers,
Ivan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-12-13 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 22:24 Ivan.Novick [this message]
2010-12-14 4:43 ` inode64 mount option added after data exists Dave Chinner
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=C92BDD2E.1C75%ivan.novick@emc.com \
--to=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 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.