From: Phillip Susi <psusi@ubuntu.com>
To: Roger Heflin <rogerheflin@gmail.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Phil Turmel <philip@turmel.org>, Wolfgang Denk <wd@denx.de>,
Roman Mamedov <rm@romanrm.net>,
"linux-raid@vger.kernel.org List" <linux-raid@vger.kernel.org>
Subject: Re: writing zeros to bad sector results in persistent read error
Date: Wed, 08 Oct 2014 13:51:33 -0400 [thread overview]
Message-ID: <543579A5.6020504@ubuntu.com> (raw)
In-Reply-To: <CAAMCDef3tO4Ah_3gYJ_6Y0Kh_mPn+z=E5voHFYr-z7_Leuf48Q@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/29/2014 8:51 PM, Roger Heflin wrote:
> All of this is probably the reason that this command exists:
>
> hdparm --write-sector <sectornum>
>
> I believe it directly sends the scsi/ata layer commands.
You end up with the same results as using dd ( with oflag=direct ), it
is just a matter of the path it takes to get there.
With dd, it calls write() to pass the data to the block layer, which
hands it to the scsi layer, which translates it into a scsi
WRITE_10/16 command, which hands it to libata which translates it into
an ata taskfile to be handed to the drive.
With hdparm --write-sector, it builds the ata taskfile, uses the SG_IO
ioctl to hand it to the block layer, which hands it down through the
scsi and libata layers which see that it needs no translation and it
goes to the drive unmodified.
The resulting taskfile the drive actually sees should be the same.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJUNXmlAAoJEI5FoCIzSKrwMYwIAJj1c0pBxdOcCQAk4i26802S
/lbPHhY5Xu7wR5KbZSXeEazE/vgTT7mDgjWHoe6Vl9e+Ci90KJxSFgQXNNwcYtuK
V+UFrTyqiKAzfk8VbRj0kwxk1JuXRQesDlwCGUsBkjSO26pdhUVfxwP8I3JcOBQW
uKRmh8PE48iq7kDWQdtxve6IPnAj/VY8AubwRAaVAvZ3xsEUBlf7UAkvA4n3WvWN
mfO1VVWwv4zyZ6bEBoWfjj6//5C0R+q2TrnBDFD9pN/wY4TdAx0gtufiUWx0v5WG
NNzJ9tm5z2rNo/HNi4w1gHm0JLDhSky21sNX7KyY8/1tFjqa3KQT7iQ6vxk4UJM=
=Xv01
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-10-08 17:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 0:11 writing zeros to bad sector results in persistent read error Chris Murphy
2014-06-07 1:26 ` Roger Heflin
2014-06-07 1:51 ` Roman Mamedov
2014-06-07 16:42 ` Chris Murphy
2014-06-07 18:26 ` Chris Murphy
2014-06-08 0:52 ` Chris Murphy
2014-06-08 1:50 ` Roger Heflin
2014-06-08 21:50 ` Chris Murphy
2014-06-08 8:10 ` Wilson Jonathan
2014-06-10 0:09 ` Chris Murphy
2014-06-10 6:52 ` Wilson Jonathan
2014-10-08 17:56 ` Phillip Susi
2014-06-09 19:37 ` Wolfgang Denk
2014-06-10 2:48 ` Chris Murphy
2014-06-10 13:40 ` Phil Turmel
2014-06-29 0:05 ` Chris Murphy
2014-06-29 23:50 ` Martin K. Petersen
2014-06-30 0:51 ` Roger Heflin
2014-10-08 17:51 ` Phillip Susi [this message]
2014-06-10 22:18 ` Eyal Lebedinsky
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=543579A5.6020504@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=martin.petersen@oracle.com \
--cc=philip@turmel.org \
--cc=rm@romanrm.net \
--cc=rogerheflin@gmail.com \
--cc=wd@denx.de \
/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.