All of lore.kernel.org
 help / color / mirror / Atom feed
* verbose logging for mount -t ceph or ceph-fuse problems
@ 2016-07-18 22:41 Deneau, Tom
  2016-07-19  8:47 ` John Spray
  0 siblings, 1 reply; 3+ messages in thread
From: Deneau, Tom @ 2016-07-18 22:41 UTC (permalink / raw)
  To: ceph-devel

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: verbose logging for mount -t ceph or ceph-fuse problems
  2016-07-18 22:41 verbose logging for mount -t ceph or ceph-fuse problems Deneau, Tom
@ 2016-07-19  8:47 ` John Spray
  2016-07-21  2:14   ` Ken Dreyer
  0 siblings, 1 reply; 3+ messages in thread
From: John Spray @ 2016-07-19  8:47 UTC (permalink / raw)
  To: Deneau, Tom; +Cc: ceph-devel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: verbose logging for mount -t ceph or ceph-fuse problems
  2016-07-19  8:47 ` John Spray
@ 2016-07-21  2:14   ` Ken Dreyer
  0 siblings, 0 replies; 3+ messages in thread
From: Ken Dreyer @ 2016-07-21  2:14 UTC (permalink / raw)
  To: John Spray; +Cc: Deneau, Tom, ceph-devel

Thanks John, I've captured that in the docs for the page Tom linked.

https://github.com/ceph/ceph/pull/10374

- Ken

On Tue, Jul 19, 2016 at 2:47 AM, John Spray <jspray@redhat.com> wrote:
> 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
> --
> 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-07-21  2:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-18 22:41 verbose logging for mount -t ceph or ceph-fuse problems Deneau, Tom
2016-07-19  8:47 ` John Spray
2016-07-21  2:14   ` Ken Dreyer

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.