All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Masanari Iida <standby24x7@gmail.com>
Cc: Amir Goldstein <amir73il@gmail.com>, Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Question about ext4 journal
Date: Sat, 24 Oct 2015 07:23:33 -0400	[thread overview]
Message-ID: <20151024112333.GA27558@thunk.org> (raw)
In-Reply-To: <CALLJCT2T9t9Qsn+6CPCJqd9HLTHn1ZHdOOM74+8X-LHvPuhqaw@mail.gmail.com>

On Sat, Oct 24, 2015 at 12:10:48PM +0900, Masanari Iida wrote:
> 
> My wild guess is
> file was created in inode #100 (for example),
> it was deleted and inode #100 moved to orphan list.
> The inode #100 was re-used in step 3.

The inode is removed from the orphan list as soon as the inode is
released.  The only time an inode remains on the orphan list is if
some other process had an open file descriptor on the file before it
was unlinked.  But in that case, when you recreate the file with the
same name, you will get a new inode, because the old inode has not yet
been released.  Once it has been released, it is removed from the orphan list.

> snapshot taken.

If the storage device is not synchronized with the file system then
there is no guarantee that the snapshot will be consistent.  But given
that you said you waited for hours before taking the snapshot, and it
seems likely that isn't the problem.

> Did we have such trouble during 2.6.32 time?

I don't recall anything like that.  But if you are still using 2.6.32,
then presumably you are on some enterprise distro.  I suggest you open
a support call with your enterprise distro provider, and/or with your
storage device (since I assume you're using some kind of storage array
that has a proprietary device driver).

Cheers,

					- Ted

  reply	other threads:[~2015-10-24 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  4:04 Question about ext4 journal Masanari Iida
     [not found] ` <CAOQ4uxhFw5HCyVuYsKROKvMHJWBCEqZfBM8gtcV1bPQGFXT-hQ@mail.gmail.com>
2015-10-23  6:22   ` Fwd: " Amir Goldstein
2015-10-24  3:10     ` Masanari Iida
2015-10-24 11:23       ` Theodore Ts'o [this message]
2015-10-23 12:50 ` Theodore Ts'o

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=20151024112333.GA27558@thunk.org \
    --to=tytso@mit.edu \
    --cc=amir73il@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=standby24x7@gmail.com \
    /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.