From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: Amon Ott <ao@m-privacy.de>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] fixes for undeletable empty directory
Date: Thu, 06 Dec 2012 23:09:11 +0800 [thread overview]
Message-ID: <50C0B517.303@intel.com> (raw)
In-Reply-To: <50BF093F.4060709@m-privacy.de>
On 12/05/2012 04:43 PM, Amon Ott wrote:
> Am 04.12.2012 09:09, schrieb Yan, Zheng:
>> These two patches fix MDS restart issues that may corrupt the fragstat accounting
>> and cause undeletable empty directory. These two patches, together with the patch
>> "mds: fix journaling issue regarding rstat accounting", have passed overnight
>> "fsstress + restart MDS every 120s" test. No undeletable directory was found.
>>
>> These patches are also in:
>> git://github.com/ukernel/ceph.git wip-mds
>
> Thank you very much for working on MDS issues, your work gave me some
> hope that our very long standing crashes at MDS failover could be fixed
> soon.
Hi,
Sorry for the delay
>
> Right now, we have our four node test cluster running with 0.55 and your
> latest patches. Hopefully, today's stress test will work fine.
>
> One question: with your latest patches, is a multiple MDS setup stable
> in your tests? So far, we only tried with max mds = 1. As our work load
> writes many small files, some load sharing for MDS would be nice to
> have. I would be willing to help with tests and reports, if needed.
>
No, multiple MDS setup is still unstable.
Regards
Yan, Zheng
> Amon Ott
>
prev parent reply other threads:[~2012-12-06 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 8:09 [PATCH 0/2] fixes for undeletable empty directory Yan, Zheng
2012-12-04 8:09 ` [PATCH 1/2] mds: don't create bloom filter for incomplete dir Yan, Zheng
2012-12-04 8:09 ` [PATCH 2/2] mds: journal remote inode's projected parent Yan, Zheng
2012-12-05 8:43 ` [PATCH 0/2] fixes for undeletable empty directory Amon Ott
2012-12-06 15:09 ` Yan, Zheng [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=50C0B517.303@intel.com \
--to=zheng.z.yan@intel.com \
--cc=ao@m-privacy.de \
--cc=ceph-devel@vger.kernel.org \
/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