All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: raid 1 filesystem corruption
Date: Mon, 18 Feb 2019 16:23:27 -0700	[thread overview]
Message-ID: <CAJCQCtSc8dF6K8GGCp+kxXYj1PjpJ4qpcabFzYUx02JaVQK_ng@mail.gmail.com> (raw)
In-Reply-To: <CAAD7_rAk=iArkpSHeTRv7uv1tFz5nEh2qGEb7nixujLXcmhxxw@mail.gmail.com>

> Am Mo., 18. Feb. 2019 um 23:35 Uhr schrieb Rudolf Kastl <che666@gmail.com>:
> >
> > I tried a btrfs check --repair on sda2:

OK I think this is a risky decision, hopefully it works out though.

a. There's corruption and IO error we don't understand the source of
yet. Repairs can make problems much worse if the source of corruption
happens during repair.

b. from the 'man btrfs check' page
           Warning
           Do not use --repair unless you are advised to do so by a
developer or an experienced user, and then only after having accepted
that no fsck successfully repair all types of filesystem corruption.
Eg. some other software or hardware bugs can fatally damage a volume.


-- 
Chris Murphy

      parent reply	other threads:[~2019-02-18 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 21:19 raid 1 filesystem corruption Rudolf Kastl
2019-02-18 21:30 ` Chris Murphy
     [not found]   ` <CAAD7_rBSYJ_Srcsuf--0YMXW3xd3SVdECzmH=BroOwu9YTnTjg@mail.gmail.com>
     [not found]     ` <CAJCQCtQknb1qDusDY-iS2n_u5ywqFD4N-nKXBEJs0czEZS3b2w@mail.gmail.com>
     [not found]       ` <CAAD7_rArVnFS=s53x2aWR==VYi6eS-OOYvBihxhOickxCxfNOg@mail.gmail.com>
     [not found]         ` <CAAD7_rAk=iArkpSHeTRv7uv1tFz5nEh2qGEb7nixujLXcmhxxw@mail.gmail.com>
2019-02-18 23:23           ` Chris Murphy [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=CAJCQCtSc8dF6K8GGCp+kxXYj1PjpJ4qpcabFzYUx02JaVQK_ng@mail.gmail.com \
    --to=lists@colorremedies.com \
    --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.