This is probably by design..
On Thu, Dec 15, 2016 at 11:48 AM, Marco Gaiarin wrote:
>
> Sorry, i came back to this topic because i've done some more tests.
>
> Seems that 'pveceph' tool have some trouble creating OSD with journal
> on ''nonstandard'' partition, for examply on a
Sorry, i came back to this topic because i've done some more tests.
Seems that 'pveceph' tool have some trouble creating OSD with journal
on ''nonstandard'' partition, for examply on a MD device.
A command like:
pveceph createosd /dev/sde --journal_dev /dev/md4
fail mysteriously (OSD
Mandi! Alwin Antreich
In chel di` si favelave...
> The ratio for SDD journal to OSD disks, can be done by a simple dd test. Take
> the write speed of the SSD and divide it
> through the write speed of the OSD, then you will get the max number of disks
> that can be used on one SSD, without
>
Mandi! Alwin Antreich
In chel di` si favelave...
> I have to ask a more general question here, why are you putting the journal
> on a RAID1?
For safety?
> For better performance and less
> complexity the journal should reside on standalone SSDs. With the RAID1 you
> limit the speed of the
Hello Marco,
On 10/13/2016 12:13 PM, Marco Gaiarin wrote:
>
> I'm a bit confused.
>
> I'm trying to create 4 OSD on a server, where the SO reside on a
> raid-1. On the same (couple of) disk there's 4 50MB partition for
> the journal (the two disks are SSD).
> Better with a command:
I have to
I'm a bit confused.
I'm trying to create 4 OSD on a server, where the SO reside on a
raid-1. On the same (couple of) disk there's 4 50MB partition for
the journal (the two disks are SSD).
Better with a command:
root@vedovanera:~# blkid
/dev/sdf1: UUID="75103d23-83a6-9f5d-eb1e-f021e729041b"