Opened 12 years ago

Closed 12 years ago

#150 closed defect (fixed)

Restore crashes during ext3 format of LVM

Reported by: eleventeenth Owned by: bruno
Priority: normal Milestone: 2.2.4
Component: mondo Version: 2.2.1
Severity: normal Keywords:
Cc:

Description

Hardware: Dell PowerEdge? 1855 (Blade server) OS: Fedora Core 5 (LVM based) Boot options: added "ramdisk_blocksize=1024" (fedora specific)

All blades in teh chasis are exactly the same. After install on one blade, we imaged a DVD using the most recent Mondo. Using this DVD, we attempted to restore onto another of the blades. This crashed out after it started to format the LVM partitions it just created.

This was first attempted on non-interractive. We then tried on interractive, then tried to mkfs.ext3 on the LVM partitions from expert mode. Each resulted in:

Writing INODE tables: bad page state in process 'mkfs.ext2'

we could not get log files as it locked fully and needed reboot. Other errors were displayed on screen, but after about 30 seconds to 1 minute, the following was displayed:

Bug: spinlock lockup on CPU#0,mkfs.ext2/7559,c06c9380 (tainted: G B)

If we can provide further information, please ask.

Chris McLean?

Change History (5)

comment:1 Changed 12 years ago by bruno

Now that 2.2.2 is officially published on ftp://ftp.mondorescue.org could you check again if this has been solved for good.

comment:2 Changed 12 years ago by eleventeenth

will do when I can - which might be some time (weeks/months) as we have since manually installed all our blades

comment:3 Changed 12 years ago by bruno

Is it linked to http://www.nabble.com/BUG:-write-lock-lockup-t1776128.html ? In which case I suspect it has nothing to do with mondo in itself :-(

comment:4 Changed 12 years ago by bruno

Maybe related to #157 and an issue on FC5 kernel. Please try with an older kernel as well or mindi failsafe kernel

comment:5 Changed 12 years ago by bruno

  • Milestone set to 2.2.4
  • Resolution set to fixed
  • Status changed from new to closed

As I've got no news on that bug I'll close it. If it's not the case, please first test with the latest 2.2.4 before re-opening it.

Note: See TracTickets for help on using tickets.