linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladi Gergov <vgergov@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs raid1 degraded does not mount or fsck
Date: Fri, 29 Oct 2010 13:53:42 -0700	[thread overview]
Message-ID: <20101029205340.GA10326@gypsyops.denof.sin> (raw)

kernel: scratch git repo from today 10.29.10 @ 14:30 PST
Btrfs v0.19-35-g1b444cd-dirty

>>> gypsyops @ /mnt > sudo btrfs filesystem show
Label: 'das4'  uuid: d0e5137f-e5e7-49da-91f6-a9c4e4e72c6f
    Total devices 3 FS bytes used 1.38TB
    devid    3 size 1.82TB used 0.00 path /dev/sdb
    devid    2 size 1.82TB used 1.38TB path /dev/sdc
    *** Some devices missing

Btrfs v0.19-35-g1b444cd-dirty

>>> gypsyops @ /mnt > sudo mount -o degraded /dev/sdc das3/
Password: 
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[  684.577540] device label das4 devid 2 transid 107954 /dev/sdc
[  684.595150] btrfs: allowing degraded mounts
[  684.595594] btrfs: failed to read chunk root on sdb
[  684.604110] btrfs: open_ctree failed

>>> gypsyops @ /mnt > sudo btrfsck /dev/sdc
btrfsck: volumes.c:1367: btrfs_read_sys_array: Assertion `!(ret)' failed.

any help please?

-- 

,-| Vladi
`-| Gergov

!DSPAM:4ccb39a9191821603519226!



             reply	other threads:[~2010-10-29 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 20:53 Vladi Gergov [this message]
2010-10-30  6:55 ` btrfs raid1 degraded does not mount or fsck Goffredo Baroncelli
2010-11-16 21:50 ` Chris Mason
2011-10-10  4:42   ` Larry Reaves
2012-09-17 20:38 ` btrfs raid1 degraded in need of chuck tree rebuild Vladi Gergov
2016-04-09 22:44 btrfs raid1 degraded does not mount or fsck Vladi Gergov
2016-04-10  6:55 ` Duncan

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=20101029205340.GA10326@gypsyops.denof.sin \
    --to=vgergov@gmail.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 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).