From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com
 [IPv6:2a00:1450:400c:c09::230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue, 15 Dec 2015 10:37:27 +0100 (CET)
Received: by mail-wm0-x230.google.com with SMTP id p66so100768358wmp.1
 for <dm-crypt@saout.de>; Tue, 15 Dec 2015 01:37:27 -0800 (PST)
References: <CAEtdG7uDuvJDys=TT9-Ou5zR8VMCFkqAiWJDLaR5dPhicDfVTA@mail.gmail.com>
 <1308232842.375292.1449777297163.JavaMail.yahoo@mail.yahoo.com>
 <CAEtdG7sSJQC79cAqCGcMwREH_nTb8NakiXSfCr3+vv3vyo0w+A@mail.gmail.com>
 <CAEtdG7vzPtjzcaD0O4Fa4QoHLApMiBo4vaWRL0x8H-9aCbr+KQ@mail.gmail.com>
 <566ADEFA.7090509@gmail.com>
 <CAEtdG7vAYRf=t==w7vJ-gvfAaS85mT66fTOSKAhJeQfyefs6WQ@mail.gmail.com>
 <566DCC8B.10401@gmail.com>
 <CAEtdG7t713F63L=du_QDdsZ=iLevoM0cEiJ47p-S=GK+u-pKyw@mail.gmail.com>
 <CAEtdG7vqPSH2c2VNKwdocJcUcRscq=Ax9JK244NDh1tRyJPqQA@mail.gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <566FDF55.40204@gmail.com>
Date: Tue, 15 Dec 2015 10:37:25 +0100
MIME-Version: 1.0
In-Reply-To: <CAEtdG7vqPSH2c2VNKwdocJcUcRscq=Ax9JK244NDh1tRyJPqQA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [dm-crypt] Fwd: Cannot wipe header on device
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: =?UTF-8?Q?Lu=c3=ads_de_Sousa?= <luis.a.de.sousa@gmail.com>, dm-crypt@saout.de



On 12/15/2015 09:53 AM, Luís de Sousa wrote:
> Hello again,
> 
> I have just consulted the mail list archive and it seems I am only
> recieving a restricted number of replies to this thread. You can find
> the smartctl output at the end of this message; it essentially says
> nothing. Regarding system messages, I am not getting anything beyond
> those I already posted here.
> 
> Yesterday I ran badblocks again in read-write mode; it took over 8
> hours to complete and reported zero errors. The only new thing is the
> output from fsck, that is reporting "Bad magic number in super-block"
> - see the full output below. I recieve the same error if try one of
> the alternate superblocks suggested.

I wonder if the problem is O_SYNC flag in that request...

But that would indicate some problem in kernel perhaps.

Milan