From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: Mdadm server eating drives Date: Fri, 14 Jun 2013 17:30:46 -0400 Message-ID: <51BB8B86.9050803@turmel.org> References: <51B896A2.9090105@websitemanagers.com.au> <51BA7B28.9030808@turmel.org> <51BB8A67.5000605@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51BB8A67.5000605@turmel.org> Sender: linux-raid-owner@vger.kernel.org To: Barrett Lewis Cc: "linux-raid@vger.kernel.org" List-Id: linux-raid.ids On 06/14/2013 05:25 PM, Phil Turmel wrote: > On 06/14/2013 05:20 PM, Barrett Lewis wrote: >> Is there any reason not to run "e2fsck -y /dev/md0"? > > An fsck is often needed after one of these crises. So, yes. After wrapping my head around the grammar... *No*, no reason to not run fsck. :-) Phil