From: Bill Davidsen <davidsen@tmr.com>
To: Roberto Spadim <rspadim@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Help creating filesystem (xfs) and partitioning
Date: Sun, 28 Jul 2013 18:46:07 -0400 [thread overview]
Message-ID: <51F59F2F.2080709@tmr.com> (raw)
In-Reply-To: <CAH3kUhHzZ3DoA-mJiQG+27gai1=MZEu6t8JTMtmMvQ7q0ipEoQ@mail.gmail.com>
Roberto Spadim wrote:
> ok =] in other words no problem about performace loss, just use one
> xfs per disk, right?
> the second doubt... i was thinking about /boot /home and /, in the
> same partition, should i consider other design? a /boot with ext2 or
> ext3 and a / with xfs?
>
> i'm considering only one partition with swap and one partition with
> raid1+xfs, what you think?
> in a crash (power failure) i will have better rescure with only one
> partition? or many partitions?
>
I would create a /boot partition, root partition, and swap partition on each
drive and make rais1 to create three devices, with two filesystem, /boot and
root. My thought is that you rarely change /boot, and that MUST work to get the
system up, so put it by itself. Also, I'm pretty sure you want ext on the boot
filesystem, if for no other reason than the code in grub being better tested
booting from that than any other. I will let someone who is more expert in xfs
than I discuss any questions you have, boot issues may be urban myth, but I see
no benefit to using anything else.
Note that I have no solid evidence the other than ext for /boot causes problems,
but years of trouble free with ext3.
--
Bill Davidsen <davidsen@tmr.com>
"'Nothing to hide' does not imply 'nothing to fear'"
- me
"AT&T could not seriously contend that a reasonable entity in its position
could have believed that the alleged domestic dragnet was legal."
-judge Vaughn R. Walker of the U.S. District Court
for the Northern District of California, EFF vs. AT&T
prev parent reply other threads:[~2013-07-28 22:46 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
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 [this message]
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=51F59F2F.2080709@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=rspadim@gmail.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;
as well as URLs for NNTP newsgroup(s).