On 09:20 24 Mar 2003, Edward Dekkers <[EMAIL PROTECTED]> wrote:
| >Mar 21 22:11:09 wolfserver kernel: EXT3-fs error (device ida0(72,1)):
| > read_block_bitmap: Cannot read block bitmap - block_group = 7,
| > block_bitmap = 229380
| > Mar 21 22:11:09 wolfserver kernel: Fatal error on ida/c0d0
| >
|
>Mar 21 22:11:09 wolfserver kernel: EXT3-fs error (device ida0(72,1)):
> read_block_bitmap: Cannot read block bitmap - block_group = 7,
> block_bitmap = 229380
> Mar 21 22:11:09 wolfserver kernel: Fatal error on ida/c0d0
>
> After this, the messages just repeat until the crash...
HHmmm. Find out w
List,
Tonight my server crashed and in the Messages log I got these messages.
After a reboot and a journal recovery, I'm back in business, but what
would cause this?
Please let me know is you need any further information...
Thanks
Joe
Mar 21 22:10:03 wolfserver kernel: Non Fatal error on ida/
Hi
I have plenty of orphaned inodes, inode bitmap differences etc, many.
How can I fix these without taking the server down?
I think e2fsck only works on unmounted partitions is this correct?
Many Thanks
Mike
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscr
shop that built it because Seagate said that bios had
missed identified the drive geometry and had the head
sectors ect set wrong.
Linda
- Original Message -
From: Dan Horth <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 25, 2000 6:59
just saw these two errors in my log files... can someone enlighten me
as to what may be going on here... these drives are two of the three
that form our mission-critical file server raid-5 volume... should I
be concerned?
tia. dan.
May 26 01:08:25 kernel: hda: status timeout: status=0xd0 { Bu
Hiya - still trying to find bad blocks and reformat my scsi disk -
not sure if it's the way to get this working but I'm seeing loads of
these errors in /var/log/messages:
May 19 14:12:43 magma kernel: Deferred error sd08:01: sense key Medium Error
May 19 14:12:43 magma kernel: Additional sense
