From mboxrd@z Thu Jan 1 00:00:00 1970 From: Willem Jan Withagen Subject: Re: New messages in OSD logs. Date: Wed, 20 Apr 2016 11:41:34 +0200 Message-ID: <57174ECE.8010800@digiware.nl> References: <57121CDE.3010908@digiware.nl> <2067877477.80383590.1461142063409.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from smtp.digiware.nl ([31.223.170.169]:34500 "EHLO smtp.digiware.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933016AbcDTJuc (ORCPT ); Wed, 20 Apr 2016 05:50:32 -0400 In-Reply-To: <2067877477.80383590.1461142063409.JavaMail.zimbra@redhat.com> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Erwan Velu Cc: Ceph Development On 20-4-2016 10:47, Erwan Velu wrote: > I have the exact same trace while running a test on teuthology. And I guess you are not running FreeBSD... :) Teuthology would certainly not. Does you test also ends in error? --WjW > ----- Mail original ----- > De: "Willem Jan Withagen" > =C3=80: "Ceph Development" > Envoy=C3=A9: Samedi 16 Avril 2016 13:07:10 > Objet: New messages in OSD logs. >=20 > Hi >=20 > I've recently rebased my fork, and also upgrae FreeBSD to more recent= code. > Now I'm running into this: >=20 > 2016-04-16 03:03:55.891466 805617000 -1 > filestore(testdir/test-erasure-eio/0) WARNING: max attr value size (1= 024) > is smaller than osd_max_object_name_len (2048). Your backend filesyst= em > appears to not support attrs large enough > to handle the configured max rados name size. You may get unexpected > ENAMETOOLONG errors on rados operations or buggy behavior >=20 > and later on: >=20 > 2016-04-16 03:04:03.287073 805617000 2 osd.0 0 boot > 2016-04-16 03:04:03.287846 805617000 -1 osd.0 0 backend (filestore) i= s=20 > unable to support max object name[space] le > n > 2016-04-16 03:04:03.287873 805617000 -1 osd.0 0 osd max object nam= e=20 > len =3D 2048 > 2016-04-16 03:04:03.287894 805617000 -1 osd.0 0 osd max object=20 > namespace len =3D 256 > 2016-04-16 03:04:03.287931 805617000 -1 osd.0 0 (63) File name too lo= ng > 2016-04-16 03:04:03.303432 805617000 1 journal close=20 > testdir/test-erasure-eio/0/journal > 2016-04-16 03:04:03.310280 805617000 -1 ^[[0;31m ** ERROR: osd init=20 > failed: (63) File name too long^[[0m >=20 > And the OSD dies.... >=20 > I guess that this has the do with the changes in the LFN modules, and= is=20 > also the reason for the debate about ext4 support. >=20 > Uptill now unittest_chain_xattr did work, but that now also fails. > But it fails in a strange way where it tries to delete attributes wit= h=20 > numerical ends that are certainly not in the attributes. > Maximum xattr name length in FreeBSD seems to be 256 chars, which was= n't=20 > a problem yet. >=20 > So is there any chance of continuing on my "old" way to finish a firs= t=20 > version of the port? >=20 > Or am I just seeing things, and should I start looking at the FreeBSD= =20 > side of things? >=20 >=20 > Thanx, > --WjW > -- > 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 >=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