From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: Alexandre Oliva <oliva@gnu.org>
Cc: Gregory Farnum <greg@inktank.com>, Sage Weil <sage@inktank.com>,
"Yan, Zheng" <ukernel@gmail.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] mds: handle setxattr ceph.parent
Date: Fri, 20 Dec 2013 16:03:42 +0800 [thread overview]
Message-ID: <52B3F9DE.60301@intel.com> (raw)
In-Reply-To: <orbo0c5h4p.fsf@livre.home>
On 12/20/2013 11:35 AM, Alexandre Oliva wrote:
> On Dec 19, 2013, "Yan, Zheng" <zheng.z.yan@intel.com> wrote:
>
>> next time you encountered log corruption, please open "new issues" at http://tracker.ceph.com/
>
> I have saved the dumped journal, but it contains too much information
> I'm not supposed to or willing to share, especially with a US-based
> company in the post-Snowden era :-( (something like btrfs-image -s
> might be good to have)
>
> I'd be glad to try to dig info that might be useful out of it, if told
> how to do so, but uploading the journal as taken from the cluster is not
> an option.
>
can you send out the mds log (the latest few hundreds of lines) when the mds crashed.
Regards
Yan, Zheng
next prev parent reply other threads:[~2013-12-20 8:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 11:25 [PATCH] mds: handle setxattr ceph.parent Alexandre Oliva
2013-12-18 2:47 ` Yan, Zheng
2013-12-18 16:32 ` Alexandre Oliva
2013-12-18 17:09 ` Sage Weil
2013-12-18 21:10 ` Gregory Farnum
2013-12-19 8:00 ` Alexandre Oliva
2013-12-19 13:27 ` Yan, Zheng
2013-12-20 3:35 ` Alexandre Oliva
2013-12-20 8:03 ` Yan, Zheng [this message]
2013-12-21 0:22 ` Alexandre Oliva
2013-12-21 0:50 ` Alexandre Oliva
2014-01-06 17:22 ` Gregory Farnum
2014-01-07 4:15 ` Alexandre Oliva
2014-01-07 16:39 ` Gregory Farnum
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=52B3F9DE.60301@intel.com \
--to=zheng.z.yan@intel.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=oliva@gnu.org \
--cc=sage@inktank.com \
--cc=ukernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.