From: Andreas Dilger <adilger@clusterfs.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2 anomaly when making filesystem?
Date: Tue, 3 Sep 2002 11:04:16 -0600 [thread overview]
Message-ID: <20020903170416.GO32468@clusterfs.com> (raw)
In-Reply-To: <3D747134.9290.1A2BFC@localhost>
On Sep 03, 2002 08:22 +0200, Ulrich Windl wrote:
> Being curious, I dumped the metadata after creation and found some odd
> thing: For several allocation groups there was a gap in the free
> blocks. First I thought it is intentional; maybe to put administrative
> data in the moddle of the allocation group, but then I found that other
> groups had no such gap. I'll attach the dump at the end.
>
> If it's intentional, maybe add some documentation about the layout to
> the manual pages; if it's a bug, it would be nice to see it fixed.
It _is_ intentional. The groups which have a gap do not have a backup
superblock or group descriptor table.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
prev parent reply other threads:[~2002-09-03 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 6:22 ext2 anomaly when making filesystem? Ulrich Windl
2002-09-03 17:04 ` Andreas Dilger [this message]
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=20020903170416.GO32468@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox