Latest update on this thread. btrfs check (4.3.1) reports no problems.
Volume mounts with kernel 4.2.8 with no errors. And I just did a scrub
and there were no errors, not even any fix up messages. And dev stats
are all zero.
So... it appears it was a minor enough problem, and still consistent
On 2015-12-22 05:23, Duncan wrote:
Kai Krakow posted on Tue, 22 Dec 2015 02:48:04 +0100 as excerpted:
I just wondered if btrfs allows for the case where both stripes could
have valid checksums despite of btrfs-RAID - just because a failure
occurred right on the spot.
Is this possible? What
Kai Krakow posted on Tue, 22 Dec 2015 02:48:04 +0100 as excerpted:
> I just wondered if btrfs allows for the case where both stripes could
> have valid checksums despite of btrfs-RAID - just because a failure
> occurred right on the spot.
>
> Is this possible? What happens then? If yes, it would
Am Mon, 21 Dec 2015 10:23:31 +0800
schrieb Qu Wenruo :
>
>
> Chris Murphy wrote on 2015/12/20 19:12 -0700:
> > On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo
> > wrote:
> >>
> >>
> >> Chris Murphy wrote on 2015/12/20 15:31 -0700:
> >
> >>> I think
Am Tue, 22 Dec 2015 09:22:20 +0800
schrieb Qu Wenruo :
>
>
> Kai Krakow wrote on 2015/12/22 02:05 +0100:
> > Am Mon, 21 Dec 2015 10:23:31 +0800
> > schrieb Qu Wenruo :
> >
> >>
> >>
> >> Chris Murphy wrote on 2015/12/20 19:12 -0700:
> >>> On
Kai Krakow wrote on 2015/12/22 02:48 +0100:
Am Tue, 22 Dec 2015 09:22:20 +0800
schrieb Qu Wenruo :
Kai Krakow wrote on 2015/12/22 02:05 +0100:
Am Mon, 21 Dec 2015 10:23:31 +0800
schrieb Qu Wenruo :
Chris Murphy wrote on 2015/12/20
Latest update.
4.4.0-0.rc6.git0.1.fc24.x86_64
btrfs-progs v4.3.1
Mounted the volume normally with both devices available, no mount
options, so it is a rw mount. And it mounts with only the normal
kernel messages:
[ 9458.290778] BTRFS info (device sdc): disk space caching is enabled
[
Kai Krakow wrote on 2015/12/22 02:05 +0100:
Am Mon, 21 Dec 2015 10:23:31 +0800
schrieb Qu Wenruo :
Chris Murphy wrote on 2015/12/20 19:12 -0700:
On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo
wrote:
Chris Murphy wrote on 2015/12/20 15:31
On Mon, Dec 14, 2015 at 10:59 AM, Chris Murphy wrote:
> On Mon, Dec 14, 2015 at 1:04 AM, Qu Wenruo wrote:
>>
>>
>> Chris Murphy wrote on 2015/12/14 00:24 -0700:
>>> What is a full disk dump? I can try to see if it's possible.
>>
>>
>> Just a dd
On Sun, Dec 20, 2015 at 7:23 PM, Qu Wenruo wrote:
>
>
> Chris Murphy wrote on 2015/12/20 19:12 -0700:
>>
>> On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo
>> wrote:
>>>
>>>
>>>
>>> Chris Murphy wrote on 2015/12/20 15:31 -0700:
>>
>>
I think the
Chris Murphy wrote on 2015/12/20 19:12 -0700:
On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo wrote:
Chris Murphy wrote on 2015/12/20 15:31 -0700:
I think the cause is related to bus power with buggy USB 3 LPM
firmware (these enclosures are cheap maybe $6). I've
On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo wrote:
>
>
> Chris Murphy wrote on 2015/12/20 15:31 -0700:
>> I think the cause is related to bus power with buggy USB 3 LPM
>> firmware (these enclosures are cheap maybe $6). I've found some
>> threads about this being a
Chris Murphy posted on Mon, 14 Dec 2015 00:24:21 -0700 as excerpted:
>> Personally speaking, it may be a false alert from btrfsck.
>> So in this case, I can't provide much help.
>>
>> If you're brave enough, mount it rw to see what will happen(although it
>> may mount just OK).
>
> I'm brave
On Mon, Dec 14, 2015 at 1:04 AM, Qu Wenruo wrote:
>
>
> Chris Murphy wrote on 2015/12/14 00:24 -0700:
>> What is a full disk dump? I can try to see if it's possible.
>
>
> Just a dd dump.
OK, yeah. That's 750GB per drive.
>t won't be an easy
> thing to find a place to
Chris Murphy wrote on 2015/12/14 00:24 -0700:
Thanks for the reply.
On Sun, Dec 13, 2015 at 10:48 PM, Qu Wenruo wrote:
Chris Murphy wrote on 2015/12/13 21:16 -0700:
btrfs check with devid 1 and 2 present produces thousands of scary
messages, e.g.
checksum verify
Chris Murphy wrote on 2015/12/13 21:16 -0700:
Part 1= What to do about it? This post.
Part 2 = How I got here? I'm still working on the write up, so it's
not yet posted.
Summary:
2 dev (spinning rust) raid1 for data and metadata.
kernel 4.2.6, btrfs-progs 4.2.2
btrfs check with devid 1 and
Part 1= What to do about it? This post.
Part 2 = How I got here? I'm still working on the write up, so it's
not yet posted.
Summary:
2 dev (spinning rust) raid1 for data and metadata.
kernel 4.2.6, btrfs-progs 4.2.2
btrfs check with devid 1 and 2 present produces thousands of scary
messages,
Thanks for the reply.
On Sun, Dec 13, 2015 at 10:48 PM, Qu Wenruo wrote:
>
>
> Chris Murphy wrote on 2015/12/13 21:16 -0700:
>> btrfs check with devid 1 and 2 present produces thousands of scary
>> messages, e.g.
>> checksum verify failed on 714189357056 found E4E3BDB6
18 matches
Mail list logo