All of lore.kernel.org
 help / color / mirror / Atom feed
From: huang jun <hjwsm1989@gmail.com>
To: Colin Patrick McCabe <colin.mccabe@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: fuse problem
Date: Fri, 20 May 2011 09:01:25 +0800	[thread overview]
Message-ID: <BANLkTin8ayOJUWFyDv96y13Oj_rr+PCtdg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikSWLVJ7FE4Gsi-yh+APYohOMEXZA@mail.gmail.com>

hi,colin
i try it as you said, but i can not see anything
 [client]
     log_file = /home/client_logfile
     debug ms = 1
     debug client = 10
     client cache size = 1024*1024*100
is there anything wrong with this setting?

thanks!
2011/5/20 Colin Patrick McCabe <colin.mccabe@dreamhost.com>:
> Hi Huang,
>
> cfuse is a client, so it will use whatever the logging settings are for clients.
> you can set this by adding something like this to the [client] section
> of your configuration file:
>
> log_file = /my_log_file
>
> You can also use this command-line switch to override the configuration:
> --log-file=/my/log/file
>
> cheers,
> Colin
>
>
> On Thu, May 19, 2011 at 4:52 PM, huang jun <hjwsm1989@gmail.com> wrote:
>> hi,brian
>> my 'ceph -s' shows everything is ok
>> and if i do it  on the other machine, i did not find this error.
>> i trun on the debug on ceph.conf like :
>>   [client]
>>       debug ms = 1
>>       debug client = 10
>> but i can't find where does this info goes to ?  not in /var/log/ceph/
>> so where should i look for this debug output?
>>
>> thanks!
>>
>> 2011/5/19 Brian Chrisman <brchrisman@gmail.com>:
>>> On Thu, May 19, 2011 at 4:12 AM, huang jun <hjwsm1989@gmail.com> wrote:
>>>> hi, all
>>>> i just encountered a problem about cfuse:
>>>> i mount cfsue successfully on /mnt by using
>>>>   "cfuse -m 192.168.0.170:6789 /mnt"
>>>> but when i enter /mnt directory, it shows that:
>>>>   [root@localhost mnt]# ll
>>>>   ls: .: Transport endpoint is not connected
>>>
>>> This is a FUSE failure message that generally occurs when your
>>> userspace process (in this case cfuse) has exited (closed its
>>> connection to the FUSE kernel driver).
>>> does 'ceph -s' show that your ceph cluster is up and healthy?
>>> You may want to turn on client debugging to see why cfuse is exiting:
>>> http://ceph.newdream.net/wiki/Debugging
>>>
>>>
>>>> my cfuse client is on centos5, it kernel version is 2.6.18
>>>> and OSD cluster is on debian5, 2.6.35
>>>> i don't know whether it related to SimpleMessenger,so anyone can give
>>>> me some prompts?
>>>>
>>>> thanks!
>>>> --
>>>> 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
>>
>
--
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

  reply	other threads:[~2011-05-20  1:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 11:12 fuse problem huang jun
2011-05-19 14:32 ` Brian Chrisman
2011-05-19 23:52   ` huang jun
2011-05-20  0:47     ` Colin Patrick McCabe
2011-05-20  1:01       ` huang jun [this message]
2011-05-20  2:04         ` Colin Patrick McCabe
2011-05-20  2:31           ` huang jun
2011-05-20  3:13             ` huang jun
2011-05-20 17:25             ` Colin Patrick McCabe
2011-05-23 23:53               ` huang jun
2011-05-24 21:11                 ` Colin Patrick McCabe

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=BANLkTin8ayOJUWFyDv96y13Oj_rr+PCtdg@mail.gmail.com \
    --to=hjwsm1989@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=colin.mccabe@dreamhost.com \
    /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.