Date: Fri, 19 Jan 2018 08:55:27 -0600 From: Tim Daneliuk <tundra@tundraware.com> To: "Steve O'Hara-Smith" <steve@sohara.org> Cc: freebsd-questions@freebsd.org Subject: Re: gpart And VPS Disk: Disappearing swap Partition Message-ID: <b43abfb0-61a5-c57f-6f2d-14aa2cb1a784@tundraware.com> In-Reply-To: <20180119075943.aa44341ba798fb1b6c096670@sohara.org> References: <511934e8-cbcb-75e2-b4ac-ea06e1a54196@tundraware.com> <20180118213913.b39616554429136e897334fa@sohara.org> <06ff73a3-1c73-3309-985f-297b7dbfa1df@tundraware.com> <20180119075943.aa44341ba798fb1b6c096670@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/19/2018 01:59 AM, Steve O'Hara-Smith wrote: > Try adding -l swap1 to that command viz: > > gpart add -t freebsd-swap -l swap1 -i4 vtbd0 > > That *should* cause a /dev/gpt/swap1 to appear and persist through > reboots. It does cause the label to appear under /dev/gpt, but as before, it disappears on reboot. > >> gpart modify -i4 -lswapfs2 vtbd0 >> >> At this point, I can see the new swap partition. However, when I reboot, >> it's no longer there. > Hmm - does vtbd0 exist at all after reboot ? Yes, the raw drive and all the partition entries are there. This is very strange. From the OS' point of view, this is just another hard drive. The reason this came up at all is because I got a larger drive assigned to the virtual instance. I was able to successfully resize the root ufs volume. But when I then tried to use the last 1G of the drive for additional swap, I ran into the problems thus described... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b43abfb0-61a5-c57f-6f2d-14aa2cb1a784>