Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck failes
Date: Wed, 15 Jan 2014 07:08:09 -0800	[thread overview]
Message-ID: <20140115150809.GH10639@merlins.org> (raw)
In-Reply-To: <A76390BF-4D85-47D3-A332-AD09809F6632@colorremedies.com>

On Mon, Jan 13, 2014 at 05:37:31PM -0700, Chris Murphy wrote:
> 
> On Jan 13, 2014, at 3:58 PM, Holger Brandsmeier <brandsmeier@gmail.com> wrote:
> > 
> > Currently btrfsck failes to repair my partition, I get the output:
> > 
> > [root@ho-think bholger]# btrfsck --repair /dev/sda5
> 
> This is almost the last resort and you probably should be posting to the list before using repair.

A reminder about my previous comment that brtfsck should really give
better usage info and --force or --really-try-to-fsck  ;)

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2014-01-15 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 22:58 btrfsck failes Holger Brandsmeier
2014-01-13 23:15 ` Holger Brandsmeier
2014-01-13 23:53   ` Holger Brandsmeier
2014-01-14  0:37 ` Chris Murphy
2014-01-15 15:08   ` Marc MERLIN [this message]
2014-01-15 16:15   ` Mitch Harder
2014-01-15 17:16     ` Chris Murphy
2014-01-16 12:19       ` Marc MERLIN
2014-01-16 20:30         ` Holger Brandsmeier
     [not found] <CAFP7zVtDEfDjKA1GvBq_QMs6gKv9t=K_qNyv6dcxawe5iuj8Kw@mail.gmail.com>
2014-01-15  4:06 ` Chris Murphy
     [not found]   ` <CAFP7zVuB=A2Lty275-VdixjzG6twXKmJo0qB3gZEH=9noQbpRQ@mail.gmail.com>
2014-01-15  7:53     ` Fwd: " Holger Brandsmeier
2014-01-15 15:15       ` Marc MERLIN
2014-01-15 17:07         ` Chris Murphy

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=20140115150809.GH10639@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox