From: Dwight Engen <dwight.engen@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Jeff Moyer <jmoyer@redhat.com>, stan@hardwarefreak.com, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: 091, 240, 268 fix for xfs on 4k sector hard drive
Date: Thu, 25 Jul 2013 14:43:08 -0400 [thread overview]
Message-ID: <20130725144308.4c4a5f79@oracle.com> (raw)
In-Reply-To: <51F142E7.4050500@sandeen.net>
On Thu, 25 Jul 2013 10:23:19 -0500
Eric Sandeen <sandeen@sandeen.net> wrote:
[...]
> (You can probably mkfs w/ an explicit 512 sector size, and confirm
> that 512-byte DIOs work again)
Hi Eric, yep, confirmed that doing mkfs.xfs -b size=1024 (used 1024
instead of 512 so that 240 would run) makes 091, 240, and 268 work
without my changes.
> bleah, perhaps that was a mistake - or perhaps we need to fix
> kernelspace to prefer physical-size IOs, but allow logical-size if a
> DIO requests it.
ext4 and btrfs did work, so perhaps that is what they are doing, I
have not looked yet.
[... test 240]
> >>>> -logical_block_size=`blockdev --getss $TEST_DEV`
> >>>> +logical_block_size=`blockdev --getpbsz $TEST_DEV`
> >>>
> >>> FWIW, that doesn't make much sense - putting the physical block
> >>> size into a variable named "logical_block_size".....
> >
> > Yeah, that name wouldn't make much sense with this change. Its
> > actually being used to compare to the fs block size and then its
> > passed into aiodio_sparse2 as offset. 091 and 268 use the more
> > generic name bsize, should I can change it to that?
>
> Well, that was put there with:
>
> commit 2dbd21dc152d89715263990c881025f17c7b632e
> Author: Jeff Moyer <jmoyer@redhat.com>
> Date: Fri Feb 11 15:20:02 2011 -0500
>
> 240: only run when the file system block size is larger than the
> disk sector size
> This test really wants to test partial file-system block I/Os.
> Thus, if the device has a 4K sector size, and the file system has a
> 4K block size, there's really no point in running the test. In the
> attached patch, I check that the fs block size is larger than the
> device's logical block size, which should cover a 4k device block
> size with a 16k fs block size.
>
> I verified that the patched test does not run on my 4k sector
> device with a 4k file system. I also verified that it continues to
> run on a 512 byte logical sector device with a 4k file system block
> size.
> Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
The name was added in this commit, and the message would lead me to
believe that Jeff intended for the test to not run on a 4k physical
sector disk with a 4k fs, so is the "logical_block_size" name a
misnomer?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-25 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 18:32 [PATCH] xfstests: 091,240,268 fix for xfs on 4k sector hard drive Dwight Engen
2013-07-24 23:57 ` [PATCH] xfstests: 091, 240, 268 " Dave Chinner
2013-07-25 4:36 ` Stan Hoeppner
2013-07-25 14:27 ` Dwight Engen
2013-07-25 15:23 ` Eric Sandeen
2013-07-25 18:43 ` Dwight Engen [this message]
2013-07-25 19:07 ` Eric Sandeen
2013-08-15 18:20 ` Ric Wheeler
2013-08-15 23:30 ` Stan Hoeppner
2013-08-19 19:54 ` 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=20130725144308.4c4a5f79@oracle.com \
--to=dwight.engen@oracle.com \
--cc=jmoyer@redhat.com \
--cc=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