From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: debugfs fill_bgs command?
Date: Wed, 11 Apr 2007 15:17:26 -0500 [thread overview]
Message-ID: <461D4256.6020509@redhat.com> (raw)
I was wondering if others think it would be useful to have a "fill_bgs"
command in debugfs; this would (minimally) mark the lower X bgs as full
for both inodes & blocks (possibly either/or), to allow testing the
higher block groups. I'm using a hacked up version of this to do a
little ext3 testing above 8T. Given that this would really only be a
testing option in nature, would it be accepted into e2fsprogs? I'd
probably need some sort of "unfill" command as well, to put the bg
counters back where they should be; probably by actually reading the
bitmaps. This way fsck would still find a consistent filesystem...
I had originally written a set_bg_field function too, to go with inode &
sb variants, though for marking the first few thousand bg's it was going
to get a bit tedious... :)
Thoughts?
Thanks,
-Eric
next reply other threads:[~2007-04-11 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 20:17 Eric Sandeen [this message]
2007-04-11 22:52 ` debugfs fill_bgs command? Andreas Dilger
2007-04-12 1:21 ` Eric Sandeen
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=461D4256.6020509@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).