From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Try to free truncate log when meeting ENOSPC in write.
Date: Wed, 3 Nov 2010 23:19:29 -0700 [thread overview]
Message-ID: <20101104061928.GA22663@mail.oracle.com> (raw)
In-Reply-To: <4CD246E1.1030608@oracle.com>
On Thu, Nov 04, 2010 at 01:38:41PM +0800, Tao Ma wrote:
> yes, I have run the test case overnight and didn't hit ENOSPC any
> more. So do you think of accepting it? If yes, I will regenerate the
> patch for your merge.
Please do. Thanks.
Joel
--
"The question of whether computers can think is just like the question
of whether submarines can swim."
- Edsger W. Dijkstra
Joel Becker
Senior Development Manager
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-11-04 6:19 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 [this message]
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
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=20101104061928.GA22663@mail.oracle.com \
--to=joel.becker@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).