Re: To upgrade the ceph version(v0.26)

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

 



Thanks for your help!
I am very appreciate^^

2011/4/11 Gregory Farnum <gregory.farnum@xxxxxxxxxxxxx>:
> On Thu, Apr 7, 2011 at 7:16 PM, doki74216@xxxxxxxxx <doki74216@xxxxxxxxx> wrote:
>> Hi,
>>
>> MY current version is v0.24.3, I want to upgrade version to v 0.26.
>> And my  Linux OS is Fedora 14.
>>
>> I want to know my step is correctly or not?
>> Here is my upgraded steps:
>> 1) We stop the current system (v0.24.3)by "/etc/init.d/ceph -a stop "
>> 2) We start to download the newest version(v0.26) and install it.
>> 3) Then we mkcephfs (by "mkcephfs -c /etc/ceph/ceph.conf --allhosts --mkbtrfs
>> -k keyring.bin") and start it(by " /etc/init.d/init-ceph -a -c
>> /etc/ceph/ceph.conf start").
>>
>> But there's a problem I met when I was started the Ceph.
>> The system stops running and it shows the error messages as shown below:
>>
>>
>> === mds.0 ===
>> Starting Ceph mds0 on host4...
>>  ** WARNING: Ceph is still under heavy development, and is only suitable for **
>>  **          testing and review.  Do not trust it with important data.       **
>> terminate called after throwing an instance of 'ceph::buffer::end_of_buffer'
>>  what():  buffer::end_of_buffer
>> bash: line 1: 24409 Segmentation fault      (core dumped)
>> /usr/local/bin/cmds -i 0 -c /tmp/ceph.conf.5135
>> failed: 'ssh host4  /usr/local/bin/cmds -i 0 -c /tmp/ceph.conf.5135 '
>
> Hmm. That's not something I'd expect to see on startup, especially
> with a fresh filesystem. Can you get the backtrace from gdb?
>
>> The second question is when we upgrate the ceph successfully.
>> Is there any tool to transfer the existing data (which from the old
>> ceph system) to the newest system?
>> Because we thought the data in the older version(eg. 0.24.3) is
>> slightly different from the newer version(eg. 0.26)?
>> I want to know the data will be still correctly?
> The on-disk format doesn't change too often and we try and keep it
> backwards compatible -- you should be able to start up new daemons on
> old data and in the worst case they will slowly upgrade it. If this
> doesn't work then there's a bug somewhere.
> So, no, you should not lose your data.
>
> However, in the list of steps you took, you ran mkcephfs, and that did
> kill all your data (I thought there were several warnings about this
> when using the tool?). Running mkcephfs is only necessary when
> creating the filesystem, not when upgrading it!
> -Greg
>
--
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