ceph-devel.vger.kernel.org archive mirror
 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: Wed, 1 Oct 2014 10:50:00 +0200	[thread overview]
Message-ID: <1412153400.6822.14.camel@sebmain.cern.ch> (raw)
In-Reply-To: <542BBC5D.8080304@dachary.org>

I've tried on 3 machines up to now, with different kernels :
  - a RHEL6 (or close to it) with kernel 2.6.32-358.2.1.el6.x86_64
  - a debian unstable box with kernel 3.12-1-amd64 #1 SMP Debian 3.12.6-2
  - an ubuntu one, as you suggested, don't remember the kernel (and box is gone)

Sebastien


On Wed, 2014-10-01 at 10:33 +0200, Loic Dachary wrote:
> Which kernel are you running accord to uname -a ? I have:
> 
> Linux 0a2ad46b4fb5 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> 
> 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).
> > Concerning configure and autogen, I do the standard (naive ?)
> > "./autogen.sh; ./configure; make" given by the readme.
> > 
> > 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
> > 
> 



      reply	other threads:[~2014-10-01  8: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
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 [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=1412153400.6822.14.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;
as well as URLs for NNTP newsgroup(s).