From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Mike Aubury <mike@aubit.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Meta data full on a Readynas
Date: Thu, 27 Aug 2015 11:43:50 -0600 [thread overview]
Message-ID: <CAJCQCtQ8YXR4mkFFnrDcfiHB4qi2B2uNT2AtqNQQ6noS_rP95A@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQzTt14UDKKK996U-CRznvzL8JxnkkRWC=WfxmqDCbsOQ@mail.gmail.com>
On Thu, Aug 27, 2015 at 11:41 AM, Chris Murphy <lists@colorremedies.com> wrote:
> On Thu, Aug 27, 2015 at 11:33 AM, Mike Aubury <mike@aubit.com> wrote:
>> # btrfs dev scan
>> Scanning for Btrfs filesystems
>>
>> (back to # prompt)
>>
>>
>> # mount -o ro,degraded /data
>>
>>
>> Seems to work, /data is mounted
>>
>> # btrfs fi show
>> Label: '0e36d290:data' uuid: e75a9856-d9e5-4d02-92e6-a217056c69b7
>> Total devices 4 FS bytes used 6.09TiB
>> devid 1 size 2.71TiB used 2.71TiB path /dev/md127
>> devid 2 size 1.82TiB used 1.82TiB path /dev/md126
>> devid 3 size 1.82TiB used 1.82TiB path /dev/md125
>> *** Some devices missing
>>
>>
>> Where next ?
Well now at least you can suck the data off the volume...
If you can't figure out why the loop back mount device continues to be
missing, you might as well just take advantage of the fact you've got
it ro mounted and get everything off the volume in preparation to wipe
it and start over.
--
Chris Murphy
prev parent reply other threads:[~2015-08-27 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 10:02 Meta data full on a Readynas Mike Aubury
2015-08-27 16:23 ` Chris Murphy
2015-08-27 16:35 ` Mike Aubury
2015-08-27 16:55 ` Chris Murphy
[not found] ` <CAGAq4WF1-aeLHzz25WjqnrP9wrfjERFy+MqdTK5nbqfg6c5xcA@mail.gmail.com>
2015-08-27 17:27 ` Chris Murphy
2015-08-27 17:33 ` Mike Aubury
2015-08-27 17:41 ` Chris Murphy
2015-08-27 17:43 ` 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=CAJCQCtQ8YXR4mkFFnrDcfiHB4qi2B2uNT2AtqNQQ6noS_rP95A@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mike@aubit.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).