public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Helmut Tessarek <tessarek@evermeet.cx>
To: xfs@oss.sgi.com
Subject: How to format RAID1 correctly
Date: Tue, 23 Sep 2014 20:46:34 -0400	[thread overview]
Message-ID: <5422146A.90206@evermeet.cx> (raw)

The information provided in the FAQ and on several web sites is not really
useful regarding RAID1.

According to the FAQ (entry 35):
The correct options to format a RAID1 (2 disks) with 64k chunk size is:
mkfs.xfs -d su=64k -d sw=1 /dev/mapper/data
But it also states that it would be automatically detected and used correctly,
yet
mkfs.xfs /dev/mapper/data
yields a different result:

[root@atvie01s ~]# mkfs.xfs -f /dev/mapper/data

meta-data=/dev/mapper/data       isize=256    agcount=4,
agsize=244173876 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=976695504, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal log           bsize=4096   blocks=476902, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

Formel 1:

[root@atvie01s ~]# mkfs.xfs -f -d su=64k -d sw=1 /dev/mapper/data

meta-data=/dev/mapper/data       isize=256    agcount=32,
agsize=30521728 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=976695296, imaxpct=5
         =                       sunit=16     swidth=16 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal log           bsize=4096   blocks=476902, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0


Another inconsistency is that RAID1 doesn't use striping, so the chunk size
should be irrelevant in the first place.

So what is ultimately the correct way to format a RAID1?

Cheers,
  K. C.

-- 
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2014-09-24  0:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24  0:46 Helmut Tessarek [this message]
2014-09-24  2:05 ` How to format RAID1 correctly Helmut Tessarek
2014-09-24  2:07 ` Eric Sandeen
2014-09-24  2:11   ` Helmut Tessarek
2014-09-24  2:21     ` Eric Sandeen
2014-09-24  2:30       ` Helmut Tessarek
2014-09-24  3:05     ` stan hoeppner
2014-09-24  3:15       ` Helmut Tessarek
2014-09-24  4:09         ` Stan Hoeppner
2014-09-24 15:53           ` Helmut Tessarek
2014-09-24 16:18             ` Eric Sandeen
2014-09-24 19:06             ` Stan Hoeppner

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=5422146A.90206@evermeet.cx \
    --to=tessarek@evermeet.cx \
    --cc=xfs@oss.sgi.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