From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: Data Offset Date: Wed, 13 Jun 2012 14:11:58 -0400 Message-ID: <4FD8D7EE.5000805@turmel.org> References: <20120602095237.3822e2c2@notabene.brown> <20120604133526.6da3bf10@notabene.brown> <4FCCFDBB.201@pierre-beck.de> <20120605085728.7e922359@notabene.brown> <20120605154427.192566af@notabene.brown> <20120610074531.65eaed81@notabene.brown> <4FD86179.1080209@pierre-beck.de> <4FD88C50.1000104@turmel.org> <4FD8D439.10406@pierre-beck.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FD8D439.10406@pierre-beck.de> Sender: linux-raid-owner@vger.kernel.org To: Pierre Beck Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids On 06/13/2012 01:56 PM, Pierre Beck wrote: > Am 13.06.2012 14:49, schrieb Phil Turmel: >> >> fsck -n is the *only* safe way to automate the check. Hex dumps of >> expected signature blocks is even better, but is difficult to automate. > > The journal playback seemed less dangerous than fsck in general, but > fsck -n is even better, agreed. It's not a question more or less dangerous. If the stripes are out of order, writing to the array is destructive. Not only will the writes probably land in the wrong place on the device, but writing triggers recalculated parity, which also probably stomps on other data. Phil