On 2019/6/12 下午9:51, Tomasz Kłoczko wrote: > On Tue, 11 Jun 2019 at 20:02, David Sterba <dsterba@xxxxxxxx> wrote: >> btrfs-progs version 5.1.1 have been released. > > Still test suite is failing for me. > > + /usr/bin/make test > [TEST] fsck-tests.sh > [TEST/fsck] 001-bad-file-extent-bytenr > [TEST/fsck] 002-bad-transid > [TEST/fsck] 003-shift-offsets > [TEST/fsck] 004-no-dir-index > [TEST/fsck] 005-bad-item-offset > [TEST/fsck] 006-bad-root-items > [TEST/fsck] 007-bad-offset-snapshots > [TEST/fsck] 008-bad-dir-index-name > [TEST/fsck] 009-no-dir-item-or-index > [TEST/fsck] 010-no-rootdir-inode-item > [TEST/fsck] 011-no-inode-item > [TEST/fsck] 012-leaf-corruption > [TEST/fsck] 013-extent-tree-rebuild > [TEST/fsck] 014-no-extent-info > [TEST/fsck] 016-wrong-inode-nbytes > [TEST/fsck] 017-missing-all-file-extent > [TEST/fsck] 018-leaf-crossing-stripes > [TEST/fsck] 019-non-skinny-false-alert > [TEST/fsck] 020-extent-ref-cases > [TEST/fsck] 021-partially-dropped-snapshot-case > [TEST/fsck] 022-qgroup-rescan-halfway > [TEST/fsck] 023-qgroup-stack-overflow > [TEST/fsck] 024-clear-space-cache > [TEST/fsck] 025-file-extents > [TEST/fsck] 026-bad-dir-item-name > [TEST/fsck] 027-bad-extent-inline-ref-type > [TEST/fsck] 028-unaligned-super-dev-sizes > [TEST/fsck] 029-valid-orphan-item > [TEST/fsck] 030-reflinked-prealloc-extents > [TEST/fsck] 031-metadatadump-check-data-csum > [TEST/fsck] 032-corrupted-qgroup > [TEST/fsck] 033-lowmem-collission-dir-items > [TEST/fsck] 034-bad-inode-flags > [TEST/fsck] 035-inline-bad-ram-bytes > [TEST/fsck] 036-bad-dev-extents > [TEST/fsck] 036-rescan-not-kicked-in > [TEST/fsck] 037-freespacetree-repair > failed: root_helper umount > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//test.img > test failed for case 037-freespacetree-repair > make: *** [Makefile:352: test-fsck] Error 1 > error: Bad exit status from /var/tmp/rpm-tmp.3DQ01g (%check) > > In log line I found: > > ====== RUN CHECK root_helper mount -t btrfs -o loop > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//test.img > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//mnt > ====== RUN CHECK root_helper fallocate -l 50m > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//mnt/file > ====== RUN CHECK root_helper umount > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//test.img > umount: /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests/mnt: > target is busy. > failed: root_helper umount > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//test.img > > After test suite fails I'm able to umount it manually. > > [tkloczko@domek tests]$ sudo umount > /home/tkloczko/rpmbuild/BUILD/btrfs-progs-v5.1.1/tests//test.img > [tkloczko@domek tests]$ > > So looks like during umount still something is holding umount. Similar situation here, but if you're using DE or things like udisk, it's mostly such tools affecting the umount. For me, inside a minimal VM, without all the GUI things listening on mounted locations, 037 will pass without problem. Thanks, Qu > > kloczek >
Attachment:
signature.asc
Description: OpenPGP digital signature
