From: Andries Brouwer <aebr@win.tue.nl>
To: Daniel Cavanagh <nofsk@vtown.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux kernel problem (disklabel and swap)
Date: Sun, 6 Jul 2003 12:48:46 +0200 [thread overview]
Message-ID: <20030706104846.GA17191@win.tue.nl> (raw)
In-Reply-To: <3F07B957.4010206@vtown.com.au>
On Sun, Jul 06, 2003 at 03:53:27PM +1000, Daniel Cavanagh wrote:
> i recently had the problem with a bsd disklabel and swap and as someone
> suggested, the swap slice did not have SWAPSPACE in it and that running
> mkswap would fix this. sure enough it did, but then i wondered why
> swapon allowed /dev/hda3 as a valid swap. so i had a look and SWAPSPACE2
> was there, right at the start of the openbsd partition, inside the
> disklabel. so i have come to the conclusion that openbsd tells the world
> via the disklabel that a partition/slice is swap rather than at the
> start of the swap slice.
I don't know about openbsd, but this sounds rather unlikely.
More likely is that you (or some installation script run by you)
marked that partition as swapspace.
mkswap for SWAPSPACE2 will preserve the first 1024 bytes, so it is possible
that you did this mkswap without destroying the disklabel.
Note that partition numbering is a black art, especially when you mix
several types of partition table. The name (number) of your partition
may depend on kernel version and on for what partition table types you
have support in your kernel.
prev parent reply other threads:[~2003-07-06 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 5:53 linux kernel problem (disklabel and swap) Daniel Cavanagh
2003-07-06 10:48 ` Andries Brouwer [this message]
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=20030706104846.GA17191@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nofsk@vtown.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.