From: Roman Penyaev <roman.penyaev@profitbricks.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Roman Penyaev <roman.penyaev@profitbricks.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] ext4: Find desired extent in ext4_ext_shift_extents() using binsearch
Date: Wed, 4 Jan 2017 19:32:18 +0100 [thread overview]
Message-ID: <CAJrWOzA467XZOpZmaGr6_z+nwNAxJZXYFmb4azS7Haag4dtWAQ@mail.gmail.com> (raw)
In-Reply-To: <20170103221510.dkrxqav7qrq772ji@thunk.org>
On Tue, Jan 3, 2017 at 11:15 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> On Tue, Jan 03, 2017 at 09:44:15PM +0100, Roman Penyaev wrote:
>>
>> (I had to say that right now I am testing on 4.4.28 kernel and testing
>> on latest sources taken from linux-next will require some time, but of
>> course I will retest and send up-to-date results)
>>
>> ---
>> Failures: ext4/302 ext4/303 ext4/304 generic/061 generic/063
>> generic/075 generic/079 generic/091 generic/112 generic/127
>> generic/252 generic/263
>> Failed 12 of 200 tests
>
> You didn't say what file system configuration you're using, but I'm
> assuming it's a default ext4 4k configuration?
Yep, that was the default run, 4K block.
> One of the things
> about my kvm-xfstests and gce-xfstests setup is that I test a range of
> file system configurations, and there are specific exclude files to
> skip certain known failures. Currently we are skipping the following
> tests globally (from kvm-xfstests/test-appliances/files/root/fs/ext4/exclude):
[ cut ]
> You'll see that modulo the encryption failures and some failures on
> the 1k config case which I need to track down and iron out, we're in
> pretty good shape. Below please find the summary; attached please
> find the full log file.
Thanks a lot. Perfect reference. That is quite enough for a good start.
This kvm-xfstests is a nice thingy. That was pretty annoying to rebuild
xfsprogs on a debian jessie, which does not have 'xfs_io -c finsert' by
default.
Theodore, recently I sent an ext4/023 xfstest test. New test reproduces
the problem with a wrong right shift. I tried to make the test explicit,
but not sure succeeded or not. Probably, md5sum is not a good choice to
make things clear, but hexdump of 1000 blocks is quite large (~80K).
Could you please take a look?
Now I am running kvm-xfstests, will figure out what I've done wrong with
recent ext4 patches.
--
Roman
next prev parent reply other threads:[~2017-01-04 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 12:54 [PATCH 0/3] ext4: fallocate insert/collapse range fixes Roman Pen
2017-01-02 12:54 ` [PATCH 1/3] ext4: Include forgotten start block on fallocate insert range Roman Pen
2017-01-02 12:54 ` [PATCH 2/3] ext4: Do not populate extents tree with outdated offsets while shifting extents Roman Pen
2017-01-02 12:54 ` [PATCH 3/3] ext4: Find desired extent in ext4_ext_shift_extents() using binsearch Roman Pen
2017-01-03 14:40 ` Theodore Ts'o
2017-01-03 20:44 ` Roman Penyaev
2017-01-03 22:15 ` Theodore Ts'o
2017-01-04 18:32 ` Roman Penyaev [this message]
2017-01-04 23:58 ` Theodore Ts'o
2017-01-05 8:02 ` Roman Penyaev
2017-01-06 20:21 ` Roman Penyaev
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=CAJrWOzA467XZOpZmaGr6_z+nwNAxJZXYFmb4azS7Haag4dtWAQ@mail.gmail.com \
--to=roman.penyaev@profitbricks.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).