From: efkf@firemail.cc
To: linux-btrfs@vger.kernel.org
Subject: Tried to replace a drive in a raid 1 and all hell broke loose
Date: Mon, 23 May 2022 18:21:40 +0100 [thread overview]
Message-ID: <9a9d16a133c13bed724f2a6a406bd3b6@firemail.cc> (raw)
Hello, this is my first time interacting with a mailing list and the
first time actually using btrfs.
THE CURRENT SITUATION:
I think I have two working drives with dm-crypt in what i think is raid
1
when booted on a either fedora live disk or debian testing i can mount
the filesystem but check fails and scrub aborts.
-= FEDORA =-
The first time i scrub i get this on the kernel log: ( attachment
fedora_scrub_1 )
i unmounted, mounted and scrubbed again and got a different error: (
attachment fedora_scrub_2 )
check says this: ( attachment fedora_check )
This is the distro info: ( attachment fedora_info ))
-= DEBIAN TESTING =-
The first time i scrub i get this on the kernel log: ( attachment
debian_scrub1 )
I unmounted and got a call trace and register dump on the kernel log: (
attachment debian_unmount )
i mounted and scrubbed again and got a similar error to fedora's second
scrub: ( attachment debian_scrub2 )
check says the same thing
This is the distro info: ( attachment debian_info )
THE BACKSTORY:
here is a timeline of the events that lead up to this
(by the way, all of this was done with clean unmounts and reboots)
[ Using debian stable btrfs-progs 5.10.1-2 ]
- Btrfs raid 1 works great srubs ok with 2 drives
- One drive starts dying, i get one to replace it
- Add the new one to the array (with all three plugged in) (i now know i
should've use replace instead)
- run btrfs balance (with all three again)
- tried to delete the drive but failed (around this time i started
running into weird errors)
- updated debian to testing, updated kernel, rebooted ( btrgs-progs
5.10.1-2 -> 5.17-1 )
- managed to remove the failing drive (not sure if the update helped)
- Have to mount degraded and check shows a lot of errors
- bite the bullet and run check --repair, it says it is fixing errors
and at the end it says no errors
- run just check again and get the same errors as before roughly
- run check --repair again, gets stuck in what seems to be an infinite
loop. Says its fixing the same things again and again
- joined the irc channel to ask for help
- send sigterm to btrfs check --repair ( no one had replied by then)
- it actually mounts without needing -o degraded now
- get told to run 'btrfs fi us -T /mnt' and realize that i have both
raid1 and some small single chunks
- run btrfs balance start -mconvert=raid1,soft -dconvert=raid1,soft /mnt
- btrfs check shows much less errors and all single chunks are gone (
the btrfs check output at that point is attached as old_completing_check
on the email )
- try to run scrubs, they abort
- check and there are some single chunks yet again
- try fedora, run check and it gives the error i have attached and
doesn't go through with actually checking everything
- try debian again and now checking doesn't complete with the same error
as in fedora
I also tried running 'btrfs balance start -mconvert=raid1,soft
-dconvert=raid1,soft /mnt' again now and the first time I run it, it
says
ERROR: error during balancing '/mnt/sd': No such file or directory
and it the second time
ERROR: error during balancing '/mnt/sd': Read-only file system
Thanks a lot for reading my email and sorry if it winds up being
something not related to btrfs
next reply other threads:[~2022-05-23 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 17:21 efkf [this message]
[not found] ` <5fd50e9.def5d621.180f273d002@tnonline.net>
2022-05-23 20:00 ` Tried to replace a drive in a raid 1 and all hell broke loose efkf
2022-05-23 20:05 ` efkf
2022-05-24 6:51 ` efkf
2022-05-24 19:11 ` Chris Murphy
2022-05-27 15:13 ` efkf
2022-05-27 15:15 ` efkf
2022-05-27 15:25 ` Forza
2022-05-27 16:28 ` efkf
2022-05-27 21:37 ` Forza
2022-05-28 20:20 ` Nicholas D Steeves
2022-05-28 21:04 ` Forza
2022-05-29 20:48 ` efkf
2022-05-30 20:47 ` Forza
2022-05-30 21:59 ` Graham Cobb
2022-06-07 21:17 ` Nicholas D Steeves
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=9a9d16a133c13bed724f2a6a406bd3b6@firemail.cc \
--to=efkf@firemail.cc \
--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.