On 4/21/20 12:11 PM, Will, Chris wrote: > Has anyone run into something like this? I would like to fix this > proactively and not wait until the server dies and I have to go into > emergency mode. This could be an issue with all our servers.
Hi, Chris, I really thing the BCACHE messages are a red herring. I'm not at all sure what the real cause of the problem is, but I don't think it's that. Have you opened a problem with your support provider? I think a lot more information is going to be needed to help you with this. As far as being proactive, there are a number of things you can try. I don't know that any of them will actually prevent the problem, since we don't really know what's causing it. The "Inconsistent metadata found for VG system-vg - updating to use version 8 n 8" message is the most interesting data point from what I can tell. If you possibly can, I would try to clone the DASD volume(s) that make up one of your other existing SLES12 SP4 systems, and see if you can recreate the problem. If so, then re-clone the volume(s), and try doing something like this: pvscan vgscan pvck /dev/dasd?? (for each physical volume) lvscan Then try extending a logical volume again and see if the problem reoccurs or not. This is very much stabbing in the dark, but it might provide some relief. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
