From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Mudama, Eric" <eric_mudama@Maxtor.com>,
"'Hans Reiser '" <reiser@namesys.com>,
"'Wes Janzen '" <superchkn@sbcglobal.net>,
"'Rogier Wolff '" <R.E.Wolff@BitWizard.nl>,
"'John Bradford '" <john@grabjohn.com>,
<linux-kernel@vger.kernel.org>, <nikita@namesys.com>,
"'Justin Cormack '" <justin@street-vision.com>,
"'Vitaly Fertman '" <vitaly@namesys.com>,
"'Krzysztof Halasa '" <khc@pm.waw.pl>
Subject: Re: Blockbusting news, results end
Date: Sun, 26 Oct 2003 20:25:26 +0900 [thread overview]
Message-ID: <355901c39bb3$e6ca3a50$24ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20031026092256.GA293@elf.ucw.cz
Pavel Machek replied to me:
> > The drive finally reallocated the block and there are no longer any
> > visible bad blocks.
>
> And what was the operation that made it realocate?
At first I wasn't sure. I noticed that the drive was behaving differently
when I told dd to use bs=4096 instead of 512. Until seeing Oleg Drokin's
message about ReiserFS, I thought that the drive itself was doing something
differently. That didn't make much sense to me because the physical sectors
are much longer than 4096 and the pseudo-sectors are the conventional 512,
so why did 4096 cause different behaviour? From Oleg Drokin's message, I
guess that the use of 4096 might make a difference in the sequence of
read-modify-write cycles involved in the logical write operation.
This doesn't seem like a complete answer, but I don't think I'll ever know a
complete answer.
next prev parent reply other threads:[~2003-10-26 11:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 8:49 Blockbusting news, results end Norman Diamond
2003-10-26 9:22 ` Pavel Machek
2003-10-26 11:25 ` Norman Diamond [this message]
2003-10-27 20:58 ` jw schultz
2003-10-27 22:27 ` Andre Hedrick
2003-10-27 22:57 ` jw schultz
2003-10-28 2:03 ` jw schultz
2003-10-26 11:01 ` Hans Reiser
2003-10-26 12:59 ` Oleg Drokin
2003-10-26 12:05 ` Hans Reiser
2003-10-26 12:39 ` Oleg Drokin
2003-10-26 16:26 ` Hans Reiser
2003-10-26 17:13 ` Oleg Drokin
2003-10-26 18:20 ` Hans Reiser
2003-10-26 19:07 ` Oleg Drokin
2003-10-27 12:44 ` Vitaly Fertman
2003-10-26 18:39 Mudama, Eric
2003-10-27 9:45 ` Norman Diamond
2003-10-27 10:48 ` Krzysztof Halasa
2003-10-27 17:50 Mudama, Eric
2003-10-28 11:31 Norman Diamond
2003-10-28 16:10 Mudama, Eric
2003-10-28 18:30 ` bill davidsen
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='355901c39bb3$e6ca3a50$24ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@namesys.com \
--cc=pavel@ucw.cz \
--cc=reiser@namesys.com \
--cc=superchkn@sbcglobal.net \
--cc=vitaly@namesys.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;
as well as URLs for NNTP newsgroup(s).