On 2017年11月24日 19:42, Lakshmipathi.G wrote: >> >> To make it clear, what kernel config and commit are you using when the >> test fails? >> > When I use attached kernel config along with tar from misc-next branch > (wget https://github.com/kdave/btrfs-devel/archive/misc-next.zip) this > issue happens. BTW, David seems to update his branch more often in his git.kernel.org branch than github. So it's possible that the branch from github is out dated. > >> In my test, if I use the david/for-4.15 branch, it will fails to umount >> the fs, due to the known bug if you enabled >> CONFIG_BTRFS_FS_CHECK_INTEGRITY (you reported it first). >> And for any upstream kernel version like v4.14-rc7 or v4.14, not problem >> at all. >> > Here's btrfs related config. I checked with 4.14.2 it worked fine there too. > > The issue happens with v4.14-rc7, can you check with above config > file and zip file(misc-next.zip)? > > $ cat kernel.config | grep "BTRFS" > CONFIG_BTRFS_FS=y > CONFIG_BTRFS_FS_POSIX_ACL=y > CONFIG_BTRFS_FS_CHECK_INTEGRITY=n > CONFIG_BTRFS_FS_RUN_SANITY_TESTS=n > CONFIG_BTRFS_DEBUG=y > CONFIG_BTRFS_ASSERT=y > CONFIG_BTRFS_FS_REF_VERIFY=y For v4.14-rc7, even I enabled all the btrfs related configs, I still can't reproduce it. ------ $ zcat /proc/config.gz | grep BTRFS CONFIG_BTRFS_FS=m CONFIG_BTRFS_FS_POSIX_ACL=y CONFIG_BTRFS_FS_CHECK_INTEGRITY=y CONFIG_BTRFS_FS_RUN_SANITY_TESTS=y CONFIG_BTRFS_DEBUG=y CONFIG_BTRFS_ASSERT=y ------ So there is something strange happened. Thanks, Qu > > thanks! > > ---- > Cheers, > Lakshmipathi.G > http://www.giis.co.in http://www.webminal.org >
Attachment:
signature.asc
Description: OpenPGP digital signature
