All of lore.kernel.org
 help / color / mirror / Atom feed
From: Spencer Collyer <spencer@lasermount.plus.com>
To: linux-btrfs@vger.kernel.org
Subject: Write time tree block corruption detected
Date: Wed, 12 Aug 2020 14:49:15 +0100	[thread overview]
Message-ID: <20200812144915.488db4c7@lasermount.plus.com> (raw)

I have just received a 'write time tree block corruption detected' message on a BTRFS fs I use. As per
https://btrfs.wiki.kernel.org/index.php/Tree-checker it mentions sending a mail to this mailing list for this case.

The dmesg output from the error onwards is as follows:

[17434.620469] BTRFS error (device dm-1): block=13642806624256 write time tree block corruption detected
[17435.048842] BTRFS: error (device dm-1) in btrfs_commit_transaction:2323: errno=-5 IO failure (Error while writing out transaction)
[17435.048848] BTRFS info (device dm-1): forced readonly
[17435.048851] BTRFS warning (device dm-1): Skipping commit of aborted transaction.
[17435.048853] BTRFS: error (device dm-1) in cleanup_transaction:1894: errno=-5 IO failure

As can be seen, the fs was forced into readonly mode. I restarted the box that the fs was mounted on and am able to write to the fs again (tried 'touch'ing a non-existent file and that worked), but I'm reluctant to do any more with it until I know it is safe to do so.

Is there anything I should do to ensure the fs is OK? The page I quoted earlier said not to run 'btrfs check --repair' unless told to by a developer.

Thanks for your attention.

Spencer

             reply	other threads:[~2020-08-12 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 13:49 Spencer Collyer [this message]
2020-08-12 14:15 ` Write time tree block corruption detected Qu Wenruo
2020-08-13  5:53   ` Spencer Collyer
2020-08-13  5:58     ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2021-05-30 21:30 auxsvr
2021-06-07 11:55 ` auxsvr
2021-06-08 14:45   ` auxsvr
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
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=20200812144915.488db4c7@lasermount.plus.com \
    --to=spencer@lasermount.plus.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 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.