From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Elder Subject: Re: Date: Thu, 25 Oct 2012 09:36:49 -0500 Message-ID: <50894E81.30403@inktank.com> References: <50868471.1070105@widodh.nl> <162E8EA1E858481C9CD55412C597577E@inktank.com> <1A4C855A8DD647B0B2E8790CA2945D00@inktank.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-ie0-f174.google.com ([209.85.223.174]:58503 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759901Ab2JYOgx (ORCPT ); Thu, 25 Oct 2012 10:36:53 -0400 Received: by mail-ie0-f174.google.com with SMTP id k13so2271207iea.19 for ; Thu, 25 Oct 2012 07:36:51 -0700 (PDT) In-Reply-To: <1A4C855A8DD647B0B2E8790CA2945D00@inktank.com> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Gregory Farnum Cc: jie sun <0maidou0@gmail.com>, ceph-devel@vger.kernel.org On 10/25/2012 07:15 AM, Gregory Farnum wrote: > Sorry, I was unclear =E2=80=94 I meant I think[1] it was fixed in our= linux > branch, for future kernel releases. The messages you're seeing are > just logging a perfectly normal event that's part of the Ceph > protocol. -Greg [1]: I'd have to check to make sure. Sage, Alex, am I > remembering that correctly? I see those too. I think the socket (the other end?) closes after a period of inactivity, but it does re-open and reconnect again whenever necessary so that should really be fine. The messages have not gone away yet, I personally think they should. They originate from here, in net/ceph/messenger.c: static void ceph_fault(struct ceph_connection *con) __releases(con->mutex) { pr_err("%s%lld %s %s\n", ENTITY_NAME(con->peer_name), ceph_pr_addr(&con->peer_addr.in_addr), con->error_msg) Perhaps this should become pr_info() or something. Sage? -Alex > On Wednesday, October 24, 2012 at 11:45 PM, jie sun wrote: >=20 >> What is the version of the master branch ? I use the stable version >> 0.48.2 Thank you! -SunJie >>=20 >> 2012/10/24 Gregory Farnum : >>> On Tuesday, October 23, 2012 at 10:48 PM, jie sun wrote: >>>> My vm kernel version is "Linux ubuntu12 3.2.0-23-generic". >>>>=20 >>>> "ceph-s" shows " health HEALTH_OK monmap e1: 1 mons at >>>> {a=3D10.100.211.146:6789/0}, election epoch 0, quorum 0 a osdmap >>>> e152: 10 osds: 9 up, 9 in pgmap v48479: 2112 pgs: 2112 >>>> active+clean; 23161 MB data, 46323 MB used, 2451 GB / 2514 GB >>>> avail mdsmap e31: 1/1/1 up {0=3Da=3Dup:active} " >>>>=20 >>>> In my vm, I do operations like: I install 4 debs on my vm, such >>>> as libnss3, libnspr4, librados2, librbd1. And then execute >>>> "modprobe rbd" so that I can map a image to my vm. Then "rbd >>>> create foo --size 10240 -m $monIP(my ceph mon IP)", "rbd map >>>> foo -m $monIP" ------ Here a device /dev/rbd0 can be used as a >>>> local device "mkfs -t ext4 /dev/rbd0" "mount /dev/rbd0 /mnt(or >>>> some other directory)" After the operations above, I can use >>>> this device. But it oftern prompt some log like "libceph: osd9 >>>> 10.100.211.68:6809 socket closed". I just want to mount a >>>> device to my vm, so I didn't install a ceph client. Is this >>>> proper to do so? >>>=20 >>>=20 >>>=20 >>> You might consider using the native QEMU/libvirt instead; it >>> offers some more advanced options. But if you're happy with it, >>> this certainly works! >>>=20 >>> The "socket closed" messages are just noise; it's nothing to be >>> concerned about (you'll notice they're happening every 15 minutes >>> for each OSD; probably you aren't doing any disk accesses). I >>> think these warnings actually got removed from our master branch >>> a few days ago. -Greg >>=20 >=20 >=20 >=20 > -- To unsubscribe from this list: send the line "unsubscribe > ceph-devel" in the body of a message to majordomo@vger.kernel.org=20 > More majordomo info at http://vger.kernel.org/majordomo-info.html >=20 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html