From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Help creating filesystem (xfs) and partitioning
Date: Wed, 24 Jul 2013 14:35:20 -0500 [thread overview]
Message-ID: <51F02C78.6090104@hardwarefreak.com> (raw)
In-Reply-To: <CAH3kUhEZLBZD79WW75gWF4a5dvhQas=1+oR6vaTbuNtTBRfayg@mail.gmail.com>
On 7/24/2013 12:07 PM, Roberto Spadim wrote:
> Could i use ext3 or ext4 for boot filesystem? I need crash security (ok a
> ups is the best solution) xfs could be used too?
Again, Roberto, a journaling filesystem is not necessary for /boot. It
will not make files in /boot any more crash resistant. Files in /boot
are only modified when you replace (upgrade) your kernel. Corruption
can only occur when file writes are in flight but not completely on
disk. Therefore, to corrupt files in /boot, the machine must crash or
lose power while you're installing a new kernel, i.e. within a window of
about 10 seconds. There are 31,536,000 seconds in a year. So the odds
of a crash/power loss during any one of your kernel upgrades are, if my
math is close, approximately
1 in 3,153,600
> If i need a home directory with crypt filesystem, what should i use? Two
> partitions one with xfs and other with dmcrypt (for example) and xfs, or
> only one partition and a loop mount with crypt and quota limit for home
> directory?
Is this a workstation, personal server, or multiuser server with decent
load? If the load is light you can get away with multiple XFS
filesystem on a single spindle, separate rootfs and home.
--
Stan
next prev parent reply other threads:[~2013-07-24 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 0:06 Help creating filesystem (xfs) and partitioning Roberto Spadim
2013-07-24 6:56 ` Stan Hoeppner
[not found] ` <CAH3kUhHoQiyhVotNpNDq-rcQ36vZbRrZvoEsUzyo0=9mz8=+3w@mail.gmail.com>
2013-07-24 17:28 ` Stan Hoeppner
[not found] ` <CAH3kUhEZLBZD79WW75gWF4a5dvhQas=1+oR6vaTbuNtTBRfayg@mail.gmail.com>
2013-07-24 19:35 ` Stan Hoeppner [this message]
2013-07-24 19:41 ` Mark Knecht
2013-07-25 2:34 ` Roberto Spadim
2013-07-25 21:52 ` Bill Davidsen
2013-07-25 22:36 ` Roberto Spadim
2013-07-25 23:27 ` Stan Hoeppner
2013-07-26 0:36 ` Roberto Spadim
2013-07-26 1:30 ` Stan Hoeppner
2013-07-26 1:47 ` Roberto Spadim
2013-07-26 16:15 ` Stan Hoeppner
2013-07-26 16:47 ` Roberto Spadim
2013-07-28 22:46 ` Bill Davidsen
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=51F02C78.6090104@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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;
as well as URLs for NNTP newsgroup(s).