From: cwillu <cwillu@cwillu.com>
To: Diwaker Gupta <diwaker@maginatics.com>
Cc: Hubert Kario <hka@qbs.com.pl>, linux-btrfs@vger.kernel.org
Subject: Re: Error mounting multi-device fs after restart
Date: Tue, 8 Feb 2011 16:04:58 -0600 [thread overview]
Message-ID: <AANLkTi=rG+NODydGFUNr_LsMgJZ7=B1ae3H7reDOr-pp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=a2D+NnF5m6iE3m=tmDQK+HRRa0pPm004hsdNV@mail.gmail.com>
On Tue, Feb 8, 2011 at 3:59 PM, Diwaker Gupta <diwaker@maginatics.com> wrote:
>> Define *indefinitely*.
>
> Meaning the messages continued for as long as the system was under observation.
>
>> Are the drives not working?
>
> I believe they are. Working in the sense that I can read off data
> using 'dd', I can inspect partition tables etc.
>
>> If the drives are working, have you tried waiting 2-3 days, possibly longer?
>> 10TB is a *lot* of data
>
> The system was running overnight when I first hit the problem. On
> subsequent reboots, I've only waited less than half an hour. Usually
> the mount is instantaneous, so I wasn't sure if waiting would help at
> all. The error messages did not indicate that the system could recover
> at that stage. If there's even a slight chance that the fs would
> eventually mount, I'm happy to let it run for a day or two. Note that
> if I mount using the 'degraded' option, the mount succeeds but
> subsequent attempts to read the data fail.
Huh. How do those attempts fail?
Try mounting ro, or degraded,ro, and reading the data off. That
worked for me recently on a broken btrfs raid10 (and didn't on another
one, so your mileage may vary).
There's also the perpetually imminent fsck development which might save the day.
next prev parent reply other threads:[~2011-02-08 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 19:46 Error mounting multi-device fs after restart Diwaker Gupta
2011-02-08 20:25 ` Diwaker Gupta
2011-02-08 21:04 ` Felix Blanke
2011-02-08 21:51 ` Hubert Kario
2011-02-08 21:59 ` Diwaker Gupta
2011-02-08 22:04 ` cwillu [this message]
2011-02-08 22:11 ` Diwaker Gupta
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='AANLkTi=rG+NODydGFUNr_LsMgJZ7=B1ae3H7reDOr-pp@mail.gmail.com' \
--to=cwillu@cwillu.com \
--cc=diwaker@maginatics.com \
--cc=hka@qbs.com.pl \
--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).