From: Roman Mamedov <rm@romanrm.net>
To: Marcel Bischoff <marcel@herrbischoff.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Too many missing devices, writeable mount is not allowed
Date: Sat, 26 Sep 2015 12:46:26 +0500 [thread overview]
Message-ID: <20150926124626.6aee7e52@natsu> (raw)
In-Reply-To: <20150925214544.GB4639@herrbischoff.com>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
On Fri, 25 Sep 2015 23:45:44 +0200
Marcel Bischoff <marcel@herrbischoff.com> wrote:
> Hello all,
>
> I have kind of a serious problem with one of my disks.
>
> The controller of one of my external drives died (WD Studio). The disk
> is alright though. I cracked open the case, got the drive out and
> connected it via a SATA-USB interface.
>
> Now, mounting the filesystem is not possible. Here's the message:
>
> $ btrfs fi show
> warning devid 3 not found already
> Label: none uuid: bd6090df-5179-490e-a5f8-8fbad433657f
> Total devices 3 FS bytes used 3.02TiB
> devid 1 size 596.17GiB used 532.03GiB path /dev/sdd
> devid 2 size 931.51GiB used 867.03GiB path /dev/sde
> *** Some devices missing
>
> Yes, I did bundle up three drives with very different sizes with the
> --single option on creating the file system.
>
> I have already asked for help on StackExchange but replies have been
> few. Now I thought people on this list, close to btrfs development may
> be able and willing to help. This would be so much appreciated.
>
> Here's the issue with lots of information and a record of what I/we have
> tried up until now:
> http://unix.stackexchange.com/questions/231174/btrfs-too-many-missing-devices-writeable-mount-is-not-allowed
What I find confusing about that post, is ...okay, sdd and sde are in the
filesystem alright. But which drive is the problematic one? You never
explicitly mention that. Then you proceed to post xxd dumps of sdb(!), and
also "strings | grep" and partition listing of sdc(!!!). So which is it, sdb
or sdc, or are you unsure at this point.
Also post stuff directly to the mailing list, as websites go away with time,
whereas the mail archives can be more resilient. (Not to mention asking things
like these on "stackoverflow" is a bit like expecting a useful answer on
Ubuntu Forums).
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-09-26 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 21:45 Too many missing devices, writeable mount is not allowed Marcel Bischoff
2015-09-25 22:43 ` Hugo Mills
2015-09-26 0:34 ` Duncan
2015-09-26 7:46 ` Roman Mamedov [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=20150926124626.6aee7e52@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcel@herrbischoff.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;
as well as URLs for NNTP newsgroup(s).