Re: issue with mounting ceph cluster over NFS

2012-05-16 Thread Josh Durgin
On 05/15/2012 08:31 AM, madhusudhana U wrote: Hi, I have a ceph cluster with 5 nodes, in which 2 are MDS, 3 are MON and all Is only one MDS active? 5 acts as OSD. I have mounted the ceph cluster in one node in the cluster and exported the mounted dir via NFS. Below is my mount and exports

Re: MDS crash, wont startup again

2012-05-16 Thread Felix Feinhals
Hi again, anything on this Problem? Seems that the only choice for me is to reinitialize the whole cephfs (mkcephfs...) :( 2012/5/10 Felix Feinhals f...@turtle-entertainment.de: Hi List, we installed a ceph cluster with ceph version 0.46. 3 OSDs, 3 MONs and 3 MDSs. After copying a bunch of

Re: 'rbd map' asynchronous behavior

2012-05-16 Thread Andrey Korolyov
This is most likely due to a recently-fixed problem. The fix is found in this commit, although there were other changes that led up to it: 32eec68d2f rbd: don't drop the rbd_id too early It is present starting in Linux kernel 3.3; it appears you are running 2.6? Nope, it`s just Debian kernel

Re: issue with mounting ceph cluster over NFS

2012-05-16 Thread madhusudhana U
Is only one MDS active? Yes only one MDS is active Does the build work on ceph-fuse without nfs? I can't run build without NFS on ceph-fuse because, the build runs on a cluster (we use LSF for it) where each machine mounts the directory. The build is spit into many small jobs [around 800 in

[PATCH 1/2] rbd: allow importing from stdin

2012-05-16 Thread Christian Brunner
This patch allows importing images from stdin with the following command: rbd import --size=size in MB - [dest-image] Signed-off-by: Christian Brunner c...@muc.de --- src/rbd.cc | 37 + 1 files changed, 25 insertions(+), 12 deletions(-) diff --git

[PATCH 2/2] rbd: skip empty blocks during import

2012-05-16 Thread Christian Brunner
Check for empty blocks while importing an image. When a read block only consists of zeroes, the import is simply skipping the write. This way you non-sparse images will become sparse rbd images. Signed-off-by: Christian Brunner c...@muc.de --- src/rbd.cc | 44

Re: [PATCH 1/2] rbd: allow importing from stdin

2012-05-16 Thread Tommi Virtanen
On Wed, May 16, 2012 at 7:27 AM, Christian Brunner c...@muc.de wrote: This patch allows importing images from stdin with the following command:   rbd import --size=size in MB - [dest-image] Signed-off-by: Christian Brunner c...@muc.de ---  src/rbd.cc |   37

Re: Ceph on btrfs 3.4rc

2012-05-16 Thread Josef Bacik
On Mon, May 14, 2012 at 10:20:48AM -0400, Josef Bacik wrote: On Mon, May 14, 2012 at 04:19:37PM +0200, Martin Mailand wrote: Hi Josef, Am 11.05.2012 21:16, schrieb Josef Bacik: Heh duh, sorry, try this one instead. Thanks, With this patch I got this Bug: Yeah Christian reported

[PATCH 1/2 v2] rbd: allow importing from stdin

2012-05-16 Thread Christian Brunner
This patch allows importing images from stdin with the following command: rbd import --size=size in MB - [dest-image] v1 - v2: stat stdin as well Signed-off-by: Christian Brunner c...@muc.de --- src/rbd.cc | 26 +++--- 1 files changed, 19 insertions(+), 7 deletions(-)

Re: [PATCH 1/2 v2] rbd: allow importing from stdin

2012-05-16 Thread Tommi Virtanen
On Wed, May 16, 2012 at 3:25 PM, Yehuda Sadeh Weinraub yehud...@gmail.com wrote: I'd rather not pass size for stdin. We should instead make it so that we don't read size at all and just importing while !eof (or do that only when size is 0). We'd need to create the image with size=0 and update

Re: [PATCH 1/2 v2] rbd: allow importing from stdin

2012-05-16 Thread Josh Durgin
On 05/16/2012 04:51 PM, Tommi Virtanen wrote: On Wed, May 16, 2012 at 3:25 PM, Yehuda Sadeh Weinraub yehud...@gmail.com wrote: I'd rather not pass size for stdin. We should instead make it so that we don't read size at all and just importing while !eof (or do that only when size is 0). We'd

Re: [PATCH 1/2 v2] rbd: allow importing from stdin

2012-05-16 Thread Tommi Virtanen
On Wed, May 16, 2012 at 4:58 PM, Josh Durgin josh.dur...@inktank.com wrote: librbd prevents you from writing beyond the bounds of an image. If we keep that restriction, you'd need to resize the image to have enough space for the import, and resize down to the final size at the end. That's