From: Carl Wilhelm Soderstrom <chrome@real-time.com>
To: linux-kernel@vger.kernel.org
Subject: Re: fs corruption with 2.4.20 IDE+md+LVM
Date: Sat, 4 Jan 2003 23:48:19 -0600 [thread overview]
Message-ID: <20030104234814.B18611@real-time.com> (raw)
In-Reply-To: <20030104224455.A18362@real-time.com>; from chrome@real-time.com on Sat, Jan 04, 2003 at 10:45:00PM -0600
On Sat, Jan 04, 2003 at 10:45:00PM -0600, Carl Wilhelm Soderstrom wrote:
> I observed filesystem corruption on my home workstation recently. I was
> running kernel 2.4.20 (built myself with gcc 2.95.4), and ext3 with the
> default journaling mode (ordered?).
I should probably include some details about my IDE devices.
here's the controller for the devices in question. it's the second
controller on the mobo. (first controller is only ATA-66)
00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev
02)
Subsystem: Promise Technology, Inc. Ultra100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at 9400 [size=8]
Region 1: I/O ports at 9000 [size=4]
Region 2: I/O ports at 8800 [size=8]
Region 3: I/O ports at 8400 [size=4]
Region 4: I/O ports at 8000 [size=64]
Region 5: Memory at de800000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: <available only to root>
and here's the output of hdparm. (yes, I know it could probably get tweaked
a bit for performance. this is a brand-new drive arrangement, and I was
trying to run it in a 'safe' setting for a while to see if anything would go
wrong. well, it did).
~# hdparm /dev/hde
/dev/hde:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 155061/16/63, sectors = 156301488, start = 0
~# hdparm /dev/hdf
/dev/hdf:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 155061/16/63, sectors = 156301488, start = 0
Carl Soderstrom.
--
Systems Administrator
Real-Time Enterprises
www.real-time.com
next prev parent reply other threads:[~2003-01-05 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 4:45 fs corruption with 2.4.20 IDE+md+LVM Carl Wilhelm Soderstrom
2003-01-05 5:48 ` Carl Wilhelm Soderstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 2:14 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
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=20030104234814.B18611@real-time.com \
--to=chrome@real-time.com \
--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.