CEPH filesystem development
 help / color / mirror / Atom feed
From: Sebastien Ponce <sebastien.ponce@cern.ch>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: librados AIO problem diagnostic
Date: Thu, 2 Oct 2014 11:49:35 +0200	[thread overview]
Message-ID: <1412243375.6822.38.camel@sebmain.cern.ch> (raw)
In-Reply-To: <1412168988.6822.27.camel@sebmain.cern.ch>

Hurray, I manage to seg fault ! (sounds odd this sentence...)
So indeed, fresh ubuntu, debug mode does it. What I've also changed in
the meantime is the type of machine. It's still virtual, but more
powerful (4 cores).

Let's debug it now...

Sebastien


On Wed, 2014-10-01 at 15:09 +0200, Sebastien Ponce wrote:
> Ok, we are getting closer then.
> I'll try to reinstall the ubuntu machine and run with -g.
> 
> Sebastien
> 
> On Wed, 2014-10-01 at 15:08 +0200, Loic Dachary wrote:
> > 
> > On 01/10/2014 13:37, Sebastien Ponce wrote:
> > > I've tried it on the RHEL6 like machine, but no luck. Or should I say I
> > > was lucky ? Anyway no crash.
> > > 
> > > Discussing with Dan Van Der Ster, he told me that he had once the case
> > > where the crash was there or not depending on the libc version. Just in
> > > case, what are you using ? On the machine I've used this morning, it's
> > > glibc-2.12-1.107.el6.x86_64
> > 
> > I'm using 
> > 
> > ii  libc-bin                                              2.19-0ubuntu3 
> > 
> > and I do not have glibc installed. I'm quite sure you can reproduce the problem on a fresh Ubuntu 14.04 with the following
> > 
> > ./autogen.sh ; ./configure --disable-static --with-debug CFLAGS="-Wall -g" CXXFLAGS="-Wall -g"
> > 
> > it fails consistently in my container. When I try with ./configure it does not fail. Something is going on when there is -g instead of the default flags. I checked that --disable-static and --with-debug make no difference.
> > 
> > Cheers
> > 
> > > 
> > > Sebastien
> > > 
> > > On Wed, 2014-10-01 at 10:31 +0200, Loic Dachary wrote:
> > >> Hi,
> > >>
> > >> On 01/10/2014 09:28, Sebastien Ponce wrote:
> > >>> Thanks for this effort !
> > >>> I'll look at all that this afternoon (it's mid morning here).
> > >>
> > >> Same here : I'm in Paris ;-)
> > >>
> > >>> Concerning configure and autogen, I do the standard (naive ?)
> > >>> "./autogen.sh; ./configure; make" given by the readme.
> > >>
> > >> Could you try with
> > >>
> > >> ./autogen.sh ; ./configure --disable-static --with-debug CC='ccache gcc' CXX='ccache g++' CFLAGS="-Wall -g" CXXFLAGS="-Wall -g" ; make
> > >>
> > >> and let me know if you see a problem when running
> > >>
> > >> cd src
> > >> rm -fr dev out ;  mkdir -p dev ; CEPH_NUM_MON=1 CEPH_NUM_OSD=3 ./vstart.sh -d -n -X -l mon osd
> > >> ./ceph_test_rados_striper_api_aio
> > >>
> > >> I'm trying with your "./configure" on my end to check if this changes something.
> > >>
> > >> It's going to be a fun one ;-)
> > >>
> > >> Cheers
> > >>
> > >>>
> > >>> Sebastien
> > >>>
> > >>>
> > >>> On Wed, 2014-10-01 at 09:01 +0200, Loic Dachary wrote:
> > >>>> Hi Sebastien,
> > >>>>
> > >>>> In the context of http://tracker.ceph.com/issues/9356 I'm trying to collect as much information as I can in an environment that can be reconstructed to avoid interferences. Could you please let me know which ./configure line you are using ? Or which do_autogen.sh command you are using.
> > >>>>
> > >>>> Thanks in advance :-)
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> 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
> > >>>
> > >>
> > > 
> > > 
> > > --
> > > 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
> > > 
> > 
> 
> 
> --
> 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



  reply	other threads:[~2014-10-02  9:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  7:01 librados AIO problem diagnostic Loic Dachary
2014-10-01  7:28 ` Sebastien Ponce
2014-10-01  8:31   ` Loic Dachary
2014-10-01 11:37     ` Sebastien Ponce
2014-10-01 13:08       ` Loic Dachary
2014-10-01 13:09         ` Sebastien Ponce
2014-10-02  9:49           ` Sebastien Ponce [this message]
2014-10-02 14:31             ` Sebastien Ponce
2014-10-02 14:58               ` Loic Dachary
2014-10-08  7:14                 ` Loic Dachary
2014-10-08  8:00                   ` Sebastien Ponce
2014-10-09 14:06                     ` Sebastien Ponce
2014-10-09 14:24                       ` Loic Dachary
2014-10-01  8:33   ` Loic Dachary
2014-10-01  8:50     ` Sebastien Ponce

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=1412243375.6822.38.camel@sebmain.cern.ch \
    --to=sebastien.ponce@cern.ch \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.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