From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: xfstests ext4/304 failing due to donor inode's i_size == 0
Date: Tue, 20 Oct 2015 17:44:03 +0300 [thread overview]
Message-ID: <87h9llior0.fsf@openvz.org> (raw)
In-Reply-To: <20151019025727.GA6676@thunk.org>
[-- Attachment #1.1: Type: text/plain, Size: 260 bytes --]
Theodore Ts'o <tytso@mit.edu> writes:
> Hi Dmitry,
>
> I was investigating why ext4/304 is failing, and it's due to
> defrag-fuzzer returning an error:
Yep. You are right. I have out of tree patch which fix that. I'll send it
to xfstests-dev list.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: ext4-304-fix.patch --]
[-- Type: text/x-diff, Size: 952 bytes --]
>From ee628504370564704e218ecf089f00c243b6fd12 Mon Sep 17 00:00:00 2001
From: Dmitry Monakhov <dmonakhov@openvz.org>
Date: Tue, 20 Oct 2015 18:32:03 +0400
Subject: [PATCH] ext4/304 handle ENOSPC/EINVAL correctly
'defrag-fuzzer' is task which try to perform inplace defrag, inline-defrag
is basically of {falloc,ioc_swap} and may fail due to ENOSPC on first stage.
In that case IOCTL returns EINVAL (because we try to swap invalid extents)
Since this is hard core test then ENOSPC and corresponding EINVAL is expected.
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
---
tests/ext4/304 | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/tests/ext4/304 b/tests/ext4/304
index 7b90f1d..81d69b8 100644
--- a/tests/ext4/304
+++ b/tests/ext4/304
@@ -76,6 +76,7 @@ donorname=test4.def
filename=test4
inplace=1
rw=randwrite
+ignore_error=,EINVAL
numjobs=4*${LOAD_FACTOR}
runtime=30*${TIME_FACTOR}
time_based
--
1.7.1
next prev parent reply other threads:[~2015-10-20 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 2:57 xfstests ext4/304 failing due to donor inode's i_size == 0 Theodore Ts'o
2015-10-20 14:44 ` Dmitry Monakhov [this message]
2015-10-25 11:10 ` Theodore Ts'o
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=87h9llior0.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--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).