From: Andreas Dilger <adilger@sun.com>
To: Sandeep K Sinha <sandeepksinha@gmail.com>
Cc: Peter Teoh <htmldeveloper@gmail.com>,
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: Tue, 23 Dec 2008 01:05:45 -0700 [thread overview]
Message-ID: <20081223080545.GI5000@webber.adilger.int> (raw)
In-Reply-To: <37d33d830812222037s362060c3i8278a8a39083c50f@mail.gmail.com>
On Dec 23, 2008 10:07 +0530, Sandeep K Sinha wrote:
> I have a tool ready with unfolds a file system completely thrugh
> ioctl. You will just have to patch the kernel.
> And that also, its for ext2.
It would be much more generic to use the FIEMAP ioctl, which has made
it into the 2.6.28 kernel. It will currently only dump the file data
and xattr blocks, but it is designed to be extensible to allow dumping
other kinds of inode metadata (e.g. indirect/index blocks, etc).
> But its really verbose.
There are patches to e2fsprogs to allow filefrag to call FIEMAP to dump
the file layout. They were posted to this list a few months ago, and
are scheduled for upstream inclusion. While they will be part of e2fsprogs,
the FIEMAP ioctl is a generic mechanism that is supported by ext2/3/4,
OCFS, and XFS, and hopefully more now that it is in the kernel.
> You can have a look for the sources @ http://code.google.com/p/fscops/
> We will be uploading the tool there soon.
While the description of "What OHSM offer" sounds really good, I couldn't
find any code or description of what is actually implemented. Is this
a system that actually works, or is it only describing what you would like
OHSM to do?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-12-23 8:06 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 ` Andreas Dilger [this message]
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 ` ext2_block_alloc_info 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=20081223080545.GI5000@webber.adilger.int \
--to=adilger@sun.com \
--cc=htmldeveloper@gmail.com \
--cc=imreckless@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeepksinha@gmail.com \
--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).