From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Zorro Lang <zlang@redhat.com>, "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs/282: skip test if /var/lib/btrfs isnt writable
Date: Sat, 2 Sep 2023 08:40:17 +0800 [thread overview]
Message-ID: <f7925e65-5d8a-43b4-962c-07e1050abaad@gmx.com> (raw)
In-Reply-To: <20230901193609.yy7isx4pv6ax4g2k@zlang-mailbox>
On 2023/9/2 03:36, Zorro Lang wrote:
> On Thu, Aug 24, 2023 at 04:47:14PM -0700, Darrick J. Wong wrote:
>> From: Darrick J. Wong <djwong@kernel.org>
>>
>> I run fstests in a readonly container, and accidentally uninstalled the
>> btrfsprogs package. When I did, this test started faililng:
>>
>> --- btrfs/282.out
>> +++ btrfs/282.out.bad
>
> I can't merge this patch, it fails:
>
> Applying: btrfs/282: skip test if /var/lib/btrfs isnt writable
> error: 282.out: does not exist in index
> Patch failed at 0001 btrfs/282: skip test if /var/lib/btrfs isnt writable
> ...
>
> How can you generate this patch with btrfs/282.out.bad?
It's the diff format in the commit message confusing "git am".
You can add extra space(s) in the commit message so that "git am" can
understand what's going on.
Thanks,
Qu
>
> Thanks,
> Zorro
>
>> @@ -1,3 +1,7 @@
>> QA output created by 282
>> wrote 2147483648/2147483648 bytes at offset 0
>> XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>> +WARNING: cannot create scrub data file, mkdir /var/lib/btrfs failed: Read-only file system. Status recording disabled
>> +WARNING: failed to open the progress status socket at /var/lib/btrfs/scrub.progress.3e1cf8c6-8f8f-4b51-982c-d6783b8b8825: No such file or directory. Progress cannot be queried
>> +WARNING: cannot create scrub data file, mkdir /var/lib/btrfs failed: Read-only file system. Status recording disabled
>> +WARNING: failed to open the progress status socket at /var/lib/btrfs/scrub.progress.3e1cf8c6-8f8f-4b51-982c-d6783b8b8825: No such file or directory. Progress cannot be queried
>>
>> Skip the test if /var/lib/btrfs isn't writable, or if /var/lib isn't
>> writable, which means we cannot create /var/lib/btrfs.
>>
>> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
>> ---
>> tests/btrfs/282 | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/tests/btrfs/282 b/tests/btrfs/282
>> index 980262dcab..395e0626da 100755
>> --- a/tests/btrfs/282
>> +++ b/tests/btrfs/282
>> @@ -19,6 +19,13 @@ _wants_kernel_commit eb3b50536642 \
>> # We want at least 5G for the scratch device.
>> _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
>> +
>> _scratch_mkfs >> $seqres.full 2>&1
>> _scratch_mount
>>
>>
>
next prev parent reply other threads:[~2023-09-02 0:40 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
2023-09-01 19:36 ` Zorro Lang
2023-09-02 0:40 ` Qu Wenruo [this message]
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=f7925e65-5d8a-43b4-962c-07e1050abaad@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=djwong@kernel.org \
--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