<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Adding a simple progress bar to dd</title>
	<atom:link href="http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/</link>
	<description>Musings of a geek, jazz performer, and an OSUOSL sysadmin</description>
	<lastBuildDate>Tue, 24 May 2011 16:15:58 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Eli</title>
		<link>http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/comment-page-1/#comment-127</link>
		<dc:creator>Eli</dc:creator>
		<pubDate>Tue, 23 Nov 2010 19:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://test.lancealbertson.com/?p=93#comment-127</guid>
		<description>@KK

I think what you mean is to do is (as root):

dd if=/dev/zero of=/dev/sd(x) bs=512 count=1

where sd(x) is your hard drive, bs is the the block size, and count is the number of times the block is written to disk.

The command above writes a 512 byte block of zeros to the beginning of your drive, destroying the Master Boot Record (mbr is always the first 512 bytes on a drive). This effectively blanks the drive albiet in a non-secure manner (ie the most data on the drive will be retiervable).

DD&#039;ing the buffer or cache of a drive will only clear data used by a drives &quot;read-ahead&quot; feature, which it uses cached data from your disk for performance reasons.  If DD&#039;ing your drive buffer/cache blanked your drive, the the following command would not be safe to use to gauge disk performance, as it flushes the disk buffer/cache:

hdparm -tT /dev/sd(x).

I&#039;m not sure it&#039;s even possible to write bits to the drive cache/buffer via the DD command.</description>
		<content:encoded><![CDATA[<p>@KK</p>
<p>I think what you mean is to do is (as root):</p>
<p>dd if=/dev/zero of=/dev/sd(x) bs=512 count=1</p>
<p>where sd(x) is your hard drive, bs is the the block size, and count is the number of times the block is written to disk.</p>
<p>The command above writes a 512 byte block of zeros to the beginning of your drive, destroying the Master Boot Record (mbr is always the first 512 bytes on a drive). This effectively blanks the drive albiet in a non-secure manner (ie the most data on the drive will be retiervable).</p>
<p>DD&#8217;ing the buffer or cache of a drive will only clear data used by a drives &#8220;read-ahead&#8221; feature, which it uses cached data from your disk for performance reasons.  If DD&#8217;ing your drive buffer/cache blanked your drive, the the following command would not be safe to use to gauge disk performance, as it flushes the disk buffer/cache:</p>
<p>hdparm -tT /dev/sd(x).</p>
<p>I&#8217;m not sure it&#8217;s even possible to write bits to the drive cache/buffer via the DD command.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud</title>
		<link>http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/comment-page-1/#comment-96</link>
		<dc:creator>Bud</dc:creator>
		<pubDate>Mon, 17 May 2010 19:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://test.lancealbertson.com/?p=93#comment-96</guid>
		<description>You can also use pv (Pipe Viewer)[1] to do this kind of stuff.

[1] http://packages.gentoo.org/package/sys-apps/pv</description>
		<content:encoded><![CDATA[<p>You can also use pv (Pipe Viewer)[1] to do this kind of stuff.</p>
<p>[1] <a href="http://packages.gentoo.org/package/sys-apps/pv" rel="nofollow">http://packages.gentoo.org/package/sys-apps/pv</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Techie Talks</title>
		<link>http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/comment-page-1/#comment-92</link>
		<dc:creator>Techie Talks</dc:creator>
		<pubDate>Sat, 19 Dec 2009 14:55:39 +0000</pubDate>
		<guid isPermaLink="false">http://test.lancealbertson.com/?p=93#comment-92</guid>
		<description>Cool progress bar.  It&#039;s so simple and I love the effect its like having linux online.</description>
		<content:encoded><![CDATA[<p>Cool progress bar.  It&#8217;s so simple and I love the effect its like having linux online.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kk</title>
		<link>http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/comment-page-1/#comment-91</link>
		<dc:creator>kk</dc:creator>
		<pubDate>Sat, 05 Dec 2009 10:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://test.lancealbertson.com/?p=93#comment-91</guid>
		<description>Just a tip about zeroing drives with dd :
use bs=&quot;buffer size ofthe driver&quot; for the speedy erase.
You can try several dd, letting it go about 2 min then ctrl-c
and compare the output. So:
dd if=/dev/null of=/dev/&quot;sdX&quot; bs=&quot;buffer size of the harddisk&quot;

you can see the buffer size with hdparm -i /dev/&quot;sdX&quot;

sdX here is the drivename you have to substitte can be sda sdb ...

BE CAREFUL!!!</description>
		<content:encoded><![CDATA[<p>Just a tip about zeroing drives with dd :<br />
use bs=&#8221;buffer size ofthe driver&#8221; for the speedy erase.<br />
You can try several dd, letting it go about 2 min then ctrl-c<br />
and compare the output. So:<br />
dd if=/dev/null of=/dev/&#8221;sdX&#8221; bs=&#8221;buffer size of the harddisk&#8221;</p>
<p>you can see the buffer size with hdparm -i /dev/&#8221;sdX&#8221;</p>
<p>sdX here is the drivename you have to substitte can be sda sdb &#8230;</p>
<p>BE CAREFUL!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hal Pomeranz</title>
		<link>http://www.lancealbertson.com/2009/04/adding-a-simple-progress-bar-to-dd/comment-page-1/#comment-88</link>
		<dc:creator>Hal Pomeranz</dc:creator>
		<pubDate>Thu, 21 May 2009 03:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://test.lancealbertson.com/?p=93#comment-88</guid>
		<description>There&#039;s also dcfldd, which includes progress-bar functionality built-in (albeit a ASCII art progress bar).

It might be interesting running some timing tests to see how much overhead is involved in displaying the progress bar via these various methods as opposed to just doing the dd without any status updates.</description>
		<content:encoded><![CDATA[<p>There&#8217;s also dcfldd, which includes progress-bar functionality built-in (albeit a ASCII art progress bar).</p>
<p>It might be interesting running some timing tests to see how much overhead is involved in displaying the progress bar via these various methods as opposed to just doing the dd without any status updates.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

