All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Spray <jspray@redhat.com>
To: "Deneau, Tom" <tom.deneau@amd.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: verbose logging for mount -t ceph or ceph-fuse problems
Date: Tue, 19 Jul 2016 09:47:28 +0100	[thread overview]
Message-ID: <CALe9h7fxL54r014kJRz7tfXbGrcMpsT74Uh9PCjguMrkjydeiQ@mail.gmail.com> (raw)
In-Reply-To: <DM3PR1201MB09250DDBE36361721995F79B9B360@DM3PR1201MB0925.namprd12.prod.outlook.com>

For ceph-fuse, try running in the foreground with logging to the
console (-d) and enabling client debug (--debug-client=20), enabling
prints for each message sent (--debug-ms=1) and debugging for the
monitor client (--debug-monc=20).

Cheers,
John

On Mon, Jul 18, 2016 at 11:41 PM, Deneau, Tom <tom.deneau@amd.com> wrote:
> What debug option (from http://docs.ceph.com/docs/master/rados/troubleshooting/log-and-debug/) would be best to find errors coming from
>    * mount -t ceph ...
>    * or ceph-fuse
>
> My problems seem to be network-address-related because if I create the cluster with 1Gig addresses rather than 10Gig, both mount -t ceph and ceph-fuse work fine.
>
> -- Tom Deneau
>
> --
> 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:[~2016-07-19  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 22:41 verbose logging for mount -t ceph or ceph-fuse problems Deneau, Tom
2016-07-19  8:47 ` John Spray [this message]
2016-07-21  2:14   ` Ken Dreyer

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=CALe9h7fxL54r014kJRz7tfXbGrcMpsT74Uh9PCjguMrkjydeiQ@mail.gmail.com \
    --to=jspray@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=tom.deneau@amd.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.