From: Sage Weil <sweil@redhat.com>
To: Mark Nelson <mnelson@redhat.com>
Cc: Somnath Roy <Somnath.Roy@sandisk.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Bluestore assert
Date: Thu, 11 Aug 2016 16:36:19 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.11.1608111635230.17762@piezo.us.to> (raw)
In-Reply-To: <7dc67e25-4e1c-09a1-8667-ee47572b9290@redhat.com>
On Thu, 11 Aug 2016, Mark Nelson wrote:
> Sorry if I missed this during discussion, but why are these being called if
> the file is deleted?
I'm not sure... rocksdb is the one consuming the interface. Looking
through the code, though, this is the only way I can see that we could log
an op_file_update *after* an op_file_remove.
sage
>
> Mark
>
> On 08/11/2016 11:29 AM, Sage Weil wrote:
> > On Thu, 11 Aug 2016, Somnath Roy wrote:
> > > Sage,
> > > Please find the full log for the BlueFS replay bug in the following
> > > location.
> > >
> > > https://github.com/somnathr/ceph/blob/master/ceph-osd.1.log.zip
> > >
> > > For the db transaction one , I have added code to dump the rocksdb error
> > > code before the assert as you suggested and waiting to reproduce.
> >
> > I'm pretty sure this is the root cause:
> >
> > https://github.com/ceph/ceph/pull/10686
> >
> > sage
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
>
next prev parent reply other threads:[~2016-08-11 16:36 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 20:14 Bluestore assert Somnath Roy
2016-08-10 21:22 ` Sage Weil
2016-08-10 21:42 ` Somnath Roy
2016-08-11 15:32 ` Somnath Roy
2016-08-11 16:29 ` Sage Weil
2016-08-11 16:34 ` Mark Nelson
2016-08-11 16:36 ` Sage Weil [this message]
2016-08-11 22:20 ` Somnath Roy
2016-08-11 22:32 ` Sage Weil
2016-08-14 17:24 ` Somnath Roy
2016-08-15 19:53 ` Sage Weil
2016-08-16 19:45 ` Somnath Roy
2016-08-22 7:33 ` Somnath Roy
2016-08-22 8:02 ` Varada Kari
2016-08-22 8:12 ` Somnath Roy
2016-08-22 8:16 ` Varada Kari
2016-08-22 14:57 ` Sage Weil
2016-08-22 21:57 ` Sage Weil
2016-08-22 22:01 ` Somnath Roy
2016-08-22 23:10 ` Somnath Roy
2016-08-23 5:09 ` Varada Kari
2016-08-23 5:18 ` Somnath Roy
2016-08-23 5:25 ` Varada Kari
2016-08-23 5:27 ` Somnath Roy
2016-08-23 5:30 ` Varada Kari
2016-08-23 5:35 ` Somnath Roy
2016-08-23 5:38 ` Varada Kari
2016-08-23 13:45 ` Sage Weil
2016-08-23 14:46 ` Somnath Roy
2016-08-24 20:36 ` Somnath Roy
2016-08-24 20:43 ` Sage Weil
2016-08-24 20:49 ` Somnath Roy
2016-08-24 21:34 ` Sage Weil
2016-08-24 21:51 ` Somnath Roy
2016-08-24 22:27 ` Sage Weil
2016-08-25 21:34 ` Somnath Roy
2016-08-28 14:37 ` Somnath Roy
2016-08-29 8:20 ` Somnath Roy
2016-08-30 23:57 ` Somnath Roy
2016-08-31 13:20 ` Sage Weil
2016-09-01 22:59 ` Somnath Roy
2016-09-02 16:11 ` Somnath Roy
2016-09-02 16:34 ` Sage Weil
2016-09-02 17:23 ` Somnath Roy
2016-09-02 17:56 ` Sage Weil
2016-09-02 19:01 ` Somnath Roy
2016-09-02 19:26 ` Sage Weil
2016-09-02 20:18 ` Somnath Roy
2016-09-02 20:24 ` Sage Weil
2016-09-02 20:26 ` Somnath Roy
2016-09-06 5:13 ` Somnath Roy
2016-09-06 13:27 ` Sage Weil
2016-09-06 15:29 ` Somnath Roy
2016-09-15 5:10 ` Somnath Roy
2016-09-15 15:38 ` Sage Weil
2016-09-30 16:44 ` Somnath Roy
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=alpine.DEB.2.11.1608111635230.17762@piezo.us.to \
--to=sweil@redhat.com \
--cc=Somnath.Roy@sandisk.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mnelson@redhat.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.