From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH v2] btrfs/255: add test for quota disable in parallel with balance
Date: Wed, 19 Jan 2022 02:19:48 +0000 [thread overview]
Message-ID: <20220119021947.bfqssdofxdiuediy@shindev> (raw)
In-Reply-To: <YebSuDGqX4RoxpXq@debian9.Home>
On Jan 18, 2022 / 14:46, Filipe Manana wrote:
> On Tue, Jan 18, 2022 at 02:57:21PM +0900, Shin'ichiro Kawasaki wrote:
(snip)
> > +# Run btrfs balance and quota enable/disable in parallel
> > +_btrfs_stress_balance $SCRATCH_MNT >> $seqres.full &
> > +balance_pid=$!
> > +echo $balance_pid >> $seqres.full
> > +for ((i = 0; i < 20; i++)); do
> > + $BTRFS_UTIL_PROG quota enable $SCRATCH_MNT
> > + $BTRFS_UTIL_PROG quota disable $SCRATCH_MNT
> > +done
> > +kill $balance_pid &> /dev/null
>
> You need to wait for the balance pid to exit before terminating the test,
> otherwise the test will fail often when the fstests framework is trying
> to unmount the scratch device (with an -EBUSY returned from umount).
>
> And please do like in other tests that use _btrfs_stress_balance():
>
> kill $balance_pid
> wait
> # wait for the balance operation to finish
> while ps aux | grep "balance start" | grep -qv grep; do
> sleep 1
> done
>
> Like in btrfs/060 for example.
>
> Other than that, it looks fine, thanks.
Thanks. Will update the patch as you commented and send out v3.
--
Best Regards,
Shin'ichiro Kawasaki
prev parent reply other threads:[~2022-01-19 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 5:57 [PATCH v2] btrfs/255: add test for quota disable in parallel with balance Shin'ichiro Kawasaki
2022-01-18 14:46 ` Filipe Manana
2022-01-19 2:19 ` Shinichiro Kawasaki [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=20220119021947.bfqssdofxdiuediy@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.