From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Patrick Dijkgraaf <bolderbast@duckstad.net>, linux-btrfs@vger.kernel.org
Subject: Re: Need help: super_total_bytes mismatch with fs_devices total_rw_bytes
Date: Sat, 24 Aug 2019 19:01:05 +0800 [thread overview]
Message-ID: <211fbb73-6a16-a8a6-e2b3-a0799216fe9c@gmx.com> (raw)
In-Reply-To: <42e408bdd5b38305358c961e06c0afe250a00a90.camel@duckstad.net>
[-- Attachment #1.1: Type: text/plain, Size: 2701 bytes --]
On 2019/8/24 下午2:48, Patrick Dijkgraaf wrote:
> Hi all,
>
> My server hung this morning, and I had to hard-reset is. I did not
> apply any updates. After the reboot, my FS won't mount:
>
> [Sat Aug 24 08:16:31 2019] BTRFS error (device sde2): super_total_bytes
> 92017957797888 mismatch with fs_devices total_rw_bytes 184035915595776
> [Sat Aug 24 08:16:31 2019] BTRFS error (device sde2): failed to read
> chunk tree: -22
> [Sat Aug 24 08:16:31 2019] BTRFS error (device sde2): open_ctree failed
>
> However, running btrfs rescue shows:
> root@cornelis ~]# btrfs rescue fix-device-size /dev/sdh2
> No device size related problem found
That's strange.
Would you please dump the chunk tree and super blocks?
# btrfs ins dump-super -fFa /dev/sdh2
# btrfs ins dump-tree -t chunk /dev/sdh2
And, have you tried to mount using different devices? If it's some super
blocks get corrupted, using a different device to mount may help.
(With that said, it's better to call that dump-super for each device)
>
> FS config is shown below:
> [root@cornelis ~]# btrfs fi show
> Label: 'cornelis-btrfs' uuid: ac643516-670e-40f3-aa4c-f329fc3795fd
> Total devices 1 FS bytes used 536.05GiB
> devid 1 size 800.00GiB used 630.02GiB path /dev/mapper/cornelis-
> cornelis--btrfs
>
> Label: 'data' uuid: 43472491-7bb3-418c-b476-874a52e8b2b0
> Total devices 16 FS bytes used 36.61TiB
> devid 1 size 7.28TiB used 2.65TiB path /dev/sde2
> devid 2 size 3.64TiB used 2.65TiB path /dev/sdf2
> devid 3 size 3.64TiB used 2.65TiB path /dev/sdg2
> devid 4 size 7.28TiB used 2.65TiB path /dev/sdh2
> devid 5 size 3.64TiB used 2.65TiB path /dev/sdi2
> devid 6 size 7.28TiB used 2.65TiB path /dev/sdj2
> devid 7 size 3.64TiB used 2.65TiB path /dev/sdk2
> devid 8 size 3.64TiB used 2.65TiB path /dev/sdl2
> devid 9 size 7.28TiB used 2.65TiB path /dev/sdm2
> devid 10 size 3.64TiB used 2.65TiB path /dev/sdn2
> devid 11 size 7.28TiB used 2.65TiB path /dev/sdo2
> devid 12 size 3.64TiB used 2.65TiB path /dev/sdp2
> devid 13 size 7.28TiB used 2.65TiB path /dev/sdq2
> devid 14 size 7.28TiB used 2.65TiB path /dev/sdr2
> devid 15 size 3.64TiB used 2.65TiB path /dev/sds2
> devid 16 size 3.64TiB used 2.65TiB path /dev/sdt2
What's the profile used on so many devices?
RAID10?
The simplest way to fix it is to just update the
Thanks,
Qu
>
> Other info:
> [root@cornelis ~]# uname -r
> 4.18.16-arch1-1-ARCH
>
> I was able to mount is using:
> [root@cornelis ~]# mount -o usebackuproot,ro /dev/sdh2 /mnt/data
>
> Now updating my backup, but I REALLY hope to get this fixed on the
> production server!
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-24 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 6:48 Need help: super_total_bytes mismatch with fs_devices total_rw_bytes Patrick Dijkgraaf
2019-08-24 11:01 ` Qu Wenruo [this message]
2019-08-24 12:05 ` Patrick Dijkgraaf
2019-08-24 13:24 ` Qu Wenruo
2019-08-25 6:41 ` Patrick Dijkgraaf
2019-08-25 13:36 ` 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=211fbb73-6a16-a8a6-e2b3-a0799216fe9c@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=bolderbast@duckstad.net \
--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).