From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2: Try to free truncate log when meeting ENOSPC in write.
Date: Tue, 07 Dec 2010 18:15:16 -0800 [thread overview]
Message-ID: <4CFEEA34.5020109@oracle.com> (raw)
In-Reply-To: <20101208015818.GB22293@mail.oracle.com>
On 12/07/2010 05:58 PM, Joel Becker wrote:
> On Thu, Nov 04, 2010 at 03:14:11PM +0800, Tao Ma wrote:
>> Recently, one of our colleagues meet with a problem that if we
>> write/delete a 32mb files repeatly, we will get an ENOSPC in
>> the end. And the corresponding bug is 1288.
>> http://oss.oracle.com/bugzilla/show_bug.cgi?id=1288
>>
>> The real problem is that although we have freed the clusters,
>> they are in truncate log and they will be summed up so that
>> we can free them once in a whole.
>>
>> So this patch just try to resolve it. In case we see -ENOSPC
>> in ocfs2_write_begin_no_lock, we will check whether the truncate
>> log has enough clusters for our need, if yes, we will try to
>> flush the truncate log at that point and try again. This method
>> is inspired by Mark Fasheh<mfasheh@suse.com>. Thanks.
> I think I like this. Anyone have any objections?
Looks good.
next prev parent reply other threads:[~2010-12-08 2:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 7:29 [Ocfs2-devel] [PATCH] ocfs2: Try to free truncate log when meeting ENOSPC in write Tao Ma
2010-10-26 8:28 ` tristan
2010-10-26 8:54 ` Tao Ma
2010-10-26 9:05 ` tristan
2010-11-04 1:46 ` Joel Becker
2010-11-04 5:38 ` Tao Ma
2010-11-04 6:19 ` Joel Becker
2010-11-04 7:14 ` [Ocfs2-devel] [PATCH v2] " Tao Ma
2010-12-08 1:58 ` Joel Becker
2010-12-08 2:15 ` Sunil Mushran [this message]
2010-12-16 8:51 ` Joel Becker
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=4CFEEA34.5020109@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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).