From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: pdj-fstest mkdir/rm error messages again
Date: Thu, 17 Jun 2010 19:26:11 +0000 (UTC) [thread overview]
Message-ID: <hvdssj$mc9$1@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1006170913550.6914@cobra.newdream.net
Am Thu, 17 Jun 2010 09:15:02 -0700 schrieb Sage Weil:
> Hi Thomas,
>
> On Thu, 17 Jun 2010, Thomas Mueller wrote:
>> for a while the pdj-fstest worked without error messages.
>>
>> now the pdj-fstest says again "successfull" but prints these:
>>
>> /home/tmu//home/tmu/src/ceph-testsuite/tools/pjd-fstest-20080816/tests/
chmod/02.t
>> ..... ok mkdir: cannot create directory
>> `_xxxxveryveryveryverylongxxxxxxxxxxx': File name too long rm: cannot
>> remove `_xxveryveryveryverylongxxxxxx': File name too long
>> /home/tmu/src/ceph-testsuite/tools/pjd-fstest-20080816/tests/chmod/03.t
>> ..... oksrc/ceph-testsuite/tools/pjd-fstest-20080816/tests/chmod/02.t
>> ..... ok mkdir: cannot create directory
>> `_xxxxveryveryveryverylongxxxxxxxxxxx': File name too long rm: cannot
>> remove `_xxveryveryveryverylongxxxxxx': File name too long
>> /home/tmu/src/ceph-testsuite/tools/pjd-fstest-20080816/tests/chmod/03.t
>> ..... ok
>
> This is a kernel client thing that was fixed by
> 558d3499bd059d4534b1f2b69dc1c562acc733fe (merged into 2.6.35-rc3). Can
> you confirm that you saw this with something older than that?
>
> Thanks-
> sage
this is on ceph-client-standalone/unstable-backport ref
fe5b9c28ed9cfeb450233d7fedced4203f7a1d64
compiled and loaded the module again. the messages are reproducable.
- Thomas
next prev parent reply other threads:[~2010-06-17 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 14:55 pdj-fstest mkdir/rm error messages again Thomas Mueller
2010-06-17 16:15 ` Sage Weil
2010-06-17 19:26 ` Thomas Mueller [this message]
2010-06-17 19:31 ` Sage Weil
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='hvdssj$mc9$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@vger.kernel.org \
/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.