Hi Adrien...
Thanks for the pointer. It effectually solved our issue.
Cheers
G.
On 12/04/2015 12:53 AM, Adrien Gillard wrote:
This is the clean way to handle this. But you can also use udev to do
this at boot. From what I found on the mailing list and made working
before using GUID :
cat > /etc/udev/rules.d/89-ceph-journal.rules << EOF
KERNEL=="sda?" SUBSYSTEM=="block" OWNER="ceph" GROUP="disk" MODE="0660"
KERNEL=="sdb?" SUBSYSTEM=="block" OWNER="ceph" GROUP="disk" MODE="0660"
KERNEL=="sdc?" SUBSYSTEM=="block" OWNER="ceph" GROUP="disk" MODE="0660"
EOF
On Thu, Dec 3, 2015 at 2:28 PM, Florent B <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Is setting GUID is the only way to fix this ? I don't use GPT but
MBR and I don't want to try conversion on production servers...
On 12/03/2015 08:39 AM, Adrien Gillard wrote:
You should check that the owner of your ceph partitions (both
journal and data) is 'ceph', otherwise the ceph user won't mount it.
You can simply do : chown ceph:disk /dev/sdc3
If this solve your issue you should set the GPT GUID [1] of the
partitions with a tool like sgdisk to make this persistent across
reboot.
I think only your journal is affected as ceph-disk does not
prepare the partition (WARNING:ceph-disk:Journal /dev/sdc3 was
not prepared with ceph-disk. Symlinking directly)
[1]
https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs
--
-----------------------------------------------------------------------------------------
Adrien GILLARD
+33 (0)6 29 06 16 31
[email protected] <mailto:[email protected]>
--
Goncalo Borges
Research Computing
ARC Centre of Excellence for Particle Physics at the Terascale
School of Physics A28 | University of Sydney, NSW 2006
T: +61 2 93511937
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
