Re: [ceph-devel] v0.19.1 stable updates

2010-03-09 Thread Anton
Sage, do you think CEPH now is ok (stable enough) to be atleast sure that uploaded data will not be corrupted, (and could be recovered in the case of fault) - for use as simple file store - say in the scenario of "upload/modify rarely, read often"?. Right now I use Gluster as clustered FS - bu

Re: [ceph-devel] v0.19.1 stable updates

2010-03-09 Thread Roland Rabben
Same story with me. Currently a frustrated Gluster user waiting for that message saying things are safe to store data with CEPH - in production. Regards, Roland 2010/3/9 Anton > Sage, do you think CEPH now is ok (stable enough) to be > atleast sure that uploaded data will not be corrupted, (a

Re: [ceph-devel] kvm driver

2010-03-09 Thread Christian Brunner
On Mon, Mar 08, 2010 at 10:18:11PM +, Sage Weil wrote: > > > > The patch for qemu-0.12.3 is attached. I would appreciate it if someone > > with a deeper understanding of the signal handling in librados and/or > > kvm could have a look. > > Yehuda is taking a look at it now. The signals are u

Re: [ceph-devel] kvm driver

2010-03-09 Thread Sage Weil
On Tue, 9 Mar 2010, Christian Brunner wrote: > On Mon, Mar 08, 2010 at 10:18:11PM +, Sage Weil wrote: > > Is there any particular reason to restrict the 'device name' to 12 chars? > > On the ceph blog I have read that the name of an object is a fixed-size > 20 byte identifier. That's why I've

Re: [ceph-devel] kvm driver

2010-03-09 Thread Christian Brunner
> > Yehuda is taking a look at it now. The signals are used to wake up > > blocking read()/write()/connect(), but we should be able to use poll() or > > select() instead (and clean things up in the process). > > Great! - That was really a quick response. I will check out the current > git versi

Re: [ceph-devel] kvm driver

2010-03-09 Thread Sage Weil
On Tue, 9 Mar 2010, Christian Brunner wrote: > > > Yehuda is taking a look at it now. The signals are used to wake up > > > blocking read()/write()/connect(), but we should be able to use poll() or > > > select() instead (and clean things up in the process). > > > > Great! - That was really a