From: Eric Sandeen <sandeen@redhat.com>
To: Heinz Nimmervoll <bt1now@gmx.at>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Aw: Re: superblock completely overwritten
Date: Wed, 14 Dec 2016 10:28:01 -0600 [thread overview]
Message-ID: <9df0fe06-da77-11f3-3d6b-dbf941df6376@redhat.com> (raw)
In-Reply-To: <trinity-6030b51c-4ef2-49de-bc0d-da61db362d9c-1481708479043@3capp-gmx-bs37>
On 12/14/16 3:41 AM, Heinz Nimmervoll wrote:
>>> - How is it possible, that even the magic number (and everything else) got overwritten?
>>> - Why could it ever be overwritten?
>> I don't think anyone here can tell you what happened, it is almost certainly not
>> an ext4 bug. Could be a driver bug, or an admin running a stray "dd" command,
>> or some other utility gone astray, or ... anything, really.
> I can rule out that it was the dd command. Eric, do you think it
> could also be a problem about the SD-card and wear levelling (just a
> guess)?
Ok, now that Darrick has pointed out that it's inode data, I am slightly
less sure that it is "almost certainly not an ext4 bug" :)
Still, I don't recall any other reports of this type of corruption, so
I think it's quite possible that it's a problem outside of ext4.
Depending on how hard it is to reproduce, you might consider retesting
several sd card types to see if it is hardware-dependent.
-Eric
prev parent reply other threads:[~2016-12-14 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 15:39 superblock completely overwritten Heinz Nimmervoll
2016-12-13 16:15 ` Eric Sandeen
2016-12-13 18:13 ` Darrick J. Wong
2016-12-14 9:41 ` Aw: " Heinz Nimmervoll
2016-12-14 16:28 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9df0fe06-da77-11f3-3d6b-dbf941df6376@redhat.com \
--to=sandeen@redhat.com \
--cc=bt1now@gmx.at \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).