Re: ceph osd create

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Found it (digging through the source code to find a guess, since it is
in no way obvious):  --osd-uuid <uuid>

On Tue, Aug 21, 2012 at 4:38 PM, Mandell Degerness
<mandell@xxxxxxxxxxxxxxx> wrote:
> Thanks, Sage.  This is what I was looking for, but what version of
> ceph do I need for this to work (it isn't there in Argonaut)?  See
> below:
>
> # ceph-osd -c /etc/ceph/ceph.conf --fsid
> 8296cc23-9c11-44d7-84c1-16866ef9c4f7 -i 50 --mkfs --osd-fsid
> e1097bd8-c931-4e2e-8ccb-332a954adace
>   --conf/-c        Read configuration from the given configuration file
>   -d               Run in foreground, log to stderr.
>   -f               Run in foreground, log to usual location.
>   --id/-i          set ID portion of my name
>   --name/-n        set name (TYPE.ID)
>   --version        show version and quit
>
>   --debug_ms N
>         set message debug level (e.g. 1)
> 2012-08-21 23:26:50.774858 7f1be9ac1780 -1 unrecognized arg --osd-fsid
> 2012-08-21 23:26:50.774864 7f1be9ac1780 -1 usage: ceph-osd -i osdid
> [--osd-data=path] [--osd-journal=path] [--mkfs] [--mkjournal]
> [--convert-filestore]
> 2012-08-21 23:26:50.774915 7f1be9ac1780 -1    --debug_osd N   set
> debug level (e.g. 10)
>
> # ceph --version
> ceph version 0.48.1argonaut (commit:a7ad701b9bd479f20429f19e6fea7373ca6bba7c)
>
> Tommi - Thank you for the suggestion of ceph-disk-prepare and
> ceph-disk-activate, but they work at too high of a level for our
> usage.  We need finer control of the block devices.
>
> Regards,
> Mandell Degerness
>
> On Tue, Aug 21, 2012 at 11:15 AM, Sage Weil <sage@xxxxxxxxxxx> wrote:
>> On Tue, 21 Aug 2012, Mandell Degerness wrote:
>>> OK.  I think I'm getting there.
>>>
>>> I want to be able to generate the fsid to be used in the OSD (from the
>>> file system fsid, if that matters).  Is there a way to inject the fsid
>>> when initializing the OSD directory?  It doesn't seem to be
>>> documented.  The alternative would require that we mount the OSD in a
>>> temp dir to read the fsid file, determine the OSD number, and then
>>> re-mount it where it belongs, which seems the wrong way to go.
>>
>> You can feed in the fsid to ceph-osd --mkfs with --osd-fsid <uuid>.
>>
>> sage
>>
>>>
>>> Regards,
>>> Mandell Degerness
>>>
>>> On Mon, Aug 20, 2012 at 4:26 PM, Tommi Virtanen <tv@xxxxxxxxxxx> wrote:
>>> > On Mon, Aug 20, 2012 at 3:53 PM, Mandell Degerness
>>> > <mandell@xxxxxxxxxxxxxxx> wrote:
>>> >> We're running Argonaut and it only has the OSD id in the whoami file
>>> >> and nothing else.
>>> >
>>> > My bad, I meant the file "fsid" (note, not "ceph_fsid").
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux