Thread (13 messages) 13 messages, 7 authors, 2008-12-24

Re: ext2_block_alloc_info

From: Sandeep K Sinha <hidden>
Date: 2008-12-24 06:46:00

Thanks a lot Peter and Andreas for taking out time and going through fscops.
We welcome all your suggestion.

We will soon be uploading all the docs/sources on to the web.
Stay tuned !!!

Thanks,
Again

On Tue, Dec 23, 2008 at 1:35 PM, Andreas Dilger [off-list ref] wrote:
On Dec 23, 2008  10:07 +0530, Sandeep K Sinha wrote:
quoted
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).
quoted
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.
quoted
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.


-- 
Regards,
Sandeep.





 	
"To learn is to change. Education is a process that changes the learner."
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help