public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason@molenda.com>
To: overseers@sources.redhat.com
Subject: Re: hard disk fun == down time
Date: Mon, 31 Dec 2001 19:40:00 -0000	[thread overview]
Message-ID: <20010329210551.A8694@shell17.ba.best.com> (raw)
In-Reply-To: <20010329203236.A2834@shell17.ba.best.com>

On Thu, Mar 29, 2001 at 09:27:37PM -0500, Christopher Faylor wrote:

> The end result was that when I wrote to /dev/hda4, I was also randomly
> writing to /dev/hda3.

I was just talking with Marc Rovner on the phone and mentioned the
problem.  He suggested that some old BIOSes had kooky confusion
about larger hard drives, and if Linux didn't know that the BIOS
might report incorrect information, hilarity could ensue.  Marc
said the trick was to specify explicitly the size of the drive
(cylinders, sectors, etc.) in Linux and everything would be OK.

FWIW.

Jason

WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason@molenda.com>
To: overseers@sources.redhat.com
Subject: Re: hard disk fun == down time
Date: Thu, 29 Mar 2001 21:06:00 -0000	[thread overview]
Message-ID: <20010329210551.A8694@shell17.ba.best.com> (raw)
Message-ID: <20010329210600.fcDezpW_eu-OMj6YYD3OMennu3JQdBiow7LhsTVqLEs@z> (raw)
In-Reply-To: <20010329203236.A2834@shell17.ba.best.com>

On Thu, Mar 29, 2001 at 09:27:37PM -0500, Christopher Faylor wrote:

> The end result was that when I wrote to /dev/hda4, I was also randomly
> writing to /dev/hda3.

I was just talking with Marc Rovner on the phone and mentioned the
problem.  He suggested that some old BIOSes had kooky confusion
about larger hard drives, and if Linux didn't know that the BIOS
might report incorrect information, hilarity could ensue.  Marc
said the trick was to specify explicitly the size of the drive
(cylinders, sectors, etc.) in Linux and everything would be OK.

FWIW.

Jason

  parent reply	other threads:[~2001-12-31 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31 19:40 Christopher Faylor
2001-03-29 18:31 ` Christopher Faylor
2001-12-31 19:40 ` Jason Molenda
2001-03-29 20:34   ` Jason Molenda
2001-12-31 19:40   ` Christopher Faylor
2001-03-29 20:56     ` Christopher Faylor
2001-12-31 19:40   ` law
2001-04-01 20:46     ` law
2001-12-31 19:40   ` Jason Molenda [this message]
2001-03-29 21:06     ` Jason Molenda
2001-12-31 19:40     ` Christopher Faylor
2001-03-29 22:14       ` Christopher Faylor

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=20010329210551.A8694@shell17.ba.best.com \
    --to=jason@molenda.com \
    --cc=overseers@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).