From: Florian Weimer <fw@deneb.enyo.de>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: adam radford <aradford@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Subject: Re: 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables
Date: Mon, 07 Nov 2005 22:53:54 +0100 [thread overview]
Message-ID: <87br0wxgy5.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <98C5049497A78ECC77D350B7@[192.168.100.25]> (Alex Bligh's message of "Sat, 05 Nov 2005 09:06:08 +0000")
* Alex Bligh:
> I /think/ what had happened is this: When I press F8 to exit the
> BIOS, it did not initialize the array (this is in accordance with the
> manual, it being deferred). Despite leaving the machine idle in the O/S
> for 2 days, it didn't start initializing the array. Running the mkfs
> started the initialization (would that make sense)? The second time
> I ran mkfs, I may have already (somehow) triggered it to start earlier.
>
> I shall try and work out some soak test I can run on it this w/e.
Please check the write cache settings and report the results.
(There's a closed-source command line utility which can report the
status in an unambiguous way.)
If the system doesn't wait on I/O, this means that all I/O is cached
by the controller, which in turn suggests that the write cache is
turned on (with obvious consequences).
next prev parent reply other threads:[~2005-11-07 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BEDEA151E8B1D6CEDD295442@192.168.100.25>
2005-11-02 22:59 ` 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables adam radford
2005-11-05 9:06 ` Alex Bligh - linux-kernel
2005-11-05 17:01 ` Jeff V. Merkey
2005-11-07 21:53 ` Florian Weimer [this message]
2005-10-30 21:10 Alex Bligh - linux-kernel
2005-11-01 12:45 ` Florian Weimer
2005-11-01 17:04 ` Lawrence Walton
2005-11-01 17:13 ` Florian Weimer
2005-11-02 0:11 ` Alex Bligh - linux-kernel
2005-11-01 22:54 ` Jeff V. Merkey
2005-11-02 22:39 ` Alex Bligh - linux-kernel
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=87br0wxgy5.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=aradford@gmail.com \
--cc=linux-kernel@alex.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.