From: Raymond Jennings <shentino@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [problem?] swapon: swap partition/volume size capped at 32G?
Date: Thu, 04 Jul 2013 11:15:10 -0700 [thread overview]
Message-ID: <1372961710.16288.1.camel@warfang> (raw)
In-Reply-To: <1372886473.1079.3.camel@warfang>
On Wed, 2013-07-03 at 14:21 -0700, Raymond Jennings wrote:
> Ok, so I just upgraded to 3.10.0 (gentoo system) and made a nice big
> 64GiB swap volume on lvm as usual.
>
> Suddenly, swapon doesn't recognize more than 32GiB, as top lists only
> that much swap space.
>
> swapon using *two* separate 32GiB partitions works fine, but for some
> reason a swap partition bigger than 32GiB isn't fully recognized.
>
> Previous kernel versions IIRC recognized the entire swap partition.
>
> Is something wrong or is this new behavior standard?
>
Hold on a minute, I just found out something ate my kernel config and
turned off PAE when I upgraded.
This in turn shrunk my pte's from 64 bits to 32 bits and is probably
what killed >32G swap extents.
prev parent reply other threads:[~2013-07-04 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 21:21 [problem?] swapon: swap partition/volume size capped at 32G? Raymond Jennings
2013-07-04 18:15 ` Raymond Jennings [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=1372961710.16288.1.camel@warfang \
--to=shentino@gmail.com \
--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