From: Roman Mamedov <rm@romanrm.net>
To: Evan Zimmerman <wolfblitz98@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS - Error After Power Outage
Date: Thu, 26 Aug 2021 02:53:58 +0500 [thread overview]
Message-ID: <20210826025358.7cba5c44@natsu> (raw)
In-Reply-To: <CA+9Jo8u1RbB=pzPj6bpAYLc5BGaZe2S17s-SxA8t+bm-D=wj-g@mail.gmail.com>
On Wed, 25 Aug 2021 14:50:18 -0700
Evan Zimmerman <wolfblitz98@gmail.com> wrote:
> Hello!
>
> I have a multi device btrfs array of 6 devices that is timing out or
> otherwise failing to mount on boot causing me to enter recovery mode,
> though I can manually mount the drives in recovery mode and can still
> see my data.
>
> I was working in my house the other day, when our power had gone out.
> I turned my Debian server back on and it started up in emergency mode
> saying BTRFS error: open_ctree failed. I also got a "failed to mount
> /mnt/data", which is where I have my data.
>
> Now, I've had a similar problem before where I believe one of my
> EasyStore drives was taking too long to be read from and causing
> Debian to boot into emergency mode, but after restarting it a few
> times, it would manage to finally boot up. This "fix" is not working
> this time around and I fear something corrupted during that power
> outage.
>
> I'm hoping to get some advice on this to see what I can do to get
> things up and running again. Now, trying to mount manually actually
> worked in emergency mode. Thank you in advance for any help you all
> can provide!
>
> # uname -a
> Linux [server_name] 5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2020-12-17)
> x86_64 GNU/Linux
>
> # btrfs --version
> btrfs-progs v5.9
>
> # btrfs fi show
> Label: 'Media' uuid: c29b9859-ae32-4be2-ad28-9193c9ebcc87
> Total devices 6 FS bytes used 28.24TiB
> devid 1 size 10.91TiB used 9.80TiB path /dev/sdd
> devid 2 size 2.73TiB used 2.68TiB path /dev/sdc
> devid 3 size 3.64TiB used 3.58TiB path /dev/sdb
> devid 4 size 2.73TiB used 2.67TiB path /dev/sde
> devid 5 size 2.73TiB used 1.61TiB path /dev/sdf
> devid 6 size 9.10TiB used 7.98TiB path /dev/sdg
>
> # dmesg | grep btrfs
Are you sure it's the actual and complete output of the command?
"grep btrfs" without -i would not have returned any of those lines.
And most importantly it looks as if a few might be missing, better just post
the entire dmesg.
> [ 16.106923] BTRFS: device label Media devid 6 transid 3072649
> /dev/sdg scanned by systemd-udevd (301)
> [ 16.492767] BTRFS info (device sdd): setting incompat feature flag
> for COMPRESS_ZSTD (0x10)
> [ 16.492768] BTRFS info (device sdd): force zstd compression, level 2
> [ 16.492768] BTRFS info (device sdd): using free space tree
> [ 16.492769] BTRFS info (device sdd): has skinny extents
> [ 114.864229] BTRFS error (device sdd): open_ctree failed
--
With respect,
Roman
next prev parent reply other threads:[~2021-08-25 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 21:50 BTRFS - Error After Power Outage Evan Zimmerman
2021-08-25 21:53 ` Roman Mamedov [this message]
[not found] ` <CA+9Jo8uye5N-cj+70mVx_6AfgWHwWqYJjrzCU9jkbATK+_U0QA@mail.gmail.com>
2021-08-25 22:03 ` Roman Mamedov
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=20210826025358.7cba5c44@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=wolfblitz98@gmail.com \
/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).