vinodeno_t is not accessible via libceph (was it previously?) though
it's still used and it's in mdstypes.h, though it doesn't look like
it'll include in a straight C compile. Is there a missing include?
[bchrisman (aemerson): src] $ find . -name '*.c' -o -name '*.h' |
xargs grep inodeno
./include/FSAL/FSAL_CEPH/fsal_types.h: vinodeno_t vi;
./include/FSAL/FSAL_CEPH/fsal_types.h: vinodeno_t vi;
./include/FSAL/FSAL_CEPH/fsal_types.h: vinodeno_t vi;
[bchrisman (aemerson): src] $
../../include/FSAL/FSAL_CEPH/fsal_types.h:73: error: expected
specifier-qualifier-list before ‘vinodeno_t’
from mdstypes:
struct vinodeno_t {
inodeno_t ino;
snapid_t snapid;
vinodeno_t() {}
vinodeno_t(inodeno_t i, snapid_t s) : ino(i), snapid(s) {}
void encode(bufferlist& bl) const {
::encode(ino, bl);
::encode(snapid, bl);
}
void decode(bufferlist::iterator& p) {
::decode(ino, p);
::decode(snapid, p);
}
};
WRITE_CLASS_ENCODER(vinodeno_t)
On Fri, Jul 29, 2011 at 12:05 PM, Matt W. Benjamin <matt@xxxxxxxxxxxx> wrote:
> Hi Brian,
>
> FSAL_CEPH doesn't involve the kernel client, rather an incidentally modified libceph and libRADOS--it's linked into Ganesha, not using POSIX. Writing directly to OSDs is part of the pNFS parallel access strategy.
>
> Matt
>
> ----- "Brian Chrisman" <brchrisman@xxxxxxxxx> wrote:
>
>> On Fri, Jul 29, 2011 at 9:30 AM, Matt W. Benjamin <matt@xxxxxxxxxxxx>
>> wrote:
>> > Hi Sage,
>> >
>> > We (Linux Box) have built and published a native FSAL for Ceph,
>> which is pretty advanced, and we've submitted the FSAL driver code
>> upstream for review Philippe Deniel.
>>
>> Looking at the FSAL_CEPH, is this expecting the filesystem to be
>> mounted via the ceph kernel client? Have you considered building out
>> an FSAL using libceph as opposed as to writing directly to OSDs
>> (assumedly via libRADOS or librbd).
>>
>> >
>> > In addition, we're working on pNFS support in Ganesha and Ceph, and
>> have a prototype file-based pNFS layout driver for the FSAL that takes
>> advantage of Ceph OSDs for parallel IO.
>> >
>> > We're actively extending these efforts and there should be some
>> publication forthcoming.
>> >
>> > We have an external git repository here:
>> >
>> > git://github.com/aemerson-linuxbox/ganesha.git
>> >
>> > We would really appreciate your feedback--and guidance on how to
>> participate in Ceph, we'd like to.
>> >
>> > Matt
>> >
>> > ----- "Sage Weil" <sage@xxxxxxxxxxxx> wrote:
>> >
>> >> Has anyone looked at Genesha?
>> >>
>> >> http://sourceforge.net/apps/trac/nfs-ganesha/
>> >>
>> >> In principle it would probably be pretty straightforward to wire
>> that
>> >> up
>> >> to libceph and avoid the kernel NFS server for reexporting ceph
>> via
>> >> NFS...
>> >>
>> >> sage
>> >> --
>> >> To unsubscribe from this list: send the line "unsubscribe
>> ceph-devel"
>> >> in
>> >> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> >
>> > --
>> >
>> > Matt Benjamin
>> >
>> > The Linux Box
>> > 206 South Fifth Ave. Suite 150
>> > Ann Arbor, MI 48104
>> >
>> > http://linuxbox.com
>> >
>> > tel. 734-761-4689
>> > fax. 734-769-8938
>> > cel. 734-216-5309
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe
>> ceph-devel" in
>> > the body of a message to majordomo@xxxxxxxxxxxxxxx
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>> >
>
> --
>
> Matt Benjamin
>
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI 48104
>
> http://linuxbox.com
>
> tel. 734-761-4689
> fax. 734-769-8938
> cel. 734-216-5309
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
