All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Parag Warudkar <parag.lkml@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ex
Subject: Re: [Bug 14354] Re: ext4 increased intolerance to unclean shutdown?
Date: Sat, 31 Oct 2009 20:54:28 +0530	[thread overview]
Message-ID: <20091031152428.GA25548@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <20091031091528.GO18464@mit.edu>

On Sat, Oct 31, 2009 at 05:15:28AM -0400, Theodore Tso wrote:
> On Fri, Oct 30, 2009 at 01:56:27PM -0600, Andreas Dilger wrote:
> > I wonder if there are multiple problems involved here?  Eric, it seems
> > possible that your reproducer is exercising a similar, though unrelated
> > codepath.  
> 
> Note that Aneesh has pubished two patches which insert a call to
> ext4_discard_preallocations().  One is a patch which inserts it into
> fs/inode.c's truncate path (for direct/indirect-mapped inodes) and one
> which is patch which inserts it into fs/extents.c truncate path (for
> extent-mapped inodes).  As near as I can tell both patches are
> necessary, and it looks to me like they should be combined into a
> single patch, since commit 487caeef9 affects both truncate paths.
> Aneesh, do you concur?
> 

We need only the patch that drop prealloc space in ext4_truncate_restart_trans
ext4_ext_truncate_extend_restart calls ext4_truncate_restart_trans. So adding
the prealloc space dropping in ext4_truncate_restart_trans should handle both
direct/indirect-mapped inode and extent-mapped inodes.

-aneesh

WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Parag Warudkar <parag.lkml@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14354] Re: ext4 increased intolerance to unclean shutdown?
Date: Sat, 31 Oct 2009 20:54:28 +0530	[thread overview]
Message-ID: <20091031152428.GA25548@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <20091031091528.GO18464@mit.edu>

On Sat, Oct 31, 2009 at 05:15:28AM -0400, Theodore Tso wrote:
> On Fri, Oct 30, 2009 at 01:56:27PM -0600, Andreas Dilger wrote:
> > I wonder if there are multiple problems involved here?  Eric, it seems
> > possible that your reproducer is exercising a similar, though unrelated
> > codepath.  
> 
> Note that Aneesh has pubished two patches which insert a call to
> ext4_discard_preallocations().  One is a patch which inserts it into
> fs/inode.c's truncate path (for direct/indirect-mapped inodes) and one
> which is patch which inserts it into fs/extents.c truncate path (for
> extent-mapped inodes).  As near as I can tell both patches are
> necessary, and it looks to me like they should be combined into a
> single patch, since commit 487caeef9 affects both truncate paths.
> Aneesh, do you concur?
> 

We need only the patch that drop prealloc space in ext4_truncate_restart_trans
ext4_ext_truncate_extend_restart calls ext4_truncate_restart_trans. So adding
the prealloc space dropping in ext4_truncate_restart_trans should handle both
direct/indirect-mapped inode and extent-mapped inodes.

-aneesh

  reply	other threads:[~2009-10-31 15:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16  4:28 ext4 increased intolerance to unclean shutdown? Parag Warudkar
2009-10-16  6:31 ` Maxim Levitsky
2009-10-16  9:15 ` [Bug 14354] " Theodore Tso
2009-10-16 13:06   ` Theodore Tso
2009-10-16 19:16   ` Ric Wheeler
2009-10-25  6:22     ` Pavel Machek
2009-10-26 13:49       ` Ric Wheeler
2009-10-16 22:24   ` Parag Warudkar
2009-10-16 22:24     ` Parag Warudkar
2009-10-26 15:42   ` Linus Torvalds
2009-10-27 10:15   ` Aneesh Kumar K.V
2009-10-29 20:10     ` Mingming
2009-10-29 21:25     ` Parag Warudkar
2009-10-29 21:25       ` Parag Warudkar
2009-10-29 21:38       ` Eric Sandeen
2009-10-30  8:16         ` Theodore Tso
2009-10-30 13:54           ` Eric Sandeen
2009-10-30 13:54             ` Eric Sandeen
2009-10-30 19:56         ` Andreas Dilger
2009-10-31  9:15           ` Theodore Tso
2009-10-31 15:24             ` Aneesh Kumar K.V [this message]
2009-10-31 15:24               ` Aneesh Kumar K.V
2009-10-29 21:42       ` Theodore Tso
2009-10-29 21:42         ` Theodore Tso
2009-10-29 21:52         ` Parag Warudkar
2009-10-29 21:52           ` Parag Warudkar

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=20091031152428.GA25548@skywalker.linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=adilger@sun.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parag.lkml@gmail.com \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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.