Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
• application/x mplayer2 plugin
• RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
• Command stream end of file while reading
• X Windows problem (xauth)
• Upgrading openoffice 1 1 rpm
• FTP: connection refused
• FTP: connection refused
• mount: /dev/cdrom: is not a valid block device
• Dell Precision 650, RedHat 9, no sound
• how to trace the cause resulting in the crash of bind server
• Virus on the list
• UNINSTALL RPM MYSQL
• usb pen drives: mounting as a user
• broadcom network interface
• make mrproper
• sendmail configuration on redhat
• Couldn 't open PID file /var/run/named/named pid Permission denied
• Promise 378 controller
• kernel 2 6 and /dev/sound/mixer not found
• Problem using up2date
• mrtg step by step howto/configuration for a newbie?
• Compiling and Installing Kernel 2 6
• Can 't locate module ppp0, can 't locate module ppp compress 21
• HOW I CAN MAKE BOOTABLE FLOPPY DISKET
• Lotus Notes under Wine
• /etc/security/limits conf question
• Intel E/1000 driver
• Command stream end of file while reading
• rpm database corrupt
• qla2300 modules
 
SCSI error and data loss with ext3 filesystem

SCSI error and data loss with ext3 filesystem

2005-10-19       - By wolf2k5

 Back
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

Hi all,

This morning I applied all the RHEL3 U6 packages, including new
kernel, to a Dell PowerEdge 1655MC and I rebooted it.

The server worked fine for a few hours, then suddenly I wasn't able to
send email to it anymore.

I logged into it and I couldn't save anything to the root filesystem,
since it was mounted in read-only mode for some reason!

I  checked the /var/log/messages file and there was the following entry:

Oct 19 15:20:48 my server kernel: SCSI disk error : host 0 channel 0
id 0 lun 0 return code = 28000002

Then I checked the console and there were the following entries:

myserver kernel: journal commit I/O error

...

sd(8,3)) in start_transaction: Journal has aborted
EXT3-fs error (device sd(8,3)) in start_transaction: Journal has aborted

The latest entry was repeated a lot of times.

Apparently there was an issue with the HD and Linux automatically
remounted the filesystem in read-only mode. Is this correct?

I rebooted the server and when it came back online I checked the
/var/log/messages file and to my surprise the above entry about the
SCSI disk error was gone: there was an hole of a few minutes in the
file!

The /var/log/maillog file also had a similar hole.

Apparently Linux wasn't able to save the latest changes to those files
to the HD.
But it's weird that I saw the entry about the SCSI disk error before
the reboot (I issued a 'cat' on the file) and it was gone after the
reboot.

Is this one of the 'feature' of the ext3 filesystem? Any way to disable it?

Also do you have any idea about the SCSI issue in question? Does it
look a SW or HW issue?

I would say it looks an HW issue, but since it aroused just after
applying the RHEL U6 packages, it may be a SW issue ...

This server worked fine for an year or so.

BTW, if I reboot the server and choose the old kernel, will Linux use
the previous modules (e.g. SCSI driver) too?

Thanks.

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list