From owner-freebsd-fs@freebsd.org Wed Sep 9 02:29:54 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7587A00AC6 for ; Wed, 9 Sep 2015 02:29:54 +0000 (UTC) (envelope-from vrock28@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 655DB10F4 for ; Wed, 9 Sep 2015 02:29:54 +0000 (UTC) (envelope-from vrock28@gmail.com) Received: by oixx17 with SMTP id x17so70491728oix.0 for ; Tue, 08 Sep 2015 19:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3F16OzMLbkf3G4Mk8oSdCLIXJAS2+YeIQ10GIEh1rSs=; b=e8gOSll3lNkdYKpVwvO4mepU95LvicxgXvZSbcJk73pnS6lTvDKkYF86J7f2x8egrg e6QqQY6gtEFHJ7I0z1TbJXs0yWvpprtgFx4Y+GiIkZX+xaY5f1F1jL+SMvQgheu4+M53 +FL2/FtSoVto1vD5OqvWhD5Gh9nXmBn6S6yVXN/dvYU5gIedJ6AWZ9TbbXJOsBJxZQqt 2Og+Ezdd3aM24REVAZ9Q+LjmNPFvR6D1L4zoN13LUIH42fQfm0QTM3aGHNNkdDkhZ7P+ ldaNgqdBGJHd41Cf/gZ1pWBJEOJi/wfim5qmxJZDBDQyTqjVo+gQQnO2EoOOS827JsNz rxCg== MIME-Version: 1.0 X-Received: by 10.202.214.133 with SMTP id n127mr10991111oig.52.1441765793570; Tue, 08 Sep 2015 19:29:53 -0700 (PDT) Received: by 10.202.197.147 with HTTP; Tue, 8 Sep 2015 19:29:53 -0700 (PDT) Received: by 10.202.197.147 with HTTP; Tue, 8 Sep 2015 19:29:53 -0700 (PDT) In-Reply-To: <8551C101-0E4B-4619-BF52-1B87BC6565D8@longcount.org> References: <100306673.40344407.1441279047901.JavaMail.zimbra@uoguelph.ca> <1564D4FA-9BE1-4E37-8E91-F14A009D6B62@icloud.com> <838814506.1858817.1441577912291.JavaMail.zimbra@uoguelph.ca> <8551C101-0E4B-4619-BF52-1B87BC6565D8@longcount.org> Date: Wed, 9 Sep 2015 07:59:53 +0530 Message-ID: Subject: Re: CEPH + FreeBSD From: Rakshith Venkatesh To: Mark Saad Cc: Rick Macklem , freebsd-fs@freebsd.org, Jordan Hubbard , Outback Dingo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2015 02:29:54 -0000 If there is a need to support cifs along with NFS then locking surely is needed to maintain data sanity and avoid problems due to concurrent access to files. On 09-Sep-2015 7:55 am, "Mark Saad" wrote: > > On Sep 8, 2015, at 9:59 PM, Outback Dingo wrote: > > > > On Wed, Sep 9, 2015 at 11:31 AM, Mark Saad wrote= : > >> All >> What about leofs. It's in ports has and s3 obj store and NFS support >> out of the box >> >> >> http://www.freshports.org/databases/leofs/ >> http://leo-project.net > > > LeoFS supperts NFSv3 and does not have a lock manager.... > > > Well, nlm it's not a hard requirement for most NFS things . NFS is there > for direct access of the data . So in its current form it's not a pnfs > setup , but there is no reason it could not be extended . > > Well it could be worse , manta, joyent's compute and storage platform ha= s > a NFS server written in node.js . Yes nfs in JavaScript , what else would > you expect from them . :) > > > --- > Mark Saad | nonesuch@longcount.org > > > >> >> >> >> --- >> Mark Saad | nonesuch@longcount.org >> >> > On Sep 6, 2015, at 6:18 PM, Rick Macklem wrote: >> > >> > Jordan Hubbard wrote: >> >> >> >>> On Sep 3, 2015, at 4:17 AM, Rick Macklem >> wrote: >> >>> >> >>> Slightly off topic but, btw, there is a port of GLusterFS and those >> folks >> >>> do seem >> >>> interested in seeing it brought "up to speed". I am not sure how >> mature it >> >>> is at >> >>> this point, but it has been known to build on amd64. (I don't have a= n >> amd64 >> >>> machine, >> >>> so I haven't gotten around to building/testing it, but I do plan to >> try and >> >>> use >> >>> it as a basis for a pNFS server, if I can figure out how to get the >> FH info >> >>> out of it. >> >>> I'm working on that;-) >> >> >> >> There are at least two distributed (multi-node) object stores for >> FreeBSD >> >> that I know of. >> >> >> >> One is glusterfs, for which I=E2=80=99m not even really clear on the = status of >> the >> >> ports for. I don=E2=80=99t see any glusterfs port in the master bran= ch of >> >> https://github.com/freebsd/freebsd-ports (or >> >> https://github.com/freebsd/freebsd-ports/tree/branches/2015Q3 for tha= t >> >> matter). >> >> >> >> Our FreeNAS ports tree (https://github.com/freenas/ports), in which >> we have a >> >> bit more latitude to add and curate our own ports, has both a >> net/glusterfs >> >> and sysutils/glusterfs, from separate sources (looks like we need to >> clean >> >> things up) - net/glusterfs lists craig001@lerwick.hopto.org as the >> >> MAINTAINER and is at version 3.6.2. The sysutils/glusterfs port list= s >> >> bapt@FreeBSD.org as the MAINTAINER and is at version 20140811. >> >> >> >> I=E2=80=99m not really sure about the provenance since we were simply >> evaluating >> >> glusterfs for awhile and may have pulled in interim versions from tho= se >> >> sources, but obviously it would be best to have an official maintaine= r >> and >> >> someone in the FreeBSD project actually curating a glusterfs port so >> that >> >> all users of FreeBSD can use it. It would also be fairly key to your >> own >> >> efforts, assuming you decide to pursue glusterfs as a foundation >> technology >> >> for pNFS. >> >> >> >> The other object store, which is pretty mature and is currently >> leading the >> >> pack (of two :) ) for inclusion into FreeNAS is RiakCS from Basho. >> There is >> >> a port currently in databases/riak but it=E2=80=99s pretty out of dat= e at >> version >> >> 1.4.12 (the current version is 2.0.1, with 2.0 being a major upgrade = of >> >> RiakCS). >> >> >> >> We are very interested in investigating various ways of shimming >> RiakCS to >> >> NFS, using RiakCS a back-end store. Is that something you=E2=80=99d= be >> amenable to >> >> discussing? I=E2=80=99d be happy to send you an amd64 architecture = machine to >> >> develop on. :) >> > Hmm. From a quick look at their web page (I looked once before as >> well), I don't >> > think RiakCS has what I need to do pNFS in a reasonable (for me) amoun= t >> of effort. >> > Two things that glusterFS has that I am hoping to use (and I don't >> think RiakCS has >> > either of these) are: >> > - A Fuse file system interface which allows the kernel nfsd to access >> the store as >> > a file system, so that it can provide the metadata services (NFS >> without the reads/writes). >> > - A userland NFSv3 server in each node which will allow the node to ac= t >> as a data server. >> > >> > If I am wrong and RiakCS does support a VFS file system interface (via >> Fuse or ???), then >> > please correct me. With that, it might be a reasonable alternative. >> > I'll admit I've spent a little time looking at the glusterFS sources >> and haven't yet >> > solved the problem of how to generate the file handles I need, but tha= t >> sounds trivial >> > compared with an entire Fuse and/or VFS file system interface, I think= ? >> > >> > In general, using a cloud object store to implement a pNFS server is a >> *mis*use of >> > the technology, imho. I think it may be possible with glusterFS, since >> that technology >> > seems to be based on a cluster file system, which is what a pNFS serve= r >> can also use. >> > >> > I think there would be a lot of work involved in mapping a POSIX file >> system onto the >> > Riak database and then exporting that via NFS, etc. It might also be >> more practical to >> > do this via a userland NFS service than the kernel based one currently >> in FreeBSD. >> > (glusterFS is starting to use the NFS-ganesha server, but I believe it >> is pretty Linux specific, >> > so I doubt it would be useful for Riak running on FreeBSD?) >> > >> > rick >> > >> >> - Jordan >> > _______________________________________________ >> > freebsd-fs@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> > >