From: Mark Lord <liml@rtr.ca>
To: IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: hdparm-8.1 now available
Date: Sat, 16 Feb 2008 10:56:28 -0500 [thread overview]
Message-ID: <47B707AC.20305@rtr.ca> (raw)
hdparm has now been updated to version 8.1,
and includes some significant new features of
potential interest to Linux kernel storage hackers:
The new --make-bad-sector flag can be used to deliberately
corrupt a sector on the media (creating a media error situation).
This can be very handy for testing error recovery strategies
and timeouts for devices and RAIDs.
It uses the new ATA WRITE_UNC_EXT command (designed for the purpose)
when the drive supports it, otherwise it will try and fall back on
the older WRITE_LONG command (which is limited to LBA28).
The manpage has more information on this option.
There is also a new --write-sector (aka. --repair-sector) flag
to *fix* a bad sector. This can be used later to undo the bad
sectors created by the --make-bad-sector flag.
The new --read-sector flag can be used to test a sector
for media errors. I generally use the following sequence here:
hdparm --make-bad-sector nnnnnnnn /dev/sdb ## corrup a sector
hdparm --read-sector nnnnnnnn /dev/sdb ## verify that it is now bad
test my device driver etc..
hdparm --repair-sector nnnnnnn /dev/sdb ## fix the bad sector
hdparm --read-sector nnnnnnn /dev/sdb ## verify that it is now fixed
hdparm also now has a new -N flag for dealing with Host-Protected-Areas (HPA),
and other, more minor, fixes and enhancements.
hdparm-8.1 is available at http://sourceforge.net/projects/hdparm/
Thanks to Bruce Allen for supplying me with test drives
which implement the new WRITE_UNC_EXT command.
Cheers
Mark Lord
reply other threads:[~2008-02-16 15:56 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=47B707AC.20305@rtr.ca \
--to=liml@rtr.ca \
--cc=ballen@gravity.phys.uwm.edu \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).