From: Carl Wilhelm Soderstrom <chrome@real-time.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dmitry Volkoff <vdb@mail.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fs corruption with 2.4.20 IDE+md+LVM
Date: Mon, 6 Jan 2003 10:21:04 -0600 [thread overview]
Message-ID: <20030106102103.A8123@real-time.com> (raw)
In-Reply-To: <1041865322.17472.13.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Mon, Jan 06, 2003 at 03:02:02PM +0000
On Mon, Jan 06, 2003 at 03:02:02PM +0000, Alan Cox wrote:
> You are reporting problems in 2.4.20. 2.4.20 doesn't have the revamped IDE...
I know. which is why I put that comment after the section of my mail
regarding md bugs in 2.4.21
> The IDE is getting updated because
>
> - Lots of new controllers dont work with the old code
> - Lots of LBA48 problems exist with the older code
> - SATA is right out with the older code
> - Several existing controllers have weird bugs with the older code
>
> I'd much prefer we didn't have to update the IDE too 8)
ok. I didn't see an extensive discussion of this on any of the kernel-digest
forums (kerneltrap, kernel traffic).
I'll trust that you're doing the right thing, and try to avoid stepping in
any other flamebait. ;)
Carl Soderstrom.
--
Systems Administrator
Real-Time Enterprises
www.real-time.com
next prev parent reply other threads:[~2003-01-06 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 2:14 fs corruption with 2.4.20 IDE+md+LVM Dmitry Volkoff
2003-01-06 4:49 ` Carl Wilhelm Soderstrom
2003-01-06 15:02 ` Alan Cox
2003-01-06 16:21 ` Carl Wilhelm Soderstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 4:45 Carl Wilhelm Soderstrom
2003-01-05 5:48 ` Carl Wilhelm Soderstrom
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=20030106102103.A8123@real-time.com \
--to=chrome@real-time.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vdb@mail.ru \
/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.