Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test case: zfs_destroy_010_pos #5893

Closed
behlendorf opened this issue Mar 14, 2017 · 1 comment
Closed

Test case: zfs_destroy_010_pos #5893

behlendorf opened this issue Mar 14, 2017 · 1 comment
Labels
Component: Test Suite Indicates an issue with the test framework or a test case Status: Stale No recent activity for issue

Comments

@behlendorf
Copy link
Contributor

System information

Type Version/Name
Distribution Name all
Distribution Version all
Linux Kernel all
Architecture all
ZFS Version 0.7.0-rc3
SPL Version 0.7.0-rc3

Describe the problem you're observing

Rare failure of test case zfs_destroy_010_pos due to an EBUSY error.

Describe how to reproduce the problem

Reproducible occasionally by the automated testing.

Include any warning/errors/backtraces from the system logs

http://build.zfsonlinux.org/builders/Ubuntu%2016.04%20x86_64%20Kmemleak%20%28TEST%29/builds/942/steps/shell_9/logs/log

Test: /usr/share/zfs/zfs-tests/tests/functional/cli_root/zfs_destroy/zfs_destroy_010_pos (run as root) [00:04] [FAIL]
23:05:12.66 ASSERTION: 'zfs destroy -R' works on deferred destroyed snapshots
23:05:12.80 SUCCESS: /sbin/zfs create testpool.26279/testctr26279
23:05:12.96 SUCCESS: /sbin/zfs create testpool.26279/testctr26279/testfs.26279
23:05:13.09 SUCCESS: /sbin/zfs create -V 150m testpool.26279/testctr26279/testvol26279
23:05:15.66 NOTE: SUCCESS: /sbin/mke2fs /dev/zvol/testpool.26279/testctr26279/testvol26279>/dev/null
23:05:15.66 SUCCESS: /bin/mkdir /var/tmp/testdir126279
23:05:15.72 SUCCESS: /bin/mount /dev/zvol/testpool.26279/testctr26279/testvol26279 /var/tmp/testdir126279
23:05:15.77 SUCCESS: /sbin/zfs snapshot testpool.26279/testctr26279/testfs.26279@testsnap26279
23:05:15.84 SUCCESS: /sbin/zfs snapshot testpool.26279/testctr26279/testvol26279@testsnap26279
23:05:16.02 SUCCESS: /sbin/zfs clone testpool.26279/testctr26279/testfs.26279@testsnap26279 testpool.26279/testfs.26279clone
23:05:16.10 SUCCESS: /sbin/zfs clone testpool.26279/testctr26279/testvol26279@testsnap26279 testpool.26279/testvol26279clone
23:05:16.15 SUCCESS: /sbin/zfs destroy -d testpool.26279/testctr26279/testfs.26279@testsnap26279
23:05:16.18 SUCCESS: datasetexists testpool.26279/testctr26279/testfs.26279@testsnap26279
23:05:16.22 cannot destroy 'testpool.26279/testfs.26279clone': dataset is busy
23:05:16.22 ERROR: /sbin/zfs destroy -R testpool.26279/testfs.26279clone exited 1
23:05:16.23 NOTE: Performing local cleanup via log_onexit (cleanup_testenv)
23:05:16.29 SUCCESS: /bin/umount -f /var/tmp/testdir126279
23:05:16.29 SUCCESS: rm -f -rf /var/tmp/testdir126279
23:05:16.89 SUCCESS: /sbin/zfs destroy -Rf testpool.26279/testctr26279
@behlendorf behlendorf added the Component: Test Suite Indicates an issue with the test framework or a test case label Mar 14, 2017
behlendorf added a commit to behlendorf/zfs that referenced this issue May 1, 2017
The following three test cases occasionally fail the automated
testing.  For the moment disable these test cases until the
underlying issues can be fully investigated and resolved.

zfs_destroy_010_pos - openzfs#5893
rsend_020_pos       - openzfs#6086 (32-bit only)
send-c_volume       - openzfs#6087 (32-bit only)

Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf added a commit to behlendorf/zfs that referenced this issue May 1, 2017
The following three test cases occasionally fail the automated
testing.  For the moment disable these test cases until the
underlying issues can be fully investigated and resolved.

zfs_destroy_010_pos - openzfs#5893
rsend_020_pos       - openzfs#6086 (32-bit only)
send-c_volume       - openzfs#6087 (32-bit only)

Signed-off-by: Brian Behlendorf <[email protected]>
Issue openzfs#5893
Issue openzfs#6086
Issue openzfs#6087
behlendorf added a commit to behlendorf/zfs that referenced this issue May 2, 2017
* zfs_destroy_001_pos - Unable to reproduce the failures locally.
  Re-enabled to determine observed buildbot failure rate.

* zfs_destroy_005_neg - Updated for expected Linux behavior.
  Busy mount points, even snapshots, are expected to fail.

* zfs_destroy_010_pos - Resolved transient EBUSY with retry.

Signed-off-by: Brian Behlendorf <[email protected]>
Issue openzfs#5635
Issue openzfs#5893
behlendorf added a commit that referenced this issue May 4, 2017
* zfs_destroy_001_pos - Unable to reproduce the failures locally.
  Re-enabled to determine observed buildbot failure rate.

* zfs_destroy_005_neg - Updated for expected Linux behavior.
  Busy mount points, even snapshots, are expected to fail.

* zfs_destroy_010_pos - Resolved transient EBUSY with retry.

Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Issue #5635 
Issue #5893 
Closes #6091
@stale
Copy link

stale bot commented Aug 25, 2020

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Aug 25, 2020
@stale stale bot closed this as completed Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Test Suite Indicates an issue with the test framework or a test case Status: Stale No recent activity for issue
Projects
None yet
Development

No branches or pull requests

1 participant