[sheepdog-users] SIGABRT when doing: dog vdi check

Hitoshi Mitake mitake.hitoshi at gmail.com
Sun Jan 5 17:08:34 CET 2014

At Sat, 4 Jan 2014 13:35:49 +0800,
Liu Yuan wrote:
> On Sat, Jan 04, 2014 at 01:28:27PM +0800, Liu Yuan wrote:
> > > Last question is about checksumming of data. Is it better to lay sheep
> > > on ext4 and use btrfs/zfs on the VDI or lay sheep on btrfs and use ext4
> > > on top of VDI?
> > > 
> > 
> > Either is okay, since sheepdog provide block device abstraction and don't care
> > how you use it. For file system that you lay sheep on, ext4 or xfs is suggested
> > since we just expect posix xattr support on the underlying filesystem.
> > 
> > By the way, if you are only interested in block device (not for VM), you can take
> > a look at iSCSI (https://github.com/sheepdog/sheepdog/wiki/General-protocol-support-%28iSCSI-and-NBD%29#iscsi)
> > 
> > Which probably will outperform sheepfs because sheepfs is based on fuse and
> > performanc is heavily constrained by it.
> > 
> Oh, I have to mention that sheepfs has some advantage over iSCSI, recently we
> add hyper volume support, with which we support as large as 16PB vdi and currently
> only sheepfs and http storage, similar to Amazon S3(We don't have wiki for it
> but I'll write it soon) support hyper volume.

I'll implement the features of erasure coding and hyper volume in the tgt driver
soon. But I have to implement a feature of iSCSI multipath first.


More information about the sheepdog-users mailing list