From: jane <jane@janeirl.dev>
To: linux-btrfs@vger.kernel.org
Subject: Re: fs forced readonly
Date: Mon, 25 Mar 2024 23:09:30 -0500 [thread overview]
Message-ID: <43720730-b1fd-4779-8514-20eda1dff0a3@janeirl.dev> (raw)
In-Reply-To: <bdcc14cf-7e12-4ae7-92c6-a4924158ea64@janeirl.dev>
On 3/25/24 23:00, jane wrote:
> btrfs-scrub output:
> UUID: 8b26e8c1-2566-4991-a0c4-e64da9a46607
> Scrub started: Mon Mar 25 22:59:39 2024
> Status: running
apologies i pasted the unfinished output. the finished one's here:
UUID: 8b26e8c1-2566-4991-a0c4-e64da9a46607
Scrub started: Mon Mar 25 23:03:21 2024
Status: finished
Duration: 0:05:27
Total to scrub: 115.05GiB
Rate: 360.29MiB/s
Error summary: no errors found
next prev parent reply other threads:[~2024-03-26 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 4:00 fs forced readonly jane
2024-03-26 4:09 ` jane [this message]
2024-03-26 4:19 ` Qu Wenruo
2024-03-27 3:52 ` jane
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=43720730-b1fd-4779-8514-20eda1dff0a3@janeirl.dev \
--to=jane@janeirl.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox