From: Theodore Ts'o <tytso@mit.edu>
To: Devrin Talen <dct23@cornell.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 filesystem corruption across partitions
Date: Thu, 17 Apr 2014 12:12:49 -0400 [thread overview]
Message-ID: <20140417161249.GH18591@thunk.org> (raw)
In-Reply-To: <1397747123.6833.24.camel@luigi>
On Thu, Apr 17, 2014 at 11:05:23AM -0400, Devrin Talen wrote:
> Hi all,
>
> I'm debugging an issue on my platform. In short, I can corrupt an ext4
> filesystem on one partition by writing a file on a different one. I'm
> suspecting something is off either with my partition table or filesystem
> parameters, but I'm such an ext4 beginner that I thought I'd start here
> to get some help in where to look.
The partition table looks fine. (What I did was to take the lba_start
and partition_size fields from your table, imported them into a
spreadsheet, and then verified that "lba_start + partition_size/512"
for each partition was the same as the lba_start of the next
partition. Obviously, there is no partition table overlap.)
The kernel is supposed to make sure that writes in one partition can't
affect another parition, so either you have a kernel bug in the block
device layer or driver, or you have a hardware problem.
I hate to ask this, but are you sure you have a quality 4GB sd card?
There are fraudulent cards out there where a card will be marked as
having X GB, but it only really has Y GB, or even Y MB worth of flash.
The people making these fraudulent cards rely on the fact that very
often people don't actually fill up their flash cards, so as long as
they don't write to more than Y GB worth of disk sectors, they won't
notice anything wrong. But if you do write to more sectors than there
is flash, then the N+Ith unique disk sector write ends up going to the
Ith disk sector that had been written.
- Ted
next prev parent reply other threads:[~2014-04-17 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 15:05 ext4 filesystem corruption across partitions Devrin Talen
2014-04-17 16:12 ` Theodore Ts'o [this message]
2014-05-06 2:01 ` Devrin Talen
2014-05-06 19:40 ` Theodore Ts'o
2014-05-06 22:38 ` Andreas Dilger
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=20140417161249.GH18591@thunk.org \
--to=tytso@mit.edu \
--cc=dct23@cornell.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.