mirror of
https://github.com/kdave/btrfs-progs
synced 2024-12-28 09:02:19 +00:00
d4c4443c2d
mount command in old system can not add "-o loop" option automatically
for loop device, and make following test failed:
# ./fsck-tests.sh
...
[TEST] 013-extent-tree-rebuild
failed: mount /data/btrfsprogs/tests/test.img /data/btrfsprogs/tests/mnt
test failed for case 013-extent-tree-rebuild
Considering that $TEST_DEV can be block or loop device, we need determine
our mount option in a condition for both case.
This patch create a wrapper function for above request, to solve current
problem in 013-extent-tree-rebuild, and support similar request in future.
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|
||
|---|---|---|
| .. | ||
| 001-bad-file-extent-bytenr | ||
| 002-bad-transid | ||
| 003-shift-offsets | ||
| 004-no-dir-index | ||
| 005-bad-item-offset | ||
| 006-bad-root-items | ||
| 007-bad-offset-snapshots | ||
| 008-bad-dir-index-name | ||
| 009-no-dir-item-or-index | ||
| 010-no-rootdir-inode-item | ||
| 011-no-inode-item | ||
| 012-leaf-corruption | ||
| 013-extent-tree-rebuild | ||
| 014-no-extent-info | ||
| 015-check-bad-memory-access | ||
| 016-wrong-inode-nbytes | ||
| 017-missing-all-file-extent | ||