-
Notifications
You must be signed in to change notification settings - Fork 82
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
Kernel Panic when using OpenCAS on CentOS 7.8 #454
Comments
Hi @darktorana, Thank You for report. Could you please provide more information about CAS configuration You are using? We are interested in:
|
Hey @mmichal10, To answer your questions: I'm not sure if it will help, but the 2TB cache is sitting in front of 5TB of data though the raid is 10TB (will be expanded to 20TB). If there's anything else you need please just ask. |
Hi guys, Is there anything else I would be able to provide you to track down the root cause of this issue? |
Could You tell something about workload? We will try to reproduce it in our test environment. About using CAS in production environment: using |
What mail server is it? Workload as similar as possible to the one Your server is handling could help us reproduce you issue. If it is a free software, we could try to set it up on our machine. |
The software is called Axigen and does have a free version. You can find the version here: If you need any help setting it up let me know. |
Environment:
OS: CentOS 7.8
Kernel: 3.10.0-1127.8.2.el7.x86_64
OpenCAS Version: 20.06.00.00000603
Issue:
While operating normally for almost 2 weeks (11 days to be more precise) we had a server using OpenCAS Kernel Panic and the crash logs are pointing towards OpenCAS.
We do have another server in operation configured the same way that has been fine for over a month so we don't believe this is a common issue.
Crash Information:
The last of the crash log has the following:
Output of bt:
Reproduce Steps:
Unfortunately we have not had this happen again in order to provide more information so it might just be a once off, but was hoping to at least find out why it occurred.
Extra Information:
If there is anything else I can get you or information that might shed some light on why this has crashed please don't hesitate. We are using this in a production environment (after testing of course) and are keen to find out what caused the panic and if something can be done to prevent it.
The text was updated successfully, but these errors were encountered: