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@xxxxxxxxxx> 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@xxxxxxx> 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@xxxxxxxxxxxxxxx >> 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@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
