From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Dušan Čolić" <dusanc@gmail.com>,
"Ivan Shapovalov" <intelfx100@gmail.com>,
reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: [Testing] Testing Reiser4 with xfstests
Date: Sat, 06 Dec 2014 13:02:41 +0100 [thread overview]
Message-ID: <5482F061.6040807@gmail.com> (raw)
In-Reply-To: <CADW=+3mMFTZDrQaLvL1d7SU4o_Ek7KWhbX6jDJJA7JdTtK465Q@mail.gmail.com>
On 12/06/2014 11:07 AM, Dušan Čolić wrote:
> Some of the tests (~20 of 300) didn't work and I traced that they
> require fallocate. AFAIK R4 doesn't support it right?
Yup, we don't support fallocate.
Edward.
>
> On Fri, Dec 5, 2014 at 2:46 PM, Dušan Čolić <dusanc@gmail.com> wrote:
>> On Fri, Dec 5, 2014 at 2:22 PM, Dušan Čolić <dusanc@gmail.com> wrote:
>>> I managed to get xfstests (
>>> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=tree ) to
>>> run on Reiser4 partition. Test for async, acl, quota still don't work but a
>>> lot of the rest finishes successfully.
>>> Tests were run on reiser4-for-3.16.2.patch
>>> I'll post unsuccessful tests and their results in following e-mails.
>>>
>> Btw. these tests can stress test fs and I could also test with
>> different mount (block size?) or mkfs options (reg40) and automate it
>> easily to test multiple combinations, so if there's any ideas what
>> would be useful please tell me.
>>
>> Thanks
>> Dushan
>>
>>
>>> Dushan
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-06 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADW=+3nVaodqG2YX0g8kajU=ZPKOPw167Sm98vHQBFvmqfL4xg@mail.gmail.com>
2014-12-05 13:46 ` [Testing] Testing Reiser4 with xfstests Dušan Čolić
2014-12-06 10:07 ` Dušan Čolić
2014-12-06 12:02 ` Edward Shishkin [this message]
2014-12-07 8:28 ` Dušan Čolić
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=5482F061.6040807@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dusanc@gmail.com \
--cc=intelfx100@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/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).