From: Eric Sandeen <sandeen@sandeen.net>
To: Stan Hoeppner <stan@hardwarefreak.com>, xfs@oss.sgi.com
Subject: Re: makefs alignment issue
Date: Fri, 24 Oct 2014 17:27:00 -0500 [thread overview]
Message-ID: <544AD234.3060100@sandeen.net> (raw)
In-Reply-To: <544AD077.4080305@sandeen.net>
On 10/24/14 5:19 PM, Eric Sandeen wrote:
> On 10/24/14 5:08 PM, Stan Hoeppner wrote:
>>
>> On 10/24/2014 03:14 PM, Eric Sandeen wrote:
>
> ...
>
>>>> Any ideas how to verify what's going on here and fix it?
>>>
>>> # blockdev --getiomin --getioopt /dev/s2d_a1l003
Also, what does it show for the underlying non-multipath device(s)?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-24 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 20:11 makefs alignment issue Stan Hoeppner
2014-10-24 20:14 ` Eric Sandeen
2014-10-24 22:08 ` Stan Hoeppner
2014-10-24 22:19 ` Eric Sandeen
2014-10-24 22:27 ` Eric Sandeen [this message]
2014-10-25 3:08 ` Stan Hoeppner
2014-10-25 15:51 ` Eric Sandeen
2014-10-25 17:35 ` Stan Hoeppner
2014-10-26 23:43 ` Dave Chinner
2014-10-27 23:04 ` Stan Hoeppner
2014-10-28 0:32 ` Dave Chinner
2014-10-28 16:55 ` 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=544AD234.3060100@sandeen.net \
--to=sandeen@sandeen.net \
--cc=stan@hardwarefreak.com \
--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