Message-ID: <3F07B957.4010206@vtown.com.au>
Date: Sun, 06 Jul 2003 15:53:27 +1000
From: Daniel Cavanagh <nofsk@vtown.com.au>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3) Gecko/20030313
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: linux kernel problem (disklabel and swap)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1232
Lines: 26

hi

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. the linux kernel does not know this and wants 
SWAPSPACE2 at the start of the partition/slice. to test this i booted up 
openbsd and forced it to swap. it wrote over the SWAPSPACE2 in the 
slice. so i think that the linux kernel needs to be fix so that if an 
openbsd partition exists, the kernel expects SWAPSPACE2 in the disklabel 
rather than the actual swap slice. i don't know if this is true for 
other *BSD though.

i hope this helps.

thanks, daniel.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/