On Mon, 15 Apr 2013 19:20:51 +0200, David Sterba wrote: > On Fri, Apr 12, 2013 at 12:01:19PM -0500, Eric Sandeen wrote: >> On 4/11/13 5:35 AM, Miao Xie wrote: >>> Now, we set incompat flag EXTEND_IREF when we actually need insert a >>> extend inode reference, not when making a fs. But some users may hope >>> that the fs still can be mounted on the old kernel, and don't hope we >>> insert any extend inode references. So we introduce noextiref mount >>> option to close this function. >> >> I'd really rather not have yet another work-around mount option. >> >> Wouldn't it be better to say: if you don't want extended irefs, turn >> that feature off on the filesystem itself, either at mkfs time or via >> btrfstune after the fact. > > I agree with this, and hope the inconsistency around extref is only > temporary so the mount options is not required in the long term. > > The code reverting extref set by default in mkfs is in integration > branch. > > The preferred solution is the -O option where we can put all the fs > features in one go at mkfs time.
All right, let's add a option for mkfs, and throw away this patchset. Thanks. Miao -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
