From: "Lukáš Czerner" <lczerner@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>,
Theodore Ts'o <tytso@mit.edu>, Eric Whitney <enwlinux@gmail.com>,
Ben Myers <bpm@sgi.com>,
linux-ext4@vger.kernel.org
Subject: Re: possible dev branch regression - xfstest 285/1k
Date: Tue, 19 Mar 2013 09:50:21 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1303190949280.2455@(none)> (raw)
In-Reply-To: <5147CD46.1090205@sandeen.net>
On Mon, 18 Mar 2013, Eric Sandeen wrote:
> Date: Mon, 18 Mar 2013 21:28:22 -0500
> From: Eric Sandeen <sandeen@sandeen.net>
> To: Theodore Ts'o <tytso@mit.edu>
> Cc: Dave Chinner <david@fromorbit.com>, Eric Whitney <enwlinux@gmail.com>,
> Eric Sandeen <sandeen@redhat.com>, Ben Myers <bpm@sgi.com>,
> linux-ext4@vger.kernel.org, xfs-oss <xfs@oss.sgi.com>
> Subject: Re: possible dev branch regression - xfstest 285/1k
>
> On 3/18/13 9:00 PM, Theodore Ts'o wrote:
> > On Tue, Mar 19, 2013 at 12:47:18PM +1100, Dave Chinner wrote:
> >> Sorry about this - I've mixed up my threads about ext4 having
> >> problems with zero-out being re-enabled. I thought this was a
> >> cross-post of the 218 issue....
> >>
> >> However, the same reasoning can be applied to 285 - the file sizes,
> >> the size of the holes and the size of the data is all completely
> >> arbitrary. If we make the holes in the files larger, then the
> >> zero-out problem simply goes away.
> >
> > Right. That was my observation. We can either make the holes larger,
> > by changing:
> >
> > pwrite(fd, buf, bufsize, bufsize*10);
> >
> > to
> >
> > pwrite(fd, buf, bufsize, bufsize*42);
> >
> > ... and then changing the expected values returned by
> > SEEK_HOLE/SEEK_DATA. (By the way; this only matters when we are
> > testing 1k blocks; if we are using a 4k block size in ext4, the test
> > currently passes.)
> >
> > Or we could set some ext4-specific tuning parameters into the #218
>
> 285! :)
>
> > shell script, if the file system in question was ext4.
> >
> > I had assumed that folks would prefer making the holes larger, but
> > Eric seemed to prefer the second choice as a better one.
>
> Ok, after the discussion I'm convinced too. Stretching out the allocation
> to avoid fill-in probably makes sense. But maybe not "42" -
> how about something much larger, so that any "reasonable" filesystem
> wouldn't even consider zeroing the range in between?
I am actually in favour of 42. 42 is "The answer" here :)
-Lukas
>
> -Eric
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-03-19 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130315222818.GA16100@wallace>
[not found] ` <20130316150923.GA18589@gmail.com>
[not found] ` <20130317030648.GA14225@thunk.org>
[not found] ` <51473C8B.5070509@redhat.com>
[not found] ` <20130318170927.GA5639@thunk.org>
2013-03-18 17:34 ` possible dev branch regression - xfstest 285/1k Eric Sandeen
2013-03-18 20:41 ` Ben Myers
2013-03-18 23:12 ` Dave Chinner
2013-03-19 1:40 ` Theodore Ts'o
2013-03-19 2:07 ` Dave Chinner
2013-03-19 1:47 ` Dave Chinner
2013-03-19 2:00 ` Theodore Ts'o
2013-03-19 2:22 ` Dave Chinner
2013-03-19 2:28 ` Eric Sandeen
2013-03-19 8:50 ` Lukáš Czerner [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='alpine.LFD.2.00.1303190949280.2455@(none)' \
--to=lczerner@redhat.com \
--cc=bpm@sgi.com \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
--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