From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] Make inode64 a remountable option
Date: Fri, 17 Aug 2012 11:42:44 +1000 [thread overview]
Message-ID: <20120817014244.GA2877@dastard> (raw)
In-Reply-To: <20120817012030.GB16013@orion.usersys.redhat.com>
On Thu, Aug 16, 2012 at 10:20:30PM -0300, Carlos Maiolino wrote:
> > Reviewed-by: Brian Foster <bfoster@redhat.com>
> >
> > I do have a question though... do we care about the remount from inode64
> > to non-inode64 case?
> >
> I thought about it, but, once we enable inode64 option, remounting it back to
> inode32 may create problems to access inodes greater than (1<<32) - 1, so, I
> don't think we should make inode32 a remountable option.
You can still read, modify and unlink inodes w/ numbers greater than
32 bits when inode32 is active - you just can't allocate new inodes
in those AGs. Hence going back the other way would still be safe to
do on remount, I think.
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:[~2012-08-17 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 18:35 [PATCH] Make inode64 a remountable option Carlos Maiolino
2012-08-16 20:23 ` Brian Foster
2012-08-17 1:20 ` Carlos Maiolino
2012-08-17 1:42 ` Dave Chinner [this message]
2012-08-16 22:40 ` Dave Chinner
2012-08-17 0:46 ` Carlos Maiolino
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=20120817014244.GA2877@dastard \
--to=david@fromorbit.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