From: Oleg Drokin <green@namesys.com>
To: JPASTORM@esade.edu
Cc: reiserfs-list@namesys.com
Subject: Re: New to reiserfs
Date: Mon, 13 May 2002 13:53:43 +0400 [thread overview]
Message-ID: <20020513135343.A1386@namesys.com> (raw)
In-Reply-To: <OF69292CB8.96B5D3F9-ONC1256BB8.0033D851@esade.edu>
Hello!
On Mon, May 13, 2002 at 11:34:29AM +0200, JPASTORM@esade.edu wrote:
> I'm new to this surprising file system. Currently I have a Linux Red Hat
> 6.2 server for testing, with two partitions (/ and /boot). I'm running the
> 2.2.14-5.0 kernel and I have several questions about reiserfs:
> 1.- Do I necessarily have to update to the 2.2.20 kernel so as to use
> 2.2.20-reiserfs patch?
No, but it is not guaranteed that that patch would apply to older kernels.
Also 2.2.14 kernel is a very old one, and it is willed with bugs and security
holes (e.g. anyone with local account may obtain root access in seconds).
So it is good idea to upgrade the kernel regardless of whenever you plan to
use reiserfs or not.
> 2.- Can I migrate from ext2 to reiserfs without loosing data (I know I
> should always backup my data) or should I have to format my new reiserfs
> partitions?
No. Currently you need to do full backup/mkfs/restore cycle.
> 3.- Is there any partition in other servers (in production) where it is
> advisable to stay with the ext2 filesystem?
I usually have very small "rescue" ext2 partition with all the necessary tools
present to ercover from various system disasters, I also never mount that
partition, except when I need to update some tools there.
ext2 was choosen as an fstype because 99% of all kernels are built with
ext2 support built-in, I guess.
In such a scenario, if I loose almost everything including rootfs,
I still can get any kernel and boot into my rescue partition to try and recover
stuff.
> 4.- I have a PIII 1 GHz, 512 MB RAM, SCSI server where I run sendmail, bind
> and squid. Will I have problems with performance if I migrate to reiserfs?
Not likely.
> What's the counterpart of dealing with a journaling filesystem?
Some of the diskspace is occupied for the journal (32M to be exact).
Also reiserfs is a balanced tree filesystem, and it puts somewhat higher
load on the CPU. (more likely to overheat if you do not have correct
cooling and stuff).
Also you usually do not see those fsck runs at startup after power failures.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-13 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 9:34 New to reiserfs JPASTORM
2002-05-13 9:53 ` Oleg Drokin [this message]
2002-05-13 10:07 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 19:53 Dieter Nützel
2002-05-13 20:57 ` Hans Reiser
2002-05-13 21:24 ` Dieter Nützel
2002-05-14 13:10 ` Chris Mason
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=20020513135343.A1386@namesys.com \
--to=green@namesys.com \
--cc=JPASTORM@esade.edu \
--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.