From: Andrew Morton <akpm@osdl.org>
To: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linuxraid@amcc.com, linux-scsi@vger.kernel.org
Subject: Re: 3Ware delayed device mounting errors with newer 9500 series adapters
Date: Sat, 21 Oct 2006 23:39:04 -0700 [thread overview]
Message-ID: <20061021233904.c2f40a5f.akpm@osdl.org> (raw)
In-Reply-To: <453A52CE.80605@wolfmountaingroup.com>
On Sat, 21 Oct 2006 11:03:10 -0600
"Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com> wrote:
>
> Adam,
>
> We have been getting 3Ware 9500 series adapters in the past 60 days
> which exhibit a delayed behavior during mounting of FS from
> /etc/fstab. The adapters older than this do not exhibit this behavior.
>
> During bootup, if the driver is compiled as a module rather than in
> kernel, mount points such as /var in fstab fail to detect the devices
> until the system fully boots, at which point the /dev/sdb etc. devices
> showup. It happens on both ATA cabled drives and drives
> cabled with multi-lane controller backplanes.
>
> The problem is easy to reproduce. Install ES4, point the /var directory
> during install to one of the array devices in disk druid, and after
> the install completes, /var/ will not mount during bootup and all sorts
> of errors stream off the screen. I can reproduce the problem
> with several systems in our labs and upon investigating the adapter
> revisions, I find that adapters ordered in the past 60 days exhibit
> the problem. Compiling the driver in kernel gets around the problem,
> indicating its timing related.
>
cc's added.
next prev parent reply other threads:[~2006-10-22 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 17:03 3Ware delayed device mounting errors with newer 9500 series adapters Jeffrey V. Merkey
2006-10-22 6:39 ` Andrew Morton [this message]
2006-10-22 17:19 ` adam radford
2006-10-22 20:19 ` Jeffrey V. Merkey
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=20061021233904.c2f40a5f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxraid@amcc.com \
/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