From: Andy Smith <andy@strugglers.net>
To: Remi Gauvin <remi@georgianit.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: One missing device = fs not detected; upgrade things first?
Date: Mon, 29 Jan 2024 21:41:24 +0000 [thread overview]
Message-ID: <ZbgbhHDCtiNHSlQL@mail.bitfolk.com> (raw)
In-Reply-To: <3f3dcc01-6d23-4490-7b8d-98eff520bc85@georgianit.com>
Hi Remi,
On Mon, Jan 29, 2024 at 01:24:09PM -0500, Remi Gauvin wrote:
> That is what lsblk output looks like to me. There is no filesystem
> information in the output. Are you confusing lsblk and blkid?
Maybe. But see later…
> > Should I build new btrfs-progs and then a new kernel and just boot
> > with those to see what happens, and then try the check --repair? Or
> > should I just build the new kernel and see what that makes of the
> > devices first, then build new btrfs-tools if I am still to run
> > check?
>
> I would suggest the output of btrfs filesystem show, as well as the
> exact mount command and any dmesg output when mount command is run.
Hmm,. strange. Now:
# btrfs fi sh
Label: 'tank' uuid: 472ee2b3-4dc3-4fc1-80bc-5ba967069ceb
Total devices 7 FS bytes used 3.72TiB
devid 5 size 2.73TiB used 2.44TiB path /dev/sdj
devid 6 size 1.82TiB used 1.53TiB path /dev/sdf
devid 8 size 931.51GiB used 839.00GiB path /dev/sdh
devid 9 size 931.51GiB used 857.00GiB path /dev/sde
devid 10 size 1.75TiB used 1.67TiB path /dev/sdg
devid 12 size 1.75TiB used 548.50GiB path /dev/sdi
*** Some devices missing
# mount -t btrfs -odegraded /dev/sde /srv/tank
(long pause, but eventually worked)
Logged:
2024-01-29T21:14:01.748805+00:00 specialbrew.localnet kernel: [19014.852866] BTRFS info (device sdj): allowing degraded mounts
2024-01-29T21:14:01.748874+00:00 specialbrew.localnet kernel: [19014.852873] BTRFS info (device sdj): disk space caching is enabled
2024-01-29T21:14:01.768772+00:00 specialbrew.localnet kernel: [19014.866523] BTRFS warning (device sdj): devid 11 uuid 296b4aa0-434d-408e-8b8b-f11d93186a11 is missing
2024-01-29T21:14:01.768772+00:00 specialbrew.localnet kernel: [19014.866523] BTRFS warning (device sdj): devid 11 uuid 296b4aa0-434d-408e-8b8b-f11d93186a11 is missing
2024-01-29T21:14:03.512856+00:00 specialbrew.localnet kernel: [19016.615549] BTRFS info (device sdj): bdev (null) errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Admittedly I did not try "btrfs filesystem show" before, as the
complete lack of spotting an fs on there, and "btrfs dev scan"
seemingly doing nothing threw me a bit. But I DID try a mount
before, which failed saying it couldn't find a superblock. Yet now
it seems to have worked okay.
Everything seems alright, I just need to work out what happened with
that one drive.
As for lsblk, it now says:
# lsblk
sde 8:64 0 931.5G 0 disk
sdf 8:80 0 1.8T 0 disk
sdg 8:96 0 1.8T 0 disk
sdh 8:112 0 931.5G 0 disk
sdi 8:128 0 1.8T 0 disk
sdj 8:144 0 2.7T 0 disk /srv/tank
but I suppose only because that is now mounted.
Thanks!
Andy
prev parent reply other threads:[~2024-01-29 21:41 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
2024-01-29 18:24 ` Remi Gauvin
2024-01-29 21:41 ` Andy Smith [this message]
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=ZbgbhHDCtiNHSlQL@mail.bitfolk.com \
--to=andy@strugglers.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.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 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.