From: Eric Sandeen <sandeen@redhat.com>
To: jon ernst <jonernst07@gmx.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: "block_dump, bd" in debugfs
Date: Wed, 26 Jun 2013 23:39:49 -0400 [thread overview]
Message-ID: <51CBB405.2080401@redhat.com> (raw)
In-Reply-To: <20130627030513.217820@gmx.com>
On 6/26/13 11:05 PM, jon ernst wrote:
> Hi,
> When I use "block_dump" to dump certain block. I got 12288 bytes dumped.
output example? It dumps a hexadecimal representation w/ octal
offsets, if you're counting bytes in the *text* output it'd be more than 4096.
> But I checked my block_size, it is 4k.
> At debugfs interactive prompt, it says "Dump contents of a block". So I am confused here.
> I read the code, it has for (i=0; i<current_fs->blocksize; i+=16) ,I don't understand why I can get 12k output.
Each line represents 16 bytes worth of data, with the starting offset of each line in octal.
When I run it on nonrepeating data, line starting points go from 0000 to 7760 (octal) on a 4k block (so it ends at 07777, or offset 4095)
> Also at the beginning of each line. The output pattern is "0000, 0020, 0040, 0060, 0100, 0120", where are numbers such as"0080,"?
Identical lines are suppressed, similar to what hexdump does by default. You might have had a "*" in between?
> Thanks in advance for any explanation.
I suppose manpage docs would help, but who has time to write those! ;)
-Eric
next prev parent reply other threads:[~2013-06-27 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 3:05 "block_dump, bd" in debugfs jon ernst
2013-06-27 3:39 ` Eric Sandeen [this message]
2013-06-27 6:00 ` Nick Dokos
2013-06-27 16:51 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 3:58 jon ernst
2013-06-27 4:00 ` 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=51CBB405.2080401@redhat.com \
--to=sandeen@redhat.com \
--cc=jonernst07@gmx.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 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.