From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f53.google.com ([209.85.215.53]:34188 "EHLO mail-lf0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752562AbcGEDss (ORCPT ); Mon, 4 Jul 2016 23:48:48 -0400 Received: by mail-lf0-f53.google.com with SMTP id h129so126659060lfh.1 for ; Mon, 04 Jul 2016 20:48:47 -0700 (PDT) Subject: Re: Unable to mount degraded RAID5 To: Chris Murphy , =?UTF-8?B?VG9tw6HFoSBIcmRpbmE=?= References: <95f58623-95a4-b5d2-fa3a-bfb957840a31@gmail.com> Cc: Btrfs BTRFS From: Andrei Borzenkov Message-ID: <577B2E1D.5070808@gmail.com> Date: Tue, 5 Jul 2016 06:48:45 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: 04.07.2016 23:43, Chris Murphy пишет: > > Have you done a scrub on this file system and do you know if anything > was fixed or if it always found no problem? > scrub on degraded RAID5 cannot fix anything by definition, because even if scrub finds discrepancies, it does not have enough data to reconstruct them. I would actually avoid it - the worst that can happen if it attempts to replace remaining data with something faked.