From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6.0-test3] file system corruption (related to atime update?)
Date: Mon, 11 Aug 2003 09:24:35 +0200 [thread overview]
Message-ID: <877k5k1wss.fsf@deneb.enyo.de> (raw)
The file system corruption I observed late in the 2.5.x series is
still not gone. File system modes are suddenly wrong, and a fsck run
removes the files. 8-/ This happens with ext2 (and previously with
ext3).
The strange thing is that these files are only read, not written to,
so it probably has to do with atime updates.
Hardware is a Siemens Primergy H450, with the following SCSI
controller (2.4.x output, as I had to downgrade again). The machine
runs a software RAID 5 across all six disks.
SCSI subsystem driver Revision: 1.00
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
<Adaptec aic7899 Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
<Adaptec aic7899 Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
blk: queue c3f87c18, I/O limit 4095Mb (mask 0xffffffff)
Vendor: FUJITSU Model: MAN3367MC Rev: 5207
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c3f87a18, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: FUJITSU Model: MAP3367NC Rev: 5205
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c3f87218, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: FUJITSU Model: MAP3367NC Rev: 5205
Type: Direct-Access ANSI SCSI revision: 03
blk: queue f7aaf818, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:4): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: SDR Model: GEM318 Rev: 0
Type: Processor ANSI SCSI revision: 02
blk: queue f7aaaa18, I/O limit 4095Mb (mask 0xffffffff)
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
scsi0:A:2:0: Tagged Queuing enabled. Depth 253
scsi0:A:4:0: Tagged Queuing enabled. Depth 253
Vendor: FUJITSU Model: MAN3367MC Rev: 5207
Type: Direct-Access ANSI SCSI revision: 03
blk: queue f7aa4818, I/O limit 4095Mb (mask 0xffffffff)
(scsi1:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: FUJITSU Model: MAP3367NC Rev: 5205
Type: Direct-Access ANSI SCSI revision: 03
blk: queue f7a9ee18, I/O limit 4095Mb (mask 0xffffffff)
(scsi1:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: FUJITSU Model: MAP3367NC Rev: 5205
Type: Direct-Access ANSI SCSI revision: 03
blk: queue f7a9e418, I/O limit 4095Mb (mask 0xffffffff)
(scsi1:A:4): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: SDR Model: GEM318 Rev: 0
Type: Processor ANSI SCSI revision: 02
blk: queue f7a94618, I/O limit 4095Mb (mask 0xffffffff)
scsi1:A:0:0: Tagged Queuing enabled. Depth 253
scsi1:A:2:0: Tagged Queuing enabled. Depth 253
scsi1:A:4:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 4, lun 0
Attached scsi disk sdd at scsi1, channel 0, id 0, lun 0
Attached scsi disk sde at scsi1, channel 0, id 2, lun 0
Attached scsi disk sdf at scsi1, channel 0, id 4, lun 0
SCSI device sda: 71771688 512-byte hdwr sectors (36747 MB)
reply other threads:[~2003-08-11 7:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877k5k1wss.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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