From: Willem Jan Withagen <wjw@digiware.nl>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: ceph-fuse is working on FreeBSD
Date: Wed, 29 Mar 2017 18:18:13 +0200 [thread overview]
Message-ID: <e5a26f2a-ab77-e49a-3a54-e039464ef913@digiware.nl> (raw)
In-Reply-To: <CAJ4mKGbvc9fiFxbrnFpCm13-QsUNR8FF_Ka6N4eFtbD9xKk=NQ@mail.gmail.com>
On 29-3-2017 18:12, Gregory Farnum wrote:
> Sweet! Try pjd yet? ;)
I guess you missed the "slowly" part..... 8-D
I was able to cp -r a small tree to it. Which I think is already a major
one for me.
That said, I know that the FreeBSD fuse interface is "fragile", and I
have seen users complain about loose bits and pieces.
--WjW
> On Wed, Mar 29, 2017 at 9:08 AM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>> Hi,
>>
>> I needed some more skills to actually get everythingin place to get it
>> working. But in essence I have ceph-fuse running...
>>
>> wjw# df | grep fuse
>> /dev/fuse 9168256790 203540395 8964716395 2% /zfs/home/wjw/mnt/zfs
>> /dev/fuse 8241876992 60174336 8181702656 1% /zfs/home/wjw/mnt/cephf
>>
>> wjw# ls ~/mnt/cephfs/
>> wjw# touch ~/mnt/cephfs//test
>> wjw# ~/mnt/cephfs/
>> test
>>
>> So we are slowly getting there....
>>
>> --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
next prev parent reply other threads:[~2017-03-29 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 16:08 ceph-fuse is working on FreeBSD Willem Jan Withagen
2017-03-29 16:09 ` John Spray
2017-03-29 16:12 ` Gregory Farnum
2017-03-29 16:18 ` Willem Jan Withagen [this message]
2017-03-29 16:23 ` Alan Somers
2017-03-30 9:59 ` Willem Jan Withagen
2017-04-28 22:01 ` Gregory Farnum
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=e5a26f2a-ab77-e49a-3a54-e039464ef913@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox