I think its a good idea to populate fs and verify them after conversion.
I'm not sure about existing tools, simply we can create local script to
this testsuite. Some thoughts on possible data set:
--
a) regular files
- empty files (touch)
- smaller files dd if=/dev/zero
- smaller files dd if=/dev/urandom
b) directory
- empty dirs.
- dir with files
- dir depth upto N
- dir with no file but lot of unlinked entries.
c) fast/slow symlink
- to dir
- to file
d) hardlink :
- between files
- between files in different sub-dir
e) fifo files and sparsefile, broken symlink
f) file and dir with special inode attribute:
- immutable flag
- sticky bit etc
g) file/directory acls:
- large no.of acls
--
fs images with debugfs tool:
a) an valid image with bad blocks.
b) corrupted images:
Ex: Create duplicate blocks and convert it & expect btrfs-check to catch issue?
Any thoughts on above list, suggestions/comments? thanks!
Cheers,
Lakshmipathi.G
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
