Re: Missing JBD2_FEATURE_INCOMPAT_64BIT in ext4

2007-04-19 Thread Mingming Cao
On Sun, 2007-04-15 at 10:16 -0600, Andreas Dilger wrote: Just a quick note before I forget. I thought there was a call in ext4 to set JBD2_FEATURE_INCOMPAT_64BIT at mount time if the filesystem has more than 2^32 blocks? Question about the online resize case. If the fs is increased to more

Re: Missing JBD2_FEATURE_INCOMPAT_64BIT in ext4

2007-04-19 Thread Andreas Dilger
On Apr 19, 2007 12:15 -0700, Mingming Cao wrote: On Sun, 2007-04-15 at 10:16 -0600, Andreas Dilger wrote: Just a quick note before I forget. I thought there was a call in ext4 to set JBD2_FEATURE_INCOMPAT_64BIT at mount time if the filesystem has more than 2^32 blocks? Question about

Re: Missing JBD2_FEATURE_INCOMPAT_64BIT in ext4

2007-04-19 Thread Andreas Dilger
On Apr 19, 2007 17:41 -0700, Mingming Cao wrote: Any concerns about turn on META_BG by default for all new ext4 fs? Initially I thought we only need META_BG for support 256TB, so there is no rush to turn it on for all the new fs. But it appears there are multiple benefits to enable META_BG by

Missing JBD2_FEATURE_INCOMPAT_64BIT in ext4

2007-04-15 Thread Andreas Dilger
Just a quick note before I forget. I thought there was a call in ext4 to set JBD2_FEATURE_INCOMPAT_64BIT at mount time if the filesystem has more than 2^32 blocks? I don't see that anywhere in the 2.6.20 ext4. Is that in the upstream git repo? Cheers, Andreas -- Andreas Dilger Principal