Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: William Rotach <wrotach1@binghamton.edu>, linux-btrfs@vger.kernel.org
Subject: Re: file system failure after hard reboot support request
Date: Sun, 2 Jun 2024 12:59:12 +0930	[thread overview]
Message-ID: <66fafc1b-3339-4336-a715-eb744d93155c@gmx.com> (raw)
In-Reply-To: <51b057bf-ce55-4649-a70d-a7b4c7b8981d@binghamton.edu>



在 2024/6/2 11:30, William Rotach 写道:
>
>    I have reached out to a couple different locations for help with
> BTRFS, and I have reached a dead end at my google-foo, and my
> distributions discussion boards.  If there is a better place to ask for
> help with respect to a hard file system crash, please let me know.
>    I have a corrupted BTRFS file system, with a quick summary in bullet
> points:
> -    single new NVME, 6 months old, 2Tb size, 1Tb used, 200Mb of really
> needed stuff
> -    one backup exists, 6 months old, still need the new copies of above
> needed files
> -    Fedora 39
> -    chromium, high tab count, apparent culprit
> -    hard system lock (no ssh response, no console switching)
> -    repeated hard system restarts, last one crashed btrfs file system
> -    btrfs hard failures:
> -        parent transid;
> -        checksum;
> -        bytenr;
> -        search for next directory;
> -        can't read tree root;
> -        bad tree block start;
> -        212 found roots, none seem to have a "good match", as noted above

Full "btrfs check --readonly" output please, not some truncated output.

Meanwhile you can try "-o rescue=all,ro mount" option to see if it can
mount, and the dmesg for such attempt.

But according to the "can't read tree root" line, rescue mount may not help.

Thanks,
Qu
>
>    I started looking into the kernel driver source code to help my
> understanding of the physical layout, and may build a more forensic
> method of retrieving the binary/text data that I need.  I hope there is
> something that is already included in the btrfs-progs packaging,
> available through the source code, or by the developer team itself.
>

  reply	other threads:[~2024-06-02  3:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  2:00 file system failure after hard reboot support request William Rotach
2024-06-02  3:29 ` Qu Wenruo [this message]
2024-06-02 14:53   ` [External Email] " William Rotach
2024-06-02 22:34     ` 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=66fafc1b-3339-4336-a715-eb744d93155c@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wrotach1@binghamton.edu \
    /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