From: Eric Sandeen <sandeen@sandeen.net>
To: Dewangga Bachrul Alam <dewanggaba@xtremenitro.org>, xfs@oss.sgi.com
Subject: Re: Change sector size on existing partition
Date: Fri, 23 Jan 2015 10:44:05 -0600 [thread overview]
Message-ID: <54C27A55.5030701@sandeen.net> (raw)
In-Reply-To: <54C2761C.4050208@xtremenitro.org>
On 1/23/15 10:26 AM, Dewangga Bachrul Alam wrote:
> Hi,
>
> Thanks for your kind, but I don't know how to reproduce the errors, it
> happens randomly. I try to reproduce on VM but nothing helps, I can't
> create raid array on VM. :)
>
> But, I'm quite sure there is miscalculation or something else that make
> 4k sector size on RAID-10 array.
Well, as Brian mentioned in the other part of the thread, it's the logical
and physical sector sizes that matter. mkfs.xfs simply acts on what the
device reports (i.e. the --getpbsz value).
If for some reason your RAID-10 array is reporting 4k/4k and you don't expect
that, you'll need to go digging through the block device configuration and
maybe ask questions of those communities, too.
It seems like you have interesting device stacking; use the blockdev command
to check logical & physical sector size at each layer starting at the disk
itself, and work your way up.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-01-23 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 13:04 Change sector size on existing partition Dewangga Bachrul Alam
2015-01-23 13:39 ` Brian Foster
2015-01-23 13:46 ` Dewangga Bachrul Alam
2015-01-23 14:06 ` Brian Foster
2015-01-23 14:35 ` Dewangga Bachrul Alam
2015-01-23 15:29 ` Eric Sandeen
2015-01-23 15:40 ` Dewangga Bachrul Alam
2015-01-23 15:49 ` Eric Sandeen
2015-01-23 16:26 ` Dewangga Bachrul Alam
2015-01-23 16:44 ` Eric Sandeen [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=54C27A55.5030701@sandeen.net \
--to=sandeen@sandeen.net \
--cc=dewanggaba@xtremenitro.org \
--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