From: Chris Mason <chris.mason@oracle.com>
To: Kaspar Schleiser <kaspar@schleiser.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs and swap files on SSD's ?
Date: Tue, 20 Jan 2009 08:02:16 -0500 [thread overview]
Message-ID: <1232456536.15042.0.camel@think.oraclecorp.com> (raw)
In-Reply-To: <4975AA6C.8@schleiser.de>
On Tue, 2009-01-20 at 11:41 +0100, Kaspar Schleiser wrote:
> Hey Cris,
>
> Chris Mason wrote:
> > This doesn't quite play nicely with btrfs and should lead to all kinds
> > of problems....I'm looking into how to disable swapfiles completely.
> Please try to support swapfiles. I know their drawbacks and still use
> them quite often.
There are patches to support swap over NFS that might make it safe to
use on btrfs. At any rate, it is a fixable problem.
But today, swapfiles on btrfs will corrupt other file data.
-chris
next prev parent reply other threads:[~2009-01-20 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 0:10 btrfs and swap files on SSD's ? Chris Samuel
2009-01-19 16:22 ` Chris Mason
2009-01-20 10:41 ` Kaspar Schleiser
2009-01-20 13:02 ` Chris Mason [this message]
2009-01-20 13:51 ` Dmitri Nikulin
2009-01-20 14:31 ` Chris Mason
2009-01-20 16:35 ` Anthony Roberts
2009-01-20 16:41 ` Chris Mason
2009-01-21 6:15 ` Andi Kleen
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=1232456536.15042.0.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=kaspar@schleiser.de \
--cc=linux-btrfs@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