At 01/11/2017 01:36 AM, [email protected] wrote:
What about submitting a btrfs-image and use generic test load?
Okay, how to share the corrupted btrfs-image? using github? And also do
you have references for this kind of
setup under btrfs-progs/tests/? So that I can follow its model.
At least I follow the following steps to create image:
- Create a 256M file
The default size of image.
All zero content is recommended for high compression ratio.
Both hole or fallocate is OK.
- Make btrfs on that file
- Fill the fs with minimum content
Just enough files/dirs for next step.
The smaller space it takes the better
- Corrupt the fs
Either using btrfs-corrupt-block or manually
- Take the dump
Either by btrfs-image or just use the raw image.
It's recommended to use btrfs-image and with -c9 option, which
can reduce the file size dramatically compared to xz raw image.
But we must ensure the recovered image still has the same
corruption, or we must use raw image.
For raw image, xz it just like other tests.
Normally submitted images are less than 100K, and that's small enough
to send as patch.
Thanks,
Qu
Cheers.
Lakshmipathi.G
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
