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.

Sign up for GitHub

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

Jump to bottom

Test case: rsend_024_pos #5665

Closed
behlendorf opened this issue Jan 25, 2017 · 2 comments
Closed

Test case: rsend_024_pos #5665

behlendorf opened this issue Jan 25, 2017 · 2 comments
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

Rarely observed failure of rsend_024_pos during automated testing.

Describe how to reproduce the problem

Reproducible by the buildbot.

Include any warning/errors/backtraces from the system logs

http://build.zfsonlinux.org/builders/Ubuntu%2014.04%20i686%20%28TEST%29/builds/686

Test: /usr/share/zfs/zfs-tests/tests/functional/rsend/rsend_024_pos (run as root) [00:00] [FAIL]
04:31:45.34 ASSERTION: Verify resumability of a full ZFS send/receive with the source  filesystem unmounted
04:31:45.37 ERROR: /sbin/zfs destroy -r testpool1.27205/recvfs exited 1
04:31:45.37 cannot destroy 'testpool1.27205/recvfs': dataset is busy
04:31:45.37 NOTE: Performing local cleanup via log_onexit (cleanup_pool testpool1.27205)
04:31:45.38 SUCCESS: rm -f -rf /var/tmp/backdir-rsend/*
04:31:45.40 ERROR: /sbin/zfs destroy -Rf testpool1.27205 exited 1
04:31:45.40 cannot destroy 'testpool1.27205/recvfs': dataset is busy
@behlendorf behlendorf added Type: Architecture Indicates an issue is specific to a single processor architecture Component: Test Suite Indicates an issue with the test framework or a test case labels Jan 25, 2017
behlendorf added a commit to behlendorf/zfs that referenced this issue Jan 25, 2017
@behlendorf
Refresh Linux test suite runfile
49bcbdb 
Associate disabled test cases with existing open issues, update
comments to be consistent, disable a few additional test cases.
The goal is for all enabled test to pass 100% reliably.

The following test cases have been disabled due to infrequent
failures during automated testing.  Several of these test cases
were previous disabled only for the kmemleak builder but have
subsequently been observed on other automated builders.

- zfs_destroy_001_pos - openzfs#5635
- zfs_rename_006_pos  - openzfs#5647
- zfs_rename_009_neg  - openzfs#5648
- zpool_clear_001_pos - openzfs#5634
- zfs_allow_010_pos   - openzfs#5646
- reservation_018_pos - openzfs#5642
- snapused_004_pos    - openzfs#5513
- rsend_022_pos       - openzfs#5654
- rsend_024_pos       - openzfs#5665
- history_008_pos     - openzfs#5658
- history_006_neg     - openzfs#5657
- history_008_pos     - openzfs#5658

Signed-off-by: Brian Behlendorf <[email protected]>
@behlendorf behlendorf mentioned this issue Jan 25, 2017
Merged
behlendorf added a commit to behlendorf/zfs that referenced this issue Jan 26, 2017
@behlendorf
Refresh Linux test suite runfile
0a209ca 
Associate disabled test cases with existing open issues, update
comments to be consistent, disable a few additional test cases.
The goal is for all enabled test to pass 100% reliably.

The following test cases have been disabled due to infrequent
failures during automated testing.  Several of these test cases
were previous disabled only for the kmemleak builder but have
subsequently been observed on other automated builders.

- zfs_destroy_001_pos - openzfs#5635
- zfs_rename_006_pos  - openzfs#5647
- zfs_rename_009_neg  - openzfs#5648
- zpool_clear_001_pos - openzfs#5634
- zfs_allow_010_pos   - openzfs#5646
- reservation_018_pos - openzfs#5642
- snapused_004_pos    - openzfs#5513
- rsend_022_pos       - openzfs#5654
- rsend_024_pos       - openzfs#5665
- history_008_pos     - openzfs#5658
- history_006_neg     - openzfs#5657
- history_008_pos     - openzfs#5658
- zfs_inherit_003_pos - openzfs#5669

Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf added a commit that referenced this issue Jan 26, 2017
@behlendorf
Refresh Linux test suite runfile
f925de3 
Associate disabled test cases with existing open issues, update
comments to be consistent, disable a few additional test cases.
The goal is for all enabled test to pass 100% reliably.

The following test cases have been disabled due to infrequent
failures during automated testing.  Several of these test cases
were previous disabled only for the kmemleak builder but have
subsequently been observed on other automated builders.

- zfs_destroy_001_pos - #5635
- zfs_rename_006_pos  - #5647
- zfs_rename_009_neg  - #5648
- zpool_clear_001_pos - #5634
- zfs_allow_010_pos   - #5646
- reservation_018_pos - #5642
- snapused_004_pos    - #5513
- rsend_022_pos       - #5654
- rsend_024_pos       - #5665
- history_008_pos     - #5658
- history_006_neg     - #5657
- history_008_pos     - #5658
- zfs_inherit_003_pos - #5669

Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #5649
wli5 pushed a commit to wli5/zfs that referenced this issue Feb 28, 2017
@behlendorf @wli5
Refresh Linux test suite runfile
4d38f3d 
Associate disabled test cases with existing open issues, update
comments to be consistent, disable a few additional test cases.
The goal is for all enabled test to pass 100% reliably.

The following test cases have been disabled due to infrequent
failures during automated testing.  Several of these test cases
were previous disabled only for the kmemleak builder but have
subsequently been observed on other automated builders.

- zfs_destroy_001_pos - openzfs#5635
- zfs_rename_006_pos  - openzfs#5647
- zfs_rename_009_neg  - openzfs#5648
- zpool_clear_001_pos - openzfs#5634
- zfs_allow_010_pos   - openzfs#5646
- reservation_018_pos - openzfs#5642
- snapused_004_pos    - openzfs#5513
- rsend_022_pos       - openzfs#5654
- rsend_024_pos       - openzfs#5665
- history_008_pos     - openzfs#5658
- history_006_neg     - openzfs#5657
- history_008_pos     - openzfs#5658
- zfs_inherit_003_pos - openzfs#5669

Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5649
wli5 pushed a commit to wli5/zfs that referenced this issue Feb 28, 2017
@behlendorf @wli5
Refresh Linux test suite runfile
af1a9f0 
Associate disabled test cases with existing open issues, update
comments to be consistent, disable a few additional test cases.
The goal is for all enabled test to pass 100% reliably.

The following test cases have been disabled due to infrequent
failures during automated testing.  Several of these test cases
were previous disabled only for the kmemleak builder but have
subsequently been observed on other automated builders.

- zfs_destroy_001_pos - openzfs#5635
- zfs_rename_006_pos  - openzfs#5647
- zfs_rename_009_neg  - openzfs#5648
- zpool_clear_001_pos - openzfs#5634
- zfs_allow_010_pos   - openzfs#5646
- reservation_018_pos - openzfs#5642
- snapused_004_pos    - openzfs#5513
- rsend_022_pos       - openzfs#5654
- rsend_024_pos       - openzfs#5665
- history_008_pos     - openzfs#5658
- history_006_neg     - openzfs#5657
- history_008_pos     - openzfs#5658
- zfs_inherit_003_pos - openzfs#5669

Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5649
@dinatale2 dinatale2 removed the Type: Architecture Indicates an issue is specific to a single processor architecture label Aug 9, 2017
@dinatale2 dinatale2 changed the title Test case: rsend_024_pos (32-bit only) Test case: rsend_024_pos Aug 9, 2017
@dinatale2
Copy link
Contributor

This test case also hangs on occasion on various TEST builders. I went ahead and removed the Architecture Specific tag. This issue can become the generic "fix rsend_024_pos" issue.

@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
behlendorf added a commit that referenced this issue Dec 21, 2021
@behlendorf
ZTS: rsend_007_pos failures
7b5d783 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #5665
Closes #6086
Closes #6087
Closes #6446
Closes #12876
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Feb 10, 2022
@behlendorf @tonyhutter
ZTS: rsend_007_pos failures
fa93a7d 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5665
Closes openzfs#6086
Closes openzfs#6087
Closes openzfs#6446
Closes openzfs#12876
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Feb 14, 2022
@behlendorf @tonyhutter
ZTS: rsend_007_pos failures
3013a15 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5665
Closes openzfs#6086
Closes openzfs#6087
Closes openzfs#6446
Closes openzfs#12876
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Feb 16, 2022
@behlendorf @tonyhutter
ZTS: rsend_007_pos failures
200c05d 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5665
Closes openzfs#6086
Closes openzfs#6087
Closes openzfs#6446
Closes openzfs#12876
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Feb 17, 2022
@behlendorf @tonyhutter
ZTS: rsend_007_pos failures
be01ee8 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5665
Closes openzfs#6086
Closes openzfs#6087
Closes openzfs#6446
Closes openzfs#12876
nicman23 pushed a commit to nicman23/zfs that referenced this issue Aug 22, 2022
@behlendorf @nicman23
ZTS: rsend_007_pos failures
1d39d5d 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5665
Closes openzfs#6086
Closes openzfs#6087
Closes openzfs#6446
Closes openzfs#12876
nicman23 pushed a commit to nicman23/zfs that referenced this issue Aug 22, 2022
@behlendorf @nicman23
ZTS: rsend_007_pos failures
4c55ec0 
The rsend_007_pos test reliably fails on Linux in the cleanup
function.  This is caused by an unmount error when attempting to
recursively destroy the newly received datasets.  Invoking `df`
prior to the `zfs destroy` interestingly avoids the unmont error.

Why this should matter is unclear and should be investigated.
However, this minor tweak may allow us to remove the ZTS rsend
exceptions.  The subsequent rsend_010_pos and rsend_011_pos
failures were a result of this initial failure.  The other
"maybe" failures I was unable to reproduce and have not been
recently observed in the master branch.

Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#5665
Closes openzfs#6086
Closes openzfs#6087
Closes openzfs#6446
Closes openzfs#12876
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@behlendorf @dinatale2