From: Andy Smith <andy@strugglers.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: One missing device = fs not detected; upgrade things first?
Date: Mon, 29 Jan 2024 18:02:51 +0000 [thread overview]
Message-ID: <ZbfoS8C0+WdTBfhl@mail.bitfolk.com> (raw)
In-Reply-To: <ZbfkaXaX0Wmef0VW@mail.bitfolk.com>
On Mon, Jan 29, 2024 at 05:46:17PM +0000, Andy Smith wrote:
> # btrfs check -p /dev/sde
> Opening filesystem to check...
> Checking filesystem on /dev/sde
> UUID: 472ee2b3-4dc3-4fc1-80bc-5ba967069ceb
> [1/7] checking root items (0:07:57 elapsed, 3055030 items checked)
> [2/7] checking extents (0:08:54 elapsed, 1334143 items checked)
> failed to load free space cache for block group 15011172843520d, 1 items checked)
> failed to load free space cache for block group 15012246585344
> [lots more of that]
> [3/7] checking free space cache (0:05:04 elapsed, 4220 items checked)
> [4/7] checking fs roots (0:51:38 elapsed, 126792 items checked)
> [5/7] checking csums (without verifying data) (0:13:45 elapsed, 2123139 items checked)
>
> (still going)
It just finished. Here was the remaining output:
[5/7] checking csums (without verifying data) (0:30:31 elapsed, 5327794 items checked)
[6/7] checking root refs (0:00:00 elapsed, 18 items checked)
[7/7] checking quota groups skipped (not enabled on this FS)
found 4088505802752 bytes used, no error found
total csum bytes: 3983137248
total tree bytes: 5464555520
total fs tree bytes: 526884864
total extent tree bytes: 364138496
btree space waste bytes: 525763765
file data blocks allocated: 4135503101952
referenced 4101458530304
I didn't see anything bad except the mass of "failed to load free
space cache for block group …". Is there anything that is safe to
try without newer kernel and btrfs-progs?
Thanks,
Andy
next prev parent reply other threads:[~2024-01-29 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 17:46 One missing device = fs not detected; upgrade things first? Andy Smith
2024-01-29 18:02 ` Andy Smith [this message]
2024-01-29 18:24 ` Remi Gauvin
2024-01-29 21:41 ` Andy Smith
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=ZbfoS8C0+WdTBfhl@mail.bitfolk.com \
--to=andy@strugglers.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 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.