[sheepdog-users] [sheepdog] Sheepfs' questions

Andrew J. Hobbs ajhobbs at desu.edu
Wed Sep 3 15:08:38 CEST 2014

Disregarding locking, this could be done if you run GFS/GFS2/OCFS on top of it and treating the sheepdog storage as purely a shared block device.  You couldn't use object caching or journaling, but due to sheepdog (by default) requiring confirmation of write before signaling completion, this should work.  In fact, it may be worth considering making locking an option rather than default for this very purpose.

On 09/03/2014 02:13 AM, Valerio Pachera wrote:

2014-09-02 20:06 GMT+02:00 黃昭龍 <regis2261 at gmail.com<mailto:regis2261 at gmail.com>>:

   And use sheepfs to mount the vdi to use as a normal file system storage directory in two nodes.

Why are you doing this?
I think you must not access a vdi from two different nodes.
With the latest master that can't even work because of vdi locking.

   When I try to use wget to download a iso file to this mount dir,I found that the download progress will hang for a while and continue to download.
   This situation will repeat several times in the whole download period.
   Can I adjust the sheep or sheepfs option(I have open 10G directio objectcache) to improve this problem ?

At what speed is the download running?

  Can I let the two nodes' mounted directory sync for the same vdi without remouting ?

I suggest instead to export the directory by nfs.

  I try to test Sheepdog block device(sbd),But I can't find the source of sbd in the downloaded source code.

sbd is a new feature so you can't find in 0.8.3 stable release.
You have to use master branch.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ajhobbs.vcf
Type: text/x-vcard
Size: 353 bytes
Desc: ajhobbs.vcf
URL: <http://lists.wpkg.org/pipermail/sheepdog-users/attachments/20140903/d55df130/attachment-0005.vcf>

More information about the sheepdog-users mailing list