Open-CAS / open-cas-linux

Open CAS Linux
https://open-cas.com
BSD 3-Clause "New" or "Revised" License
224 stars 82 forks source link

OpenCAS Metadata ERROR at Rebooting #455

Closed ycs0220 closed 4 years ago

ycs0220 commented 4 years ago

Environment

eriksun421 commented 4 years ago

Hi, can you please provide following information ?

  1. CAS configuration: /etc/opencas/opencas.conf
  2. casadm -L
  3. casadm -P -i X // X is your CAS instance ID you assigned when it is created.
  4. Detailed steps to reproduce this issue ? Is it a dirty shutdown or clean shutdown ? Is there any filesystem or LVM on top of CAS device ? Is there any I/O requests on CAS device when you reboot the system ? Is it 100% reproducible ? This is very important information that can help us analyze this issue. Please provide as much details as you can.
ycs0220 commented 4 years ago

Hi, can you please provide following information ?

  1. CAS configuration: /etc/opencas/opencas.conf
  2. casadm -L
  3. casadm -P -i X // X is your CAS instance ID you assigned when it is created.
  4. Detailed steps to reproduce this issue ? Is it a dirty shutdown or clean shutdown ? Is there any filesystem or LVM on top of CAS device ? Is there any I/O requests on CAS device when you reboot the system ? Is it 100% reproducible ? This is very important information that can help us analyze this issue. Please provide as much details as you can.

Thank you for your reply! Some detailes as follows:

There is no any filesystem or LVM on top of CAS device, we do two cases to Reproduce this problem, Metadata ERROR occurs in both cases

jfckm commented 4 years ago

Hi @ycs0220,

I have a few questions for you to help us pin down the issue you're observing.

This section of metadata is extremely unlikely to produce such errors consistenly, especially without any I/Os while rebooting... So there must be something strange going on.

ycs0220 commented 4 years ago

@robertbaldyga @imjfckm @eriksun421 @argretzi Thanks for your reply! This problem was fixed in version V20.3.1, i will close this issue. This is related to the server S3/S4 status suggested in the previous intelcas document.