public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Dave Jones <davej@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: /proc/partitions broken in 2.5.23
Date: Wed, 19 Jun 2002 14:51:54 +0200	[thread overview]
Message-ID: <20020619125154.GA15739@win.tue.nl> (raw)
In-Reply-To: <20020619134402.B29373@suse.de>

On Wed, Jun 19, 2002 at 01:44:02PM +0200, Dave Jones wrote:

> hda2 is odd looking too showing a #blocks of '1', when
> it's actually..
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hda2           234     58168  29199240    5  Extended 

That is correct, and something I did before you were born.

An extended partition is a box containing logical partitions.
It is almost always an error when people want to write directly to it
(confusing the extended partition with some logical partition inside).
After a number of reports of people who messed up their disk
by doing mkswap or mkfs on an extended partition I changed
the length of an extended partition to 1 block, enough for LILO
but stopping mkswap and mkfs.
People who really want to access these blocks, like e.g. fdisk,
can do so via /dev/hda.

Andries


  reply	other threads:[~2002-06-19 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19  9:02 /proc/partitions broken in 2.5.23 Dave Jones
2002-06-19 11:32 ` Andries Brouwer
2002-06-19 11:44   ` Dave Jones
2002-06-19 12:51     ` Andries Brouwer [this message]
2002-06-19 13:16       ` Dave Jones
2002-06-19 17:18   ` Wayne Whitney
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 23:21 Andries.Brouwer
2002-06-20 23:34 ` Dave Jones
2002-06-20 23:42 ` Anders Gustafsson
     [not found] <641481775@toto.iv>
2002-06-26  3:22 ` Peter Chubb

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=20020619125154.GA15739@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=davej@suse.de \
    --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