From: "Jarmo Järvenpää" <Jarmo.Jarvenpaa@softers.net>
To: linux-kernel@vger.kernel.org
Subject: Ide problems
Date: Tue, 31 Dec 2002 10:32:45 +0200 [thread overview]
Message-ID: <3E11562D.421CAE73@softers.net> (raw)
Hi
I've been buggered with multiple lockups of an med/heavily loaded 2.4.19
(also rc-series) and same server with 2.4.20. Machine is running
normally for a week or two, then IDE light is lit and processes are
stuck in D state (if any disk activity is required -> freezed process).
I'm using (ide-) software raid 1 and 5, tested with raid 1 alone and
same lockup-problem appears.
So, IDE-light is continuously lit but the disks are not reading nor
writing. Emergency sync nor the unmount is working. I'm guessing the
IDE-code (eh, raid too) might be cause of this.
- No OOM situation have been observed, there's been lots of free ram at
the time of each lockup.
- Processes with no disk activity are not affected (for examples vmstat
1 runs ok if started before lockup)
Currently I'm thinking of falling back to .18 with hopes of no more
problems.
Any similar experiences?
Regards,
Jarmo
PS. An extremely useful feature would be a method to freeze raid resync
until fsck is finished. Now, when both are running at the same time
server's boot speed is miserable.
next reply other threads:[~2002-12-31 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 8:32 Jarmo Järvenpää [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 10:29 ide problems nigga
2002-04-16 23:20 IDE Problems Peter Nikolic
2002-04-16 23:56 ` Alan Cox
2002-04-17 0:09 ` Thunder from the hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E11562D.421CAE73@softers.net \
--to=jarmo.jarvenpaa@softers.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox