From: "Stephen C. Tweedie" <sct@redhat.com>
To: Mike Black <mblack@csihq.com>
Cc: Andreas Dilger <adilger@turbolinux.com>,
"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>,
Ext2 development mailing list <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: 2.4.6 and ext3-2.4-0.9.1-246
Date: Tue, 10 Jul 2001 19:17:19 +0100 [thread overview]
Message-ID: <20010710191719.B1493@redhat.com> (raw)
In-Reply-To: <200107101752.f6AHqXUu022141@webber.adilger.int> <018101c1096a$17e2afc0$b6562341@cfl.rr.com>
In-Reply-To: <018101c1096a$17e2afc0$b6562341@cfl.rr.com>; from mblack@csihq.com on Tue, Jul 10, 2001 at 01:59:40PM -0400
Hi,
On Tue, Jul 10, 2001 at 01:59:40PM -0400, Mike Black wrote:
> Yep -- I said __files__ -- I'm less concerned about performance than
> reliability -- I don't think you can RAID1 a swap partition can you?
You can on 2.4. 2.2 would let you do it but it was unsafe --- swap
could interact badly with raid reconstruction. 2.4 should be OK.
> Also,
> having it in files allows me to easily add more swap as needed.
> As far as journalling mode I just used tune2fs to put a journal on with
> default parameters so I assume that's full journaling.
The swap code bypasses filesystem writes: all it does is to ask the
filesystem where on disk the data resides, then it performs IO
straight to those disk blocks. The data journaling mode doesn't
really matter there.
Cheers,
Stephen
next prev parent reply other threads:[~2001-07-10 18:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 9:47 2.4.6 and ext3-2.4-0.9.1-246 Mike Black
2001-07-10 17:52 ` Andreas Dilger
[not found] ` <018101c1096a$17e2afc0$b6562341@cfl.rr.com>
2001-07-10 18:17 ` Stephen C. Tweedie [this message]
2001-07-10 18:27 ` [Ext2-devel] " Mike Black
2001-07-10 18:29 ` Stephen C. Tweedie
2001-07-10 18:51 ` Andreas Dilger
2001-07-11 4:08 ` Andrew Morton
2001-07-11 12:16 ` Mike Black
2001-07-11 15:36 ` Andrew Morton
2001-07-12 10:54 ` Mike Black
2001-07-12 11:34 ` Andrew Morton
2001-07-13 12:22 ` Mike Black
2001-07-13 13:54 ` Mike Black
2001-07-13 14:15 ` Andrew Morton
2001-07-13 17:30 ` Mike Black
2001-07-13 17:38 ` [Ext2-devel] " Stephen C. Tweedie
2001-07-14 10:42 ` Mike Black
2001-07-14 10:53 ` Andrew Morton
2001-07-14 11:58 ` Andrew Morton
2001-07-16 18:23 ` Stephen C. Tweedie
2001-07-13 16:30 ` Stephen C. Tweedie
2001-07-13 17:27 ` Steve Lord
2001-07-13 17:33 ` Stephen C. Tweedie
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=20010710191719.B1493@redhat.com \
--to=sct@redhat.com \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.com \
/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