[Ocfs2-tools-devel] [PATCH 10/0] Ocfs2-tools: Using fsck.ocfs2 prompt codes in fswreck v2.

[tristan.ye]

Changes from v2 to v1:

1.  Use marco to define corrupt_codes array as joel suggested.

2.  Make description for corrupt code more readable.

3.  Move fsck_type.h from all headers except for main.h

4.  Fix bug for EXTENT_EB_INVALID corrupter.

5.  Several other minor improvements.



Tristan.


On Fri, 2009-06-05 at 16:01 +0800, tristan.ye wrote:
> Hi all,
> 
> The current fswreck corrupt codes do more than one corruption and have
> no relation to the fsck.ocfs2 codes. fswreck needs a new option that can
> take one or more fsck.ocfs2 codes and do exactly those corruptions.
> 
> Such improvements based on the fact that we should leave the corrupt
> implementation and logic unchanged, we therefore still use the same
> handling funcs except for some minor changes and arguments
> adjustment(such as corrupt_file, mess_up_xxx etc).
> 
> New fsck corrupt codes supported in fswreck will be more exact and
> specific to become compatible with fsck.ocfs2 as a result. now we
> support meaningful commma-separated-values corrupt codes string as
> follows:
> 
> fswreck -c CORRUPT_TYPE1,CORRUPT_TYPE2,...,CORRUPT_TYPEN /dev/sdax
> 
> Refer to http://oss.oracle.com/osswiki/OCFS2/ToolsTasksList for more
> detai.
> 
> 
> Tristan.
> 
> 
> 
> _______________________________________________
> Ocfs2-tools-devel mailing list
> Ocfs2-tools-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-tools-devel