All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roberto Spadim <rspadim@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Help creating filesystem (xfs) and partitioning
Date: Thu, 25 Jul 2013 20:30:23 -0500	[thread overview]
Message-ID: <51F1D12F.8030507@hardwarefreak.com> (raw)
In-Reply-To: <CAH3kUhHzZ3DoA-mJiQG+27gai1=MZEu6t8JTMtmMvQ7q0ipEoQ@mail.gmail.com>

On 7/25/2013 7:36 PM, 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?

What I would do:

	swap	1GB partition on each disk

md RAID1

/boot	ext2	100MB
rootfs	XFS	remainder of disk
home
...

> i'm considering only one partition with swap and one partition with
> raid1+xfs, what you think?

I wouldn't do it.  See above.

> in a crash (power failure) i will have better rescure with only one
> partition? or many partitions?

Having a separate /boot is always a good idea.

And truthfully, for a system of this caliber, you don't really gain
anything by using XFS, certainly not from a performance standpoint.  If
you were already an XFS user on large systems and it was simply your "go
to" filesystem, then using it on this system may make sense.  And if you
don't have a working UPS, you should definitely stay away from XFS.
Power failure shouldn't cause filesystem corruption, but it may well
corrupt or zero out files that are open for write but not written.  XFS
journals metadata, not data.

-- 
Stan


  reply	other threads:[~2013-07-26  1:30 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 [this message]
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=51F1D12F.8030507@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=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 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.