From: Dave Chinner <david@fromorbit.com>
To: "Gamel Anton J." <anton.gamel@physik.uni-freiburg.de>
Cc: xfs@oss.sgi.com
Subject: Re: irregular mkfs.xfs results on identical HW
Date: Fri, 26 Sep 2014 07:19:01 +1000 [thread overview]
Message-ID: <20140925211901.GH4945@dastard> (raw)
In-Reply-To: <54247484.2030808@physik.uni-freiburg.de>
On Thu, Sep 25, 2014 at 10:01:08PM +0200, Gamel Anton J. wrote:
> Dear all,
>
> servers with identical disk setup (HW RAID0 H310a):
>
> Disk /dev/sda: 598.9 GB, 598879502336 bytes
> /dev/sda1 1 49152 394813439+ 82 Linux swap / Solaris
> /dev/sda2 49153 50176 8225280 83 Linux
> /dev/sda3 6399 72809 533446357+ 44 Unknown
>
> mkfs.xfs creates on 28 of them:
> meta-data=/dev/sda3 isize=256 agcount=16, agsize=8335099 blks
> = sectsz=512 attr=1, projid32bit=0
> data = bsize=4096 blocks=133361584, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=32768, version=1
> = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
THat's clearly an old version of mkfs - it's selected version 1 logs
and attr1 by default and a log size of only 128MB. mkfs.xfs has
defaulted to v2 logs since 3.0.0 (2007).
> but on four out of them:
> meta-data=/dev/sda3 isize=256 agcount=4, agsize=33340398 blks
> = sectsz=512 attr=2, projid32bit=0
> data = bsize=4096 blocks=133361589, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=65117, version=2
> = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
Clearly much newer - attr2, log v2, log larger than 128MB...
mkfs.xfs -V on each of the nodes will tell you that they are running
different versions of mkfs, I think.
> The only way it worked was to dump nodeA:/dev/sda3 to nodeB:/dev/sda3
> Is there an explanation? May be I missed something ... hints?
If you are building a new storage system, then I'd highly recommend
all the nodes run the same software and that software is the newest
possible release you can get....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-25 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 20:01 irregular mkfs.xfs results on identical HW Gamel Anton J.
2014-09-25 21:05 ` Eric Sandeen
2014-09-25 21:19 ` Dave Chinner [this message]
2014-09-29 16:47 ` Gamel Anton J.
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=20140925211901.GH4945@dastard \
--to=david@fromorbit.com \
--cc=anton.gamel@physik.uni-freiburg.de \
--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