Custom Query (684 matches)
Results (64 - 66 of 684)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#172 | fixed | kernel panic during mindi process when using mondo rescue on x86_64 HP Proliant dl360g4 (RHEL4.5) | ||
Description |
When Mondo Rescue iso image we get: RAX: ffffffff803f0520 RBX: 0000000000000000 RCX: 000000000000003f RDX: 000001007b8bfef8 RSI: 000001007ba517c8 RDI: 000001007fbf9180 RBP: 000001007b8bfef8 R08: 0000000000000000 R09: 0000000000631e98 R10: 000000000000000c R11: 0000000000000000 R12: 0000007fbfffff47 R13: 0000000000000000 R14: 00000000006376b8 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff804ed700(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0 Process find-and-mount- (pid: 1034, threadinfo 000001007b8be000, task 000001007bb70030) Stack: ffffffff801823d7 000001007ba517c8 000001007fbf9180 0000000000000202 ffffffff8012442d 0000000100000001 ffffffff00000000 0000000000000007 0000000b0000000e 000001007b8bff18 Call Trace:<ffffffff801823d7>{vfs_stat64+47} <ffffffff8012442d>{do_page_fault+577} <ffffffff8013bdff>{do_wait+3350} <ffffffff80182717>{sys_newstat+17} <ffffffff801342a4>{default_wake_function+0} <ffffffff80110d91>{error_exit+0} <ffffffff8011026a>{system_call+126} Code: Bad RIP value. RIP [<0000000000000000>] RSP <000001007b8bfe50> CR2: 0000000000000000 <0>Kernel panic - not syncing: Oops All the firmware is up2date. We've been able to use Mondo Rescue on a dl360g3 (32 bit platform) without issues using RHEL 4.4) |
|||
#173 | fixed | mindi cannot copy files - reports that maybe it ran out if disk space but I still have disk space and inodes left | ||
Description |
I'm a very long time mondo user (since hugo rabson wrote it) but since a week mindi failes with a message that it cannot copy the file /usr/X11R6/bin/afio to tmp.mondo.17319/tmp.mondo.24604/bigdir and reports - did you run out of disk space ? I checked and I have plenty of space left on the device and I also checked the inodes usage with df -i and it says: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hda3 0 0 0 - / udev 95860 1476 94384 2% /dev /dev/hda1 10040 57 9983 1% /boot none 95860 1 95859 1% /dev/shm strange thing is that /dev/hda3 (where mondo creates its files) has no inodes listed, is that normal? However I don't see why mindi stopped working and also installing the newest mindi 1.2.4 does not help. However here is the full mindi.log + mondoarchive.log |
|||
#223 | fixed | mondo restore hang no floppy present | ||
Description |
On Debian etch with mondo 2.2.4 installed I am seeing a hang during mondo restore while "I'm thinking..." due to my machine having no floppy drive. This appears to be same as ticket#136 which changeset[1496] tries to fix. The fix doesnt work on my machine since the dmesg | grep -i floppy shows a valid device. My machine has a floppy controller but no drive, I think the floppy driver prints a boot message on seeing the controller but doesnt know that no drive is attached. A better test would be to use "getfdprm /dev/fd0u1722" from fdutils - this returns immediately with NO DEVICE. Alternately use low level calls: #include <linux/fd.h> struct floppy_struct fdprms; int ifd, res; ifd = open("/dev/fd0u1722", O_RDONLY); if (ifd > 0) { open OK
} else { skip mount } Of course, same test would apply to /dev/fd0H1440. |