From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Problems with fsck
Date: Fri, 21 Jan 2011 17:29:12 +0000 [thread overview]
Message-ID: <20110121172912.GC8323@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4D35D8C7.70905@oracle.com>
On Tue, Jan 18, 2011 at 10:15:35AM -0800, Sunil Mushran wrote:
> On 01/17/2011 09:47 PM, Tiger Yang wrote:
> > On 01/15/2011 06:38 AM, Sunil Mushran wrote:
> >> Tiger,
> >> Please can you take these four patches and test enabling indexdirs
> >> on a volume. Please do this ASAP. I want this in the git tree by early
> >> next week.
> > Hi, Sunil,
> >
> > I have finished the testing. If enable indexed-dirs on a volume which has metaecc, tunefs.ocfs2 will get segment fault. Tao's patch fixes this problem.
>
> Thanks. Add the acks and push them to the git repo.
Yeah, they all look good.
Joel
--
prev parent reply other threads:[~2011-01-21 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:46 [Ocfs2-devel] Problems with fsck Massimo Cetra
2011-01-12 16:16 ` Sunil Mushran
2011-01-13 19:19 ` Massimo Cetra
2011-01-13 20:25 ` Massimo Cetra
2011-01-14 8:03 ` Tao Ma
2011-01-14 22:38 ` Sunil Mushran
2011-01-18 5:47 ` Tiger Yang
2011-01-18 18:15 ` Sunil Mushran
2011-01-21 17:29 ` Joel Becker [this message]
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=20110121172912.GC8323@ZenIV.linux.org.uk \
--to=jlbec@evilplan.org \
--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).