Karel Zak wrote:
I did some changes to the code:
* use mnt_resolve_target() rather than mnt_resolve_spec() for target
* move all to get_btrfs_fs_root()
* make the basic if/else more readable
By the way, I am just fixing next btrfs issue. Now it is in blkid. And
it seems, that I will need some changes in the code: move the btrfs
default subvol function into the public API, and change it to return the
subvolid string.
What do you think? Should I make this function linux or linux+btrfs
specific (missing in the API/ABI otherwise, where include file would
contain #define MOUNT_HAS_BTRFS_SUPPORT or so), or implement it for all
systems. On unsupported systems it would always return NULL (the define
could exist in this case as well, but it would be optional).
Please, please, test it.
I'll test it. I think that the attached reproducer should work on any
system with btrfs support.
It would be nice to have tests/ts/mount/btrfs with all the "mount -a"
variants you have in commit messages.
Are there any rules/framework for such tests that need root and editing
of /etc/fstab?
I think that use of losetup and /dev/loopX can be used for most
testcases. I am not sure about kernel partition table support inside
loop devices.
And by the way, loop it the only device that can be used for TRIM
testing: TRIM is internally converted to making unused blocks sparse.
Here is an example of TRIM testcase using loop:
dd if=/dev/null of=loop.img seek=1000000
mkfs.btrfs /root/loop.img
mount -oloop /root/loop.img /mnt
filefrag -e loop.img
for i in $(seq 0 100) ; do dd if=/dev/urandom of=/mnt/file$i bs=1M
count=10 ; done
filefrag -e loop.img
rm /mnt/file*
fstrim /mnt
# wait some time to complete
filefrag -e loop.img
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxxx
Lihovarská 1060/12 tel: +49 911 7405384547
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
