From: Eric Sandeen <sandeen@redhat.com>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: Mike Snitzer <snitzer@gmail.com>,
Rohit Sharma <imreckless@gmail.com>,
Kernelnewbies <kernelnewbies@nl.linux.org>,
ext4 <linux-ext4@vger.kernel.org>
Subject: Re: ext2_block_alloc_info
Date: Wed, 24 Dec 2008 10:23:44 -0600 [thread overview]
Message-ID: <49526210.4030606@redhat.com> (raw)
In-Reply-To: <804dabb00812222029x76d34c24o798ade5dd0e31351@mail.gmail.com>
Peter Teoh wrote:
> Sorry, resent due to SMTP error:
>
> anyone knows any way of enumerating all the low level information like
> these for each file?
>
> Best I can get is "debugfs":
which uses libext2fs, so if you look at the debugfs source you can find
out which basic library calls to use to get this information.
> So using "show_inode_infor xxxx":
>
> Inode: 1146884 Type: regular Mode: 0767 Flags: 0x0
> Generation: 4262211373
> User: 0 Group: 0 Size: 4670783
> File ACL: 0 Directory ACL: 0
> Links: 1 Blockcount: 9152
> Fragment: Address: 0 Number: 0 Size: 0
> ctime: 0x46db7fb6 -- Mon Sep 3 11:29:58 2007
> atime: 0x47c66735 -- Thu Feb 28 15:48:05 2008
> mtime: 0x43118298 -- Sun Aug 28 17:23:36 2005
> BLOCKS:
> (0-11):2317946-0, (IND):2317958, (12-1035):2317959-0, (DIND):2318983,
> (IND):2318984, (1036-1140):2318985-0
> TOTAL: 1144
>
> Here the "BLOCKS" correspond to the block numbering we are talking
> about, right? It always start at 0 per-file. "IND" is the indirect
> block. But what is "DIND"? "2317946" is the physical block number
> right? And what is the zero after the "2317946"?
BLOCKS: is the logical/physical mapping for the file.
(AA-BB): YY-ZZ are (logical):physical ranges.
IND is indirect, DIND is double indirect.
As for the "XXXX-0" I'm not sure offhand; it should be the start-end
range for the physical blocks. Bug perhaps? :)
-Eric
prev parent reply other threads:[~2008-12-24 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 15:43 ext2_block_alloc_info Rohit Sharma
2008-12-20 19:40 ` ext2_block_alloc_info Sandeep K Sinha
2008-12-20 19:44 ` ext2_block_alloc_info Rohit Sharma
2008-12-21 1:25 ` ext2_block_alloc_info Peter Teoh
2008-12-23 2:56 ` ext2_block_alloc_info Mike Snitzer
2008-12-23 4:27 ` ext2_block_alloc_info Peter Teoh
2008-12-23 4:29 ` ext2_block_alloc_info Peter Teoh
2008-12-23 4:37 ` ext2_block_alloc_info Sandeep K Sinha
2008-12-23 7:06 ` ext2_block_alloc_info Peter Teoh
2008-12-23 8:05 ` ext2_block_alloc_info Andreas Dilger
2008-12-24 6:45 ` ext2_block_alloc_info Sandeep K Sinha
2008-12-23 5:00 ` ext2_block_alloc_info Manish Katiyar
2008-12-24 16:23 ` Eric Sandeen [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=49526210.4030606@redhat.com \
--to=sandeen@redhat.com \
--cc=htmldeveloper@gmail.com \
--cc=imreckless@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-ext4@vger.kernel.org \
--cc=snitzer@gmail.com \
/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).