<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Bryan J. Smith wrote:
<blockquote
cite="mid1136985909.4729.20.camel@bert64.oviedo.smithconcepts.com"
type="cite">
<pre wrap="">On Wed, 2006-01-11 at 00:45 -0600, William A. Mahaffey III wrote:
</pre>
<blockquote type="cite">
<pre wrap="">As hazy recollections are revisited, I am almost certain that I did
the 160 GB (about 2 years ago) w/o fdisk or equivalent (I expected
mkreiserfs to fail if there were problems ....). I redressed that this
time. I setup the 400 GB drive as ext3, after fsidk-ing it into 1
large partition. I then moved everything off of the 160 GB & re-did it
(fdisk/mkreiserfs, rather than just mkreiserfs) & moved everything
back. We'll see about reliability, stay tuned :-) ....
</pre>
</blockquote>
<pre wrap=""><!---->
In Linux, you can probably get away with that. All you get is an extra
cylinder 0 (~8MB for 63/255 sectors/heads) in capacity that is normally
used for the Legacy BIOS/DOS disk label (partition table), master boot
record (MBR), etc...
</pre>
</blockquote>
<br>
I apparently *did* sorta get away with it, for a while, until I started
using the 160 GB drive more heavily doing X-LAN backups, then the
reliability issues cropped up. I am now doing those backups onto the
400 GB drive (ext3, more space), so we'll see. So far, so good w/ the
new setup ....<br>
<br>
<pre class="moz-signature" cols="72">--
William A. Mahaffey III
----------------------------------------------------------------------
"The M1 Garand is without doubt the finest implement of war
ever devised by man."
-- Gen. George S. Patton
</pre>
</body>
</html>