From: Joost Roeleveld <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: raid1 grub ext4
Date: Tue, 12 Apr 2011 17:16:44 +0200 [thread overview]
Message-ID: <20110412151705.22F48277F@data.antarean.org> (raw)
In-Reply-To: <4DA46856.3050308@gmail.com>
On Tuesday 12 April 2011 09:57:26 Dale wrote:
> Peter Humphrey wrote:
> > On Tuesday 12 April 2011 15:10:52 James wrote:
> >> Stroller<stroller<at> stellar.eclipse.co.uk> writes:
> >>> There's no need for extents on such a small partition,
> >>> nor journalling (because you write to /boot so
> >>> rarely, the likelihood of a power failure when you're
> >>> doing so is minuscule).
> >>
> >> Yea, sure, but that's not the point. I just wanted to
> >> use ext4 for everything. Not on this system, but often,
> >> my boot partition is very active, as I copy many kernels
> >> there for many different (arch)machines and different hardware
> >> (HD, SSD, CF, SD...) I try to make the many systems I admin
> >> as homogeneous as possible, hence the switch to ext4
> >> for boot.
> >
> > Nevertheless, if ext4 isn't working for you you should follow the advice
> > you've been given and format /boot as ext2. All my boot partitions are
> > ext2, regardless of which others are ext4 or reiserfs.
>
> Same here. I use ext3 and reiserfs, depending on what it is, but /boot
> is always ext2. Why, it works well with grub and has for many many
> years and most likely will for many years to come as well.
>
> As for making things the same, that my not always be a good idea
> either. I put some things on reiserfs but some on ext3. It seams each
> file system has its strengths and weaknesses. I read that portage, with
> a lot of small files, does better on ext* file systems. So I put
> portage on that. Most everything else is on reiserfs.
Where did you read that portage, with lots of small files, is best on ext*?
I was under the impression that reiserfs has better performance with lots of
smaller files.
--
Joost
next prev parent reply other threads:[~2011-04-12 15:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 18:12 [gentoo-user] raid1 grub ext4 James
2011-04-11 20:18 ` Mick
2011-04-12 5:57 ` Stroller
2011-04-12 14:10 ` [gentoo-user] " James
2011-04-12 14:31 ` Peter Humphrey
2011-04-12 14:57 ` Dale
2011-04-12 15:16 ` Joost Roeleveld [this message]
2011-04-12 15:44 ` Peter Humphrey
2011-04-13 10:14 ` Alex Schuster
2011-04-11 20:49 ` [gentoo-user] " Neil Bothwick
2011-04-12 2:09 ` Mark Shields
2011-04-12 9:11 ` Neil Bothwick
2011-04-12 14:20 ` [gentoo-user] " James
2011-04-12 16:53 ` James
2011-04-13 9:46 ` Florian Philipp
2011-04-14 12:56 ` James
2011-04-14 13:14 ` Florian Philipp
2011-04-14 14:41 ` Paul Hartman
2011-04-14 13:10 ` James
2011-04-14 13:41 ` James
2011-04-14 14:11 ` Florian Philipp
2011-04-14 15:07 ` James
2011-04-14 15:52 ` Florian Philipp
2011-04-14 16:29 ` James
2011-04-14 19:49 ` Florian Philipp
2011-04-14 20:19 ` James
2011-04-14 21:12 ` Florian Philipp
2011-04-14 20:24 ` James
2011-04-14 14:13 ` Dale
2011-04-14 14:52 ` James
2011-04-14 16:14 ` Dale
2011-04-14 16:34 ` James
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=20110412151705.22F48277F@data.antarean.org \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.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