linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: lost with degraded RAID1
Date: Fri, 31 Jan 2014 07:37:09 +0000 (UTC)	[thread overview]
Message-ID: <pan$6a9a9$ad39465e$71323c3$6e34f01d@cox.net> (raw)
In-Reply-To: DD290B24-A1DE-477B-8A73-5507A907F901@colorremedies.com

Chris Murphy posted on Thu, 30 Jan 2014 23:13:36 -0700 as excerpted:

> On Jan 30, 2014, at 11:10 PM, Chris Murphy <lists@colorremedies.com>
> wrote:
>> 
>> I'm also seeing many "Error reading 1647012864000, -1" with different
>> block addresses (same -1 though), and also "1659900002304failed to load
>> free space cache for block group" also with different numbers. Maybe
>> hundreds of these. I'm not sure if this is due to the missing device,
>> and it's reporting missing meta data? Or if the working device also has
>> some problem, which depending on the configuration might implicate a
>> single SATA controller.
> 
> Sorry I'm being impatient since I'm away snowboarding tomorrow. The
> above refers to parts of Johan's btrfs check output which hasn't yet
> made it to the list.

Break a leg! =:^)  (If you've done much drama/acting you may know the 
reference; there's a traditional superstition that wishing someone .... 
luck is a hex and they'll forget their lines or worse!  So you wish them 
to break a leg instead!  =:^)


I'm assuming the error reading errors are due to the missing device, with 
the round-robin trying to read the bad device 50% of the time, but if it 
was full raid1, then the existing copy should be found and read instead, 
assuming of course that the checksum verifies, so despite all the 
alarming looking noise, I believe it's harmless... assuming it was indeed 
full raid1 both data and metadata.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-01-31  7:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 19:16 lost with degraded RAID1 Johan Kröckel
2014-01-30  3:28 ` Duncan
2014-01-30 11:53 ` Johan Kröckel
2014-01-30 17:57   ` Chris Murphy
     [not found]     ` <CABgvyo9FYGSYpj+jL1oqCvtNUqsC8HZ+z=x-Gz7naWoEcCKWpQ@mail.gmail.com>
2014-01-30 19:32       ` Chris Murphy
2014-01-30 22:18   ` Duncan
2014-01-31  3:00     ` Chris Murphy
2014-01-31  5:58       ` Duncan
2014-01-31  6:10         ` Chris Murphy
2014-01-31  6:13           ` Chris Murphy
2014-01-31  7:37             ` Duncan [this message]
2014-01-31  2:19   ` Chris Murphy
2014-01-30 17:33 ` Chris Murphy
2014-01-30 17:58   ` Hugo Mills
2014-01-30 18:25     ` Chris Murphy
2014-02-03 20:55       ` Johan Kröckel
2014-02-03 21:08         ` Chris Murphy
2014-02-03 21:31           ` Johan Kröckel
2014-02-07 11:34             ` Johan Kröckel
2014-02-07 17:43               ` Chris Murphy
2014-02-08 11:09                 ` Johan Kröckel
2014-02-09  5:40                   ` Duncan
2014-02-10 14:05                     ` Johan Kröckel
     [not found]   ` <CABgvyo822bOAHeA1GH28MPaBAU+Zdi72MD_uwL+dhopt+nwMig@mail.gmail.com>
2014-01-31  6:28     ` Fwd: " Johan Kröckel
2014-01-31  6:40 ` Johan Kröckel

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='pan$6a9a9$ad39465e$71323c3$6e34f01d@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).