linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>
To: linux-fsdevel@vger.kernel.org
Subject: Ext4 data structures integrity
Date: Wed, 28 Sep 2011 16:42:22 +0300	[thread overview]
Message-ID: <CALLzPKb2m6KN7-Weeq4wjUx1RbKutJcnY870tu-hziPvDJkrWQ@mail.gmail.com> (raw)

Hello,

I have a question about Ext4 data structure integrity.

On Ext3 file system I was able to modify offline inode block mapping
in such a way,
that 2 inodes did point to the same data blocks, so when modifying one
file, did affect another file..
FSCK detects such problems and create duplicated blocks, so that inode
content will not overlap...

Does Ext4 suffers from the same problem?

Thanks,
Dmitry

             reply	other threads:[~2011-09-28 13:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 13:42 Kasatkin, Dmitry [this message]
2011-09-28 13:56 ` Ext4 data structures integrity Ted Ts'o
2011-09-28 15:19   ` Kasatkin, Dmitry
2011-09-28 15:45     ` Ted Ts'o
2011-09-29 12:24       ` Kasatkin, Dmitry
2011-09-29 12:56         ` Ted Ts'o
2011-09-29 13:32           ` Kasatkin, Dmitry
2011-09-28 17:16     ` Andreas Dilger
2011-09-29 12:31       ` Kasatkin, Dmitry
2011-09-29 13:33         ` Kasatkin, Dmitry
2011-09-29 13:55           ` Ted Ts'o
2011-10-07 11:40             ` Kasatkin, Dmitry
     [not found]               ` <64BEDF63-5861-47C9-AC90-F41768D09F17@mit.edu>
2011-10-07 14:20                 ` Kasatkin, Dmitry
2011-10-07 15:22                   ` Theodore Tso
2011-11-08 23:44             ` Mimi Zohar
2011-11-10 11:21               ` Kasatkin, Dmitry
2011-09-29 16:35           ` 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=CALLzPKb2m6KN7-Weeq4wjUx1RbKutJcnY870tu-hziPvDJkrWQ@mail.gmail.com \
    --to=dmitry.kasatkin@intel.com \
    --cc=linux-fsdevel@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).