Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: "Darrick J. Wong" <djwong@kernel.org>, Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, fdmanana@suse.com
Subject: Re: [PATCH] btrfs/282: skip test if /var/lib/btrfs isnt writable
Date: Tue, 29 Aug 2023 17:53:28 +0800	[thread overview]
Message-ID: <35cc63b4-a52b-dee6-5e51-489402c20ae0@oracle.com> (raw)
In-Reply-To: <62240534-27e1-a40e-49a3-7198be83b8b3@oracle.com>


>>   _require_scratch_size $(( 5 * 1024 * 1024))
>> +# Make sure we can create scrub progress data file
>> +if [ -e /var/lib/btrfs ]; then
>> +    test -w /var/lib/btrfs || _notrun '/var/lib/btrfs is not writable'
>> +else
>> +    test -w /var/lib || _notrun '/var/lib/btrfs cannot be created'
>> +fi
>> +
> 
> We need to enhance this to  a common helper, as there are many test
> cases with the scrub command in them. I'll enhance it.

Hmm. No, for all the remaining test cases that use btrfs scrub start,
the output and its stderr are redirected to seqres.full. So, those test
cases will still pass. And, btrfs/282"is the only test case that
requires scrub status.

Thanks, Anand

> 
> However, for now, this patch is fine has been applied locally with
> commit log changes.
> 
> Reviewed-by: Anand Jain <anand.jain@oracle.com>
> 
> 
>>   _scratch_mkfs >> $seqres.full 2>&1
>>   _scratch_mount
> 


  reply	other threads:[~2023-08-29  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 23:47 [PATCH] btrfs/282: skip test if /var/lib/btrfs isnt writable Darrick J. Wong
2023-08-29  7:50 ` Anand Jain
2023-08-29  9:53   ` Anand Jain [this message]
2023-09-01 19:36 ` Zorro Lang
2023-09-02  0:40   ` Qu Wenruo
2023-09-02  5:46     ` Zorro Lang

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=35cc63b4-a52b-dee6-5e51-489402c20ae0@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=djwong@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zlang@redhat.com \
    /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