On Tue, May 31, 2011 at 9:17 AM, Gregory Farnum <gregf@xxxxxxxxxxxxxxx> wrote: > On Sat, May 28, 2011 at 7:45 PM, Sylar Shen <kimulaaa@xxxxxxxxx> wrote: >> Hi Gregory, >> Thanks for your information very much! >> Dropbox could limit the quota value of each user. >> Does Dropbox implement the quota function by recording every size of >> file in its own database? >> Or Dropbox just controls the quota of each user by the client application? >> If Dropbox did neither of the two approaches above, how did they do? >> Sorry it may be a little stupid question but I am curious about that......:p > I really have no idea how Dropbox works; it's got no relation to Ceph > except that I use it. ;) > >> By the way, the test of re-exporting NFS I did worked not bad. >> And I am wondering since Ceph can re-export NFS, then can Ceph >> re-export SAMBA that connects to windows? > We don't have a samba re-export functionality, although you can just > run samba on a Ceph mount if you like. And I think bchrisman is > working on one, but you'd have to ask him about that. :) Richard Sharpe and I have a VFS layer integrating Ceph (libceph) with Samba that is just a stone's throw from basic functionality. Current status: mount/init, stat, opendir, readdir, and a few other operations are working. We're chasing down what appears to be a few smaller problems related to read/write. We've also used to the acl_xattr module to avoid doing a bunch of acl translations, though we could probably hit that in a second pass. One future critical issue here is going to be the caching mechanism and how it works with Samba's process model (process per connection). This merits a discussion about how multiple libceph clients will work together when run on the same host. > -Greg > -- > 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 > -- 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
