From: claudius@winca.de
To: linux-btrfs@vger.kernel.org
Subject: BTRFS recovery not possible
Date: Tue, 11 Jun 2019 12:53:21 +0200 [thread overview]
Message-ID: <75a6f0280fb5829b0701f42c24a2356e@winca.de> (raw)
HI Guys,
you are my last try. I was so happy to use BTRFS but now i really hate
it....
Linux CIA 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
btrfs-progs v4.15.1
btrfs fi show
Label: none uuid: 9622fd5c-5f7a-4e72-8efa-3d56a462ba85
Total devices 1 FS bytes used 4.58TiB
devid 1 size 7.28TiB used 4.59TiB path /dev/mapper/volume1
dmesg
[57501.267526] BTRFS info (device dm-5): trying to use backup root at
mount time
[57501.267528] BTRFS info (device dm-5): disk space caching is enabled
[57501.267529] BTRFS info (device dm-5): has skinny extents
[57507.511830] BTRFS error (device dm-5): parent transid verify failed
on 2069131051008 wanted 4240 found 5115
[57507.518764] BTRFS error (device dm-5): parent transid verify failed
on 2069131051008 wanted 4240 found 5115
[57507.519265] BTRFS error (device dm-5): failed to read block groups:
-5
[57507.605939] BTRFS error (device dm-5): open_ctree failed
btrfs check /dev/mapper/volume1
parent transid verify failed on 2069131051008 wanted 4240 found 5115
parent transid verify failed on 2069131051008 wanted 4240 found 5115
parent transid verify failed on 2069131051008 wanted 4240 found 5115
parent transid verify failed on 2069131051008 wanted 4240 found 5115
Ignoring transid failure
extent buffer leak: start 2024985772032 len 16384
ERROR: cannot open file system
im not able to mount it anymore.
I found the drive in RO the other day and realized somthing was wrong
... i did a reboot and now i cant mount anmyore
any help
next reply other threads:[~2019-06-11 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 10:53 claudius [this message]
2019-06-11 13:02 ` BTRFS recovery not possible Qu Wenruo
2019-06-15 22:05 ` Claudius Winkel
2019-06-19 23:45 ` Zygo Blaxell
2019-06-20 5:00 ` 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=75a6f0280fb5829b0701f42c24a2356e@winca.de \
--to=claudius@winca.de \
--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;
as well as URLs for NNTP newsgroup(s).