[Ocfs2-tools-devel] [PATCH 6/6] debugfs.ocfs2: Journal logdump prints full inode and extent blocks

Sunil Mushran sunil.mushran at oracle.com
Thu Dec 16 09:39:02 PST 2010


On 12/16/2010 12:07 AM, Joel Becker wrote:
> On Wed, Dec 15, 2010 at 06:41:09PM -0800, Sunil Mushran wrote:
>> +		dump_inode(out, di);
>> +		if (di->i_flags&  OCFS2_LOCAL_ALLOC_FL)
>> +			dump_local_alloc(out,&(di->id2.i_lab));
>> +		else if (di->i_flags&  OCFS2_CHAIN_FL)
>> +			dump_chain_list(out,&(di->id2.i_chain));
>> +		else if (S_ISLNK(di->i_mode)&&  !di->i_clusters)
>> +			dump_fast_symlink(out, (char *)di->id2.i_symlink);
>> +		else if (di->i_flags&  OCFS2_DEALLOC_FL)
>> +			dump_truncate_log(out,&(di->id2.i_dealloc));
>> +		else if (!(di->i_dyn_features&  OCFS2_INLINE_DATA_FL))
>> +			dump_extent_list (out,&(di->id2.i_list));
> 	Shouldn't we allow an option like the -T option to inode
> dumping?  I don't want to dump massive extent lists all the time; maybe
> I just want to see the summary of the inode, etc.

This is the journal dump.  -T is already an option for inode dumping (stat).



More information about the Ocfs2-tools-devel mailing list