On Wed 20 June 2007 13:59, Kenneth Schneider wrote:
> On Wed, 2007-06-20 at 09:05 +0200, [EMAIL PROTECTED] wrote:
> > Here some HW details:
> > 1. A 5 year old system that had win2K on it for 3 years and since then
> > SuSE 9.3 and all the following. Here the problem occur with OpenSUSE
>
> 5 year old system = possible harddrive beyond its life expectancy.
>
> > 10.2. It has an ASUS mobo with ATI Radion graphic card.
> > 2. A 2 year old system only had SuSE 10.0 that had the problem and now
> > has WinXP without any problems. It's a Gigabyte mobo with ATI Radion
> > graphic card. I noticed that intensive file access by Evolution caused a
> > systrem lockup many times.
> > 3. The latest 1 year old system showed the problem mainly with SUSE 10.0
> > and now with OpenSUSE 10.2. An identical system has SuSE 10.1, where the
> > problem has till now not occured. It is a Gigabyte GA-K8N-SLi mobo with
> > nVidia GeForce 7600 GS.
>
> Even newer systems come with a one year warranty on IDE harddrives. I've
> seen new drives fail after only a couple of months of use includinf SCSI
> drives which generally have a longer life expectancy.
>
> > The difference between the lockups of the SUSE 10.0 and OpenSUSE 10.2 is
> > that with 10.0 it did not allow any access to the system at all; a
> > complete lockdown - dead - only reset got it unlocked. The OpenSUSE 10.2
> > reports RO FS problems by all applications. The system can be rebooted or
> > shut down normally.
> >
> > plus
> >
> > > information from /var/log/messages about what is happening when the
> > > filesystem goes RO
> >
> > I noticed on two different systems this sort of messages
> > in /var/logs/messages:
> >
> > Jun 2 22:15:03 kakalapap kernel: hda: task_no_data_intr: status=0x51
> > { DriveReady SeekComplete Error }
> > Jun 2 22:15:03 kakalapap kernel: hda: task_no_data_intr: error=0x04
> > { DriveStatusError }
> > Jun 2 22:15:03 kakalapap kernel: ide: failed opcode was: 0xef
>
> I only see these errors in relation to my DVD/CD drive (hda). Could this
> possibly relate to your CD drive? If not I would suspect a bad cable.
>
I followed Carl's suggestion and changed the file systems to ext3. It seems
that the use of different file systems on the same drive with different
partitions is the problem. Since I changed all partitins to ext3, the problem
did not come up anymore. High disk access does not seem to bother it now. I
have also reduced the number of e-mails in the mail boxes as Graham suggests,
but only one account is IMAP. This was done after the FS's were changed, and
it caused a lot of disk access when deleting the mails. Everything, including
the large *.jpg, *.tiff & other graphics files in Gimp could be processed
with high disk access also. So all seem to point into the direction Carl
described thus:
On Tue 19 June 2007 23:47, Carl Hartung wrote:
> On Tue June 19 2007 17:11, [EMAIL PROTECTED] wrote:
> <snip>
>
> >... Can using different FS's in one system cause such problems?
>
> Theoretically, no, but in actual fact there are circumstances where
> conflicts *can* arise.
>
> In my case... with this specific chipset and corresponding kernel IDE
> controller module... cache buffering is enabled or disabled on a per drive
> basis. Running disparate filesystem types in adjacent partitions on the
> same drive (i.e. reiserfs + ext3) triggered errors comparable to those
> you're experiencing now.
>
> I ultimately coaxed those errors away permanently by standardizing my
> installations to using only one journaling filesystem type per drive.
>
> hth & regards,
>
> Carl
:-)
Al
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
