Search results

I'm getting allot of errors like the below and in the end the migration fails because of this. What can I do against this ? Mar 21 13:25:54 rsync: set_acl: sys_acl_set_file(107/var/www/name, ACL_TYPE_ACCESS): Operation not supported (95)

Ahhh it is included in 2.6.34 and later ... In =< 2.6.32 it has to be manually added http://ceph.com/w/index.php?title=Building_kernel_client

Can I request it as a loadable module ? :)

Is this now added in the new kernel ?

How do you include the authentication key that you now manually copy in /etc/pve/priv/ceph/ceph.keyring through the webinterface ? Or will that have to be done manually ?

mapping the rbd device like rbd map rbdname format the rbd device and then mount it to a directory, which you can then add to proxmox and run your containers on. Doing the same now in a test, only now I have mounted the rbd on a proxy and running a iSCSI export to export the device, then add...

What kind of Ceph RBD support is included, other then what was already included in the stable ? modprobe rbd still gives a module not found ? So its still not possible to map a rbd device on the host. This would be awesome to run OpenVZ on ....

Hmm I now tried to mount a rbd device from ceph, is the kernel module for rbd also not included ? Is there a way to include it without rebuilding the kernel?

Will the Ceph FS be integrated in the proxmox kernel ?

Ceph RBD storage is working perfect ! Now I'm trying to run CephFS for running OpenVZ images on the storage cluster. When mounting Ceph with the Ceph-Fuse mount options, I get the following error when entering containers or doing anything in a container. "Value too large for defined data type"...

I stopped the service as a online migration on NFS or GlusterFS is not possible :)

Not sure if this is a bug aswell, but when trying todo a offline migration with HA enabled, a error occurs aswel. Executing HA migrate for CT 100 to node nod19 Trying to migrate pvevm:100 to nod19...Temporary failure; try again TASK ERROR: command 'clusvcadm -M pvevm:100 -m nod19' failed: exit...

ah thnx for the fast respone, just a small note this is not NFS but on GlusterFS

I am trying to do a online migration but getting a strange error on the chkpoint part. Does anyone know why it does this ? Apr 02 21:54:58 starting migration of CT 100 to node 'nod19' (193.47.XX.XX) Apr 02 21:54:58 container is running - using online migration Apr 02 21:54:58 container data is...

Are there people here who are running MooseFS on there Proxmox installations and can explain there setup ? Very interested in running this....

I found it ! Somehow because a OpenVZ ve ran out of its memory, it started shutting down processes .... LVM seems to depend on udev which was not running ... Thanks for the help dietmar !

Nope something got messed up ... root@node:~# lvcreate --size 1000M --name atest pve /dev/mapper/pve-atest: open failed: No such file or directory /dev/pve/atest: not found: device not cleared Aborting. Failed to wipe start of new LV. No clue how I can clear this tho :S

none also not in messages ...

Hmm I get root@node:~# lvcreate --size 1000M --snapshot --name vzsnap-node-0 /dev/pve/data /dev/mapper/pve-vzsnap--node--0: open failed: No such file or directory /dev/pve/vzsnap-node-0: not found: device not cleared Aborting. Failed to wipe snapshot exception store. strange :S

root@node:~# vgs VG #PV #LV #SN Attr VSize VFree pve 1 3 0 wz--n- 929.50g 16.00g