[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AEA0B71.5050805@redhat.com>
Date: Thu, 29 Oct 2009 16:38:57 -0500
From: Eric Sandeen <sandeen@...hat.com>
To: Parag Warudkar <parag.lkml@...il.com>
CC: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Theodore Tso <tytso@....edu>,
LKML <linux-kernel@...r.kernel.org>, linux-ext4@...r.kernel.org,
bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 14354] Re: ext4 increased intolerance to unclean shutdown?
Parag Warudkar wrote:
> On Tue, Oct 27, 2009 at 6:15 AM, Aneesh Kumar K.V
> <aneesh.kumar@...ux.vnet.ibm.com> wrote:
>> Can you try this patch ?
>>
>> commit a8836b1d6f92273e001012c7705ae8f4c3d5fb65
>> Author: Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com>
>> Date: Tue Oct 27 15:36:38 2009 +0530
>>
>> ext4: discard preallocation during truncate
>>
>> We need to make sure when we drop and reacquire the inode's
>> i_data_sem we discard the inode preallocation. Otherwise we
>> could have blocks marked as free in bitmap but still belonging
>> to prealloc space.
>
> Just wanted to let you know that I have applied this patch and one
> unclean shutdown later it seems to have not given me any trouble.
>
> I will continue testing it - hopefully I won't have to reformat this
> time ( every time I tested previously I ended up having weird issues
> that I decided to get rid of by reformatting /).
I've been running my testcase, and I just hit the usual corruption with
this patch in place after 8 iterations, I'm afraid.
-Eric
> Parag
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists