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_020_pos | rsend_021_pos #6446

Closed
dinatale2 opened this issue Aug 2, 2017 · 1 comment
Closed

Test case: rsend_020_pos | rsend_021_pos #6446

dinatale2 opened this issue Aug 2, 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

@dinatale2
Copy link
Contributor

dinatale2 commented Aug 2, 2017 •
edited
Loading

System information

Type Version/Name
Distribution Name All
Distribution Version All
Linux Kernel All
Architecture All
ZFS Version 0.7.0 (master)
SPL Version 0.7.0 (master)

Describe the problem you're observing

rsend_020_pos and rsend_021_pos appear to occasionally hang causing zfs tests to be killed by the buildbot.

Describe how to reproduce the problem

Buildbot.

Include any warning/errors/backtraces from the system logs

http://build.zfsonlinux.org/builders/Ubuntu%2016.04%20x86_64%20%28TEST%29/builds/241/steps/shell_8/logs/stdio

Test: /usr/share/zfs/zfs-tests/tests/functional/rsend/rsend_013_pos (run as root) [00:22] [PASS]
Test: /usr/share/zfs/zfs-tests/tests/functional/rsend/rsend_014_pos (run as root) [00:09] [PASS]
Test: /usr/share/zfs/zfs-tests/tests/functional/rsend/rsend_019_pos (run as root) [00:00] [SKIP]

command timed out: 4200 seconds without output running ['runurl', 'https://raw.githubusercontent.com/zfsonlinux/zfs-buildbot/master/scripts/bb-test-zfstests.sh'], attempting to kill
/usr/share/zfs/zfs-tests.sh: line 64:  7808 Terminated              ${TEST_RUNNER} ${QUIET} -c "${RUNFILE}" -i "${STF_SUITE}"
Terminated
umount: /testpool/stream: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
umount: /testpool: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
umount: /testpool/stream: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
umount: /testpool: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
@dinatale2 dinatale2 added the Component: Test Suite Indicates an issue with the test framework or a test case label Aug 2, 2017
@dinatale2 dinatale2 changed the title Test case: rsend_020_pos Test case: rsend_020_pos | rsend_021_pos Aug 3, 2017
@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
1 participant
@dinatale2