| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] Make inode64 a remountable option |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Fri, 17 Aug 2012 11:42:44 +1000 |
| In-reply-to: | <20120817012030.GB16013@xxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <1345142110-6412-1-git-send-email-cmaiolino@xxxxxxxxxx> <502D56B9.9080606@xxxxxxxxxx> <20120817012030.GB16013@xxxxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Thu, Aug 16, 2012 at 10:20:30PM -0300, Carlos Maiolino wrote: > > Reviewed-by: Brian Foster <bfoster@xxxxxxxxxx> > > > > 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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Make inode64 a remountable option, Carlos Maiolino |
|---|---|
| Next by Date: | [PATCH V2] Make inode64 a remountable option, Carlos Maiolino |
| Previous by Thread: | Re: [PATCH] Make inode64 a remountable option, Carlos Maiolino |
| Next by Thread: | Re: [PATCH] Make inode64 a remountable option, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |