From: Chris Mason <mason@suse.com>
To: JP Howard <jh_lists@fastmail.fm>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Which journal relocation+datalogging patches?
Date: 14 Nov 2002 10:10:14 -0500 [thread overview]
Message-ID: <1037286615.21957.233.camel@tiny> (raw)
In-Reply-To: <20021114033046.9A82D496DAB@server5.fastmail.fm>
On Wed, 2002-11-13 at 22:30, JP Howard wrote:
> I'm trying to build a 2.4.20pre1 kernel with data logging patches,
> journal relocation, and and important performance/reliability patches.
>
> I see from
> ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.20/README
> that these patches are against the journal relocation patches. But where
> are they? I've found a patch against 2.5.3, but that doesn't apply
> cleanly to 2.4.20pre1.
>
> If this patch doesn't yet exist against 2.4.20, could you please upload
> it someplace Chris, and let me know what order to apply the patches?
> (Since you obviously have made it, to create the data logging patch
> against it! :-)
Sorry for the confusion. The journal relocation parts are in
01-relocation-5.diff.gz, the README was attempting to make it clear
namesys authored it. Hopefully it is a little clearer now.
>
> I looks to me like all other important patches are already in
> 2.4.20pre1--is that right?
>
> What are the steps then required to move the journal to an external
> device (we're using Umem NVRAM, FWIW)? How stable are the journal
> relocation patches? If they're not recommended for production as yet,
> would we be able to move the journal to an external device later, without
> rebooting (or at least without recreating the filesystem)?
You can use reiserfstune to change the log device of an existing disk.
The relocation and data logging patches are considered stable, both are
included in the suse kernels.
To try the external logging device mkreisefs -j /dev/xxx -s 8192
/dev/yyy
That will create a 32MB log on /dev/xxx, and the main filesystem on
/dev/yyy
>
> I'm really looking forward to trying this out--I plan to set aside an
> identical server for testing and benchmarking, so hopefully we'll be able
> to provide some interesting benchmarks of IMAP server performance with
> external journals.
Excellent, I'd love to see those numbers.
-chris
next prev parent reply other threads:[~2002-11-14 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 3:30 Which journal relocation+datalogging patches? JP Howard
2002-11-14 15:10 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 20:43 JP Howard
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=1037286615.21957.233.camel@tiny \
--to=mason@suse.com \
--cc=jh_lists@fastmail.fm \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.