From: Pat LaVarre <p.lavarre@ieee.org>
To: bfennema@falcon.csc.calpoly.edu
Cc: linux-fsdevel@vger.kernel.org, linux_udf@hpesjro.fc.hp.com
Subject: Re: zeroes read back more often than appended
Date: 08 Oct 2003 10:41:30 -0600 [thread overview]
Message-ID: <1065631289.6625.34.camel@patehci2> (raw)
In-Reply-To: <20031007204951.A25423@falcon.csc.calpoly.edu>
> From: Ben Fennema
>
> I'll see if I can figure out
> whats going on in 2.6.0-test6-smp.
>
> Somehow unrecorded block(s) are getting
> inserted in the data.
Intriguing, thank you. Two questions immediately occur to me:
1) Do you mean to say you already have seen 2.6.0-test6-smp fail?
I ask because, if you say yes, then I should stop investing more time
into finding a second pc where I can reproduce my observations.
2) Do you mean to say you have seen the metadata of a failure, and you
saw that metadata say some of the data was allocated but not written?
I suspect yes because I know with a real device I saw all the write data
reach the disk. In a soft trace of usb cdb's, I saw that reading the
file back skipped over part of the disk.
With a real device I tried a pattern more complex than the byte xAA
repeated. My more complex pattern let me see that that the data
supposedly not written had been written to the disk. Only the read back
skipped over that portion of the disk.
If that theory holds true, then we will fix only metadata, not data.
> > > ... 2.6.0-test6 ...
> > > CPU0: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
> > > CPU1: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
> > ... read more zeroes than appended ...
>
> > ... 2.4.22-xfs ...
> > ... 866.394 MHz ... CPU0: Intel Pentium III ...
> > correct '\xAA' read back, no troublesome zeroes, ...
>
> can't repeat ... 2.4 or 2.6.0-test6 non-smp ...
>
> whats going on in 2.6.0-test6-smp ...
I also saw correct '\xAA' read back, no troublesome zeroes, in Red Hat
2.6.0-test3 on a (fifth?) pc, in 20..30 s/test, with a loop on ext3:
318MB LOWMEM available.
Detected 697.733 MHz processor.
CPU0: Intel Celeron (Coppermine) stepping 06
..... CPU clock speed is 697.0620 MHz.
..... host bus clock speed is 66.0440 MHz.
Pat LaVarre
next prev parent reply other threads:[~2003-10-08 16:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 19:02 zeroes read back more often than appended Pat LaVarre
2003-10-07 20:54 ` Pat LaVarre
2003-10-08 3:49 ` Ben Fennema
2003-10-08 16:41 ` Pat LaVarre [this message]
2003-10-08 16:47 ` editable udf metadata Pat LaVarre
2003-10-08 17:51 ` Pat LaVarre
2003-10-08 18:09 ` big-endian udfct_1_0r2 Pat LaVarre
2003-10-08 18:30 ` Matthew Wilcox
[not found] ` <3F8472FE.9040403@lougher.demon.co.uk>
2003-10-08 19:49 ` Matthew Wilcox
2003-10-08 20:43 ` Phillip Lougher
2003-10-21 21:54 ` editable udf metadata Pat LaVarre
2003-10-21 23:17 ` Pat LaVarre
2003-10-23 16:06 ` Pat LaVarre
2003-10-24 21:40 ` Pat LaVarre
2003-10-22 8:15 ` same page access Mark B
2003-10-22 11:21 ` Matthew Wilcox
2003-10-22 17:09 ` Mark B
2003-10-22 17:10 ` Matthew Wilcox
2003-10-08 17:02 ` zeroes read back more often than appended Pat LaVarre
2003-10-08 17:06 ` toggling smp clears x86_mce_p4thermal of make xconfig Pat LaVarre
2003-10-08 17:21 ` zeroes read back more often than appended Pat LaVarre
2003-10-08 16:46 ` soft trace of read/write of drivers/block/loop.c Pat LaVarre
2003-10-08 20:32 ` zeroes read back more often than appended Pat LaVarre
2003-10-09 20:54 ` Pat LaVarre
2003-10-10 0:52 ` Pat LaVarre
2003-10-10 16:39 ` Pat LaVarre
2003-10-10 18:15 ` Pat LaVarre
2003-10-14 0:38 ` Pat LaVarre
2003-10-14 1:48 ` Pat LaVarre
2003-10-20 23:20 ` Pat LaVarre
2003-10-21 14:47 ` Pat LaVarre
2003-10-21 16:46 ` Pat LaVarre
2003-10-21 18:44 ` Pat LaVarre
2003-10-23 18:52 ` Pat LaVarre
2003-10-27 21:55 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 16:41 Pat LaVarre
2003-11-27 0:45 ` Pat LaVarre
2003-11-28 18:20 ` Pat LaVarre
2003-11-28 18:29 ` Pat LaVarre
2003-12-11 18:42 Pat LaVarre
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=1065631289.6625.34.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux_udf@hpesjro.fc.hp.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