All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Beginner questions about ext4
Date: Mon, 1 Jul 2013 17:23:13 +0200	[thread overview]
Message-ID: <CACyNnZNQ00D=hKHZ_wvfwJx3CWt7iELrbgUf_41AzzSAJmxGUw@mail.gmail.com> (raw)
In-Reply-To: <20130623115953.GA16193@thunk.org>

On Sun, Jun 23, 2013 at 1:59 PM, Theodore Ts'o <tytso@mit.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?

If not, I wonder how a reader will recognize which groups were merged ...

thanks,
-- 
Felipe Monteiro de Carvalho

  reply	other threads:[~2013-07-01 15:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 12:20 Beginner questions about ext4 Felipe Monteiro de Carvalho
2013-06-23  6:29 ` Felipe Monteiro de Carvalho
2013-06-23 11:59   ` Theodore Ts'o
2013-07-01 15:23     ` Felipe Monteiro de Carvalho [this message]
2013-07-01 16:55       ` Theodore Ts'o
2013-07-10 16:13         ` Felipe Monteiro de Carvalho
2013-07-10 17:24           ` Theodore Ts'o
2013-07-11  7:37             ` Felipe Monteiro de Carvalho
2013-07-11 15:23               ` Theodore Ts'o
2013-07-15 10:20     ` Felipe Monteiro de Carvalho
2013-07-15 13:43       ` Theodore Ts'o
2013-07-15 16:09         ` Felipe Monteiro de Carvalho
2013-07-15 16:37           ` Theodore Ts'o
2013-07-15 17:55             ` Felipe Monteiro de Carvalho
2013-07-15 18:10               ` Theodore Ts'o
2013-07-15 18:18                 ` Felipe Monteiro de Carvalho
2013-07-15 18:59                   ` Theodore Ts'o
2013-07-16  6:14                     ` Felipe Monteiro de Carvalho

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='CACyNnZNQ00D=hKHZ_wvfwJx3CWt7iELrbgUf_41AzzSAJmxGUw@mail.gmail.com' \
    --to=felipemonteiro.carvalho@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.