From: auxsvr <auxsvr@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Write time tree block corruption detected
Date: Tue, 08 Jun 2021 17:45:10 +0300 [thread overview]
Message-ID: <4655545.31r3eYUQgx@localhost.localdomain> (raw)
In-Reply-To: <3113674.aeNJFYEL58@localhost.localdomain>
On Monday, 7 June 2021 14:55:10 EEST you wrote:
> It seems that every time free space is less than 1 GiB and I use zypper, I get a similar corruption message.
Correction: I just got:
[26355.330817] BTRFS critical (device sda2): corrupt leaf: root=3 block=537007243264 slot=0 devid=1 invalid bytes used: have 64503152640 expect [0, 64424509440]
[26355.330819] BTRFS error (device sda2): block=537007243264 write time tree block corruption detected
and:
# btrfs fi df /
Data, single: total=55.98GiB, used=43.04GiB
System, single: total=32.00MiB, used=16.00KiB
Metadata, single: total=2.00GiB, used=1.17GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
# btrfs fi show /
Label: none uuid: 44c67fa4-e2c4-4da5-9d07-98959ff77bc4
Total devices 1 FS bytes used 44.22GiB
devid 1 size 60.00GiB used 60.07GiB path /dev/sda2
60.07GiB used again!
Regards,
Petros
next prev parent reply other threads:[~2021-06-08 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 21:30 Write time tree block corruption detected auxsvr
2021-06-07 11:55 ` auxsvr
2021-06-08 14:45 ` auxsvr [this message]
2021-06-08 22:39 ` Qu Wenruo
2021-06-09 1:05 ` Qu Wenruo
2021-06-09 8:04 ` auxsvr
2021-06-09 8:32 ` Qu Wenruo
2021-06-11 19:44 ` auxsvr
-- strict thread matches above, loose matches on Subject: below --
2020-08-12 13:49 Spencer Collyer
2020-08-12 14:15 ` Qu Wenruo
2020-08-13 5:53 ` Spencer Collyer
2020-08-13 5:58 ` Qu Wenruo
2020-01-17 8:21 write " Kenneth Topp
2020-01-17 8:33 ` Qu Wenruo
2020-01-17 8:48 ` Kenneth Topp
2020-01-17 10:09 ` Qu Wenruo
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=4655545.31r3eYUQgx@localhost.localdomain \
--to=auxsvr@gmail.com \
--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