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

Failed test cases - "Unable to remove wrapper device" #132

Open
squizz617 opened this issue Apr 10, 2019 · 1 comment
Open

Failed test cases - "Unable to remove wrapper device" #132

squizz617 opened this issue Apr 10, 2019 · 1 comment

Comments

@squizz617
Copy link

Hi.
While testing seq-2 workloads, I get a lot of "Could not run test" messages.
In the log, it says "Unable to remove wrapper device":

--------------------Test #22--------------------
2019-04-05 18:20:41.828 Running test : j-lang96161as Crashmonkey standalone
Running test #22 : j-lang961612019-04-05 18:20:43.349
Error in test run, exits with status: 4352
Unable to remove wrapper device
2019-04-05 18:20:43.915 Retry running j-lang96161
2019-04-05 18:20:43.915 Running... 2019-04-05 18:20:43.930
Error starting socket to listen on 98
2019-04-05 18:20:43.941 Retry running j-lang96161
2019-04-05 18:20:43.941 Running... 2019-04-05 18:20:45.460
Error in test run, exits with status: 4352
Unable to remove wrapper device
2019-04-05 18:20:45.995 Retry running j-lang96161
2019-04-05 18:20:45.995 Running... 2019-04-05 18:20:46.11 Could not run test : j-lang96161

May I know why this happens, and is there a fix for this?

@ashmrtn
Copy link
Member

ashmrtn commented Apr 11, 2019

Hello,

Without more information, it appears that one of the earlier tests failed or died abnormally and the disk wrapper kernel module could not be removed. Checking dmesg may have more information on this (the entries will start with 'hwm' if they are in dmesg), but it is hard to tell. You can try using lsmod and looking for disk_wrapper to see if it is in use by anything ('used by' column in the output). If it isn't, you should be able to run rmmod disk_wrapper to remove it from the system and then try running xfsmonkey again. In the worst case, if you can't remove disk_wrapper with rmmod you can reboot the machine/VM you are running CrashMonkey on and that will remove the kernel module from the system.

As far as real fix for this, I can't really say since it could be caused by a number of things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants