From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v1 1/1] test_robind: add "-f" mkfs option for xfs and btrfs
Date: Wed, 25 May 2016 02:31:01 -0400 (EDT) [thread overview]
Message-ID: <977252429.1084123.1464157861719.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160524152621.GB12920@rei.suse.cz>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: "Boyang Xue" <bxue@redhat.com>, "stanislav kholmanskikh" <stanislav.kholmanskikh@oracle.com>, ltp@lists.linux.it
> Sent: Tuesday, 24 May, 2016 5:26:22 PM
> Subject: Re: [LTP] [PATCH v1 1/1] test_robind: add "-f" mkfs option for xfs and btrfs
>
> Hi!
> > Alternative would be to zero-erase first blocks of LTP_BIG_DEV
> > in runltp, but I'm not sure we want to assume that all tests
> > are going to write over it.
> >
> > I found only 3 tests using LTP_BIG_DEV, this is the only
> > one that is using xfs/btrfs, the other two are ext3/4.
>
> Or we can move the dd that erases first blocks from tst_acquire_device()
> to tst_mkfs().
I went to re-read why we are avoiding -f, and this does sound better
than adding -f back.
Regards,
Jan
>
> Or we can create an API function to get the path to big device and erase
> it there...
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
next prev parent reply other threads:[~2016-05-25 6:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 7:49 [LTP] [PATCH v1 1/1] test_robind: add "-f" mkfs option for xfs and btrfs Boyang Xue
2016-05-24 14:01 ` Jan Stancek
2016-05-24 15:26 ` Cyril Hrubis
2016-05-25 6:31 ` Jan Stancek [this message]
2016-05-25 7:05 ` Stanislav Kholmanskikh
2016-05-25 14:10 ` Cyril Hrubis
2016-06-17 4:28 ` Eryu Guan
2016-06-21 10:51 ` Stanislav Kholmanskikh
2016-06-21 10:59 ` Eryu Guan
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=977252429.1084123.1464157861719.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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