From: Andrew Morton <akpm@digeo.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
"Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [announce] swap mini-howto
Date: Sat, 02 Nov 2002 02:02:21 -0800 [thread overview]
Message-ID: <3DC3A2AD.69775F06@digeo.com> (raw)
In-Reply-To: 3DC38C43.6020103@pobox.com
Jeff Garzik wrote:
>
> ...
> That said, I would like to again point out that using sparse swapfiles
> should still be discouraged. It may be supported, but it's much better
> for system performance and stability, IMO, if the sysadmin makes certain
> all swapfiles are 100% allocated before they are mentioned to the swap
> subsystem.
>
That got stamped out. swapon will fail if the file isn't fully
instantiated on disk:
static int setup_swap_extents(struct swap_info_struct *sis)
{
...
block = bmap(inode, probe_block + block_in_page);
if (block == 0)
goto bad_bmap;
...
bad_bmap:
printk(KERN_ERR "swapon: swapfile has holes\n");
ret = -EINVAL;
}
next prev parent reply other threads:[~2002-11-02 9:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 23:58 [announce] swap mini-howto Randy.Dunlap
2002-11-02 0:09 ` Dave Jones
2002-11-02 0:07 ` Randy.Dunlap
2002-11-02 0:46 ` Andrew Morton
2002-11-02 8:26 ` Jeff Garzik
2002-11-02 10:02 ` Andrew Morton [this message]
2002-11-02 23:31 ` Jeff Garzik
2002-11-02 11:22 ` Troels Walsted Hansen
2002-11-04 10:47 ` Richard Russon
2002-11-02 16:55 ` Pavel Machek
2002-11-02 21:23 ` Rik van Riel
2002-11-02 21:28 ` Pavel Machek
2002-11-02 0:19 ` Andries Brouwer
2002-11-02 0:25 ` Randy.Dunlap
2002-11-02 11:19 ` Andries Brouwer
2002-11-05 5:54 ` [announce] swap mini-howto (updated) Randy.Dunlap
2002-11-02 1:01 ` [announce] swap mini-howto Nicolas Pitre
2002-11-02 1:23 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 10:56 Gabor MICSKO
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=3DC3A2AD.69775F06@digeo.com \
--to=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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