From: Tovo Rabemanantsoa <tovo.rabemanantsoa@bordeaux.inra.fr>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Problem with a filesystem
Date: Thu, 18 Sep 2014 15:42:08 +0200 [thread overview]
Message-ID: <541AE130.3070200@bordeaux.inra.fr> (raw)
In-Reply-To: <800A0C28-B668-4510-850E-DC92E67AD878@colorremedies.com>
On 09/17/2014 08:49 PM, Chris Murphy wrote:
>
> This isn't what I expect as a candidate for btrfs-zero-log, I don't know what the last message means. You could run a
> btrfs check <btrfsdev>
> and then ask about both the failure to read block groups -5 and also the btrfs check (without --repair) results
>
> Or take a leap of faith, take an image of the file system first as it might make recovery more difficult. If there are things you really need off this file system first you should look at https://btrfs.wiki.kernel.org/index.php/Restore before zeroing the log.
>
> btrfs-image -c 9 -t 8 <btrfsdev> /path/to/file
> btrfs-zero-log <btrfsdev>
>
>
> Chris Murphy
Well,
btrfs check ends also with a failed message.
In any ways, I think this FS corruption is due to a weakness of my raid
card. Indeed, before it happens, the kernel panicked because of this
card. The card claims that he had lost 2 disks from the pool but, just
removing them and plugging them again solved the error.
My thinking is that I didn't plug the two disks on the proper sequence.
So it corrupted the raid reconstruction process.
By the way, I don't have enough structure to host 26TB of an image.
Moreover, as it is our backup server, we need it to get back as soon as
possible.
What I'm gonna do, now, is to make a new file system instead and set up
everything one more time.
Thank you so much for helping me.
Tovo
prev parent reply other threads:[~2014-09-18 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 15:54 Problem with a filesystem Tovo Rabemanantsoa
2014-09-16 17:17 ` Chris Murphy
2014-09-16 20:11 ` Tovo Rabemanantsoa
2014-09-16 21:27 ` Chris Murphy
2014-09-17 9:06 ` Tovo Rabemanantsoa
2014-09-17 18:49 ` Chris Murphy
2014-09-18 13:42 ` Tovo Rabemanantsoa [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=541AE130.3070200@bordeaux.inra.fr \
--to=tovo.rabemanantsoa@bordeaux.inra.fr \
--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).