lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130701165524.GB23896@thunk.org> Date: Mon, 1 Jul 2013 12:55:24 -0400 From: Theodore Ts'o <tytso@....edu> To: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@...il.com> Cc: linux-ext4@...r.kernel.org Subject: Re: Beginner questions about ext4 On Mon, Jul 01, 2013 at 05:23:13PM +0200, Felipe Monteiro de Carvalho wrote: > On Sun, Jun 23, 2013 at 1:59 PM, Theodore Ts'o <tytso@....edu> wrote: > > Historically, before flex_bg, the allocation bitmaps and inode tables > > for a particular block group had to be located within that block > > group, per the image that you've referenced above. > > Thanks, but I'm still not sure: Are all groups flexible groups when > FLEX_BG feature is activated? I'm not sure whant you mean by "flexible groups". There is no such concept. > If not, I wonder how a reader will recognize which groups were merged ... And block groups don't get merged. You should think of a flex block group as a collection of block groups. (Just as a number of provinces make up country, or a collection of towns make up a county, and a number of counties make up a province.) - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists