I was able to correct the error by uninstalling lvm2 and re-installing the original rpm from the installation media.
On Fri, Jun 12, 2009 at 10:17 AM, Mark Pace <[email protected]> wrote: > I connected to LVM DASD to another SLES11 guest, did a PVSCAN and now that > system also goes into 100% CPU. > After a ctrl-c I can continue to work, although very slow as it's still > using 100% cpu on something. > > sles001:~ # rpm -qa |grep lvm > lvm2-2.02.39-17.6.2 > > Same LVM version you have. > > I wonder if I can find the original LVM RPM and downgrade/replace the > apparently bad one? > > > On Fri, Jun 12, 2009 at 9:37 AM, Zamrykut, Darren <[email protected]>wrote: > >> On Friday 12 June 2009 07:23:08 Mark Pace wrote: >> > Did you get a resolution, Darren? >> > >> > I applied some maintenance to a SLES11 guest last night and >> now get the >> > same problems. >> > After the udevadm settle timeout, the events queue contains: >> > >> > 369: /devices/css0/0.0.000d/0.0.0214/block/dasdb/dasdb1 >> > 370: /devices/css0/0.0.000d/0.0.0214 >> > 377: /devices/css0/0.0.000e/0.0.0215/block/dasdc/dasdc1 >> > 378: /devices/css0/0.0.000e/0.0.0215 >> > 388: /devices/css0/0.0.000f/0.0.0216/block/dasdd/dasdd1 >> > 389: /devices/css0/0.0.000f/0.0.0216 >> > 396: /devices/css0/0.0.0010/0.0.0217/block/dasde/dasde1 >> > 397: /devices/css0/0.0.0010/0.0.0217 >> > 404: /devices/css0/0.0.0011/0.0.0218/block/dasdf/dasdf1 >> > 405: /devices/css0/0.0.0011/0.0.0218 >> > 412: /devices/css0/0.0.0012/0.0.0219/block/dasdg/dasdg1 >> > 413: /devices/css0/0.0.0012/0.0.0219 >> > 420: /devices/css0/0.0.0013/0.0.021a/block/dasdh/dasdh1 >> > 421: /devices/css0/0.0.0013/0.0.021a >> > 431: /devices/css0/0.0.0014/0.0.021b/block/dasdi/dasdi1 >> > 432: /devices/css0/0.0.0014/0.0.021b >> > 439: /devices/css0/0.0.0015/0.0.021c/block/dasdj/dasdj1 >> > 440: /devices/css0/0.0.0015/0.0.021c >> > 444: /devices/css0/0.0.0016/0.0.021d/block/dasdk/dasdk1 >> > 445: /devices/css0/0.0.0016/0.0.021d >> > >> > On Tue, May 12, 2009 at 3:55 PM, pcsd >> <[email protected]> wrote: >> > > Through the rescue system, I can manually mount the lvms >> and view the >> > > file structure. Data looks fine. >> > > It appears as though some applied patches have something >> to do with it. >> > > Specifically, lvm2-2.02.39-17.6.2. I have a call into Novell >> and I am >> > > currently trying to determine which patch it is through the >> process of >> > > elimination. >> > > >> > > Darren >> > > >> > > ---------------------------------------------------------------------- >> > > For LINUX-390 subscribe / signoff / archive access >> instructions, >> > > send email to [email protected] with the message: >> INFO LINUX-390 or >> > > visit >> > > http://www.marist.edu/htbin/wlvindex?LINUX-390 >> > >> > -- >> > Mark Pace >> > Mainline Information Systems >> > 1700 Summit Lake Drive >> > Tallahassee, FL. 32317 >> > >> > ---------------------------------------------------------------------- >> > For LINUX-390 subscribe / signoff / archive access instructions, >> > send email to [email protected] with the message: >> INFO LINUX-390 or >> > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 >> I still have a support call into Novell. We have tried several >> things, but no resolution as of yet. >> >> Darren >> >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> > > > > -- > Mark Pace > Mainline Information Systems > 1700 Summit Lake Drive > Tallahassee, FL. 32317 > -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
