moosefs-users

[MooseFS-Users] Chunkserver failed to start after reinstallation

[<18...@gm...>]

Hi, I have 1 chunkserver in the cluster need to be reinstalled, and
after configured it, chunkserver can't start

# /etc/init.d/moosefs-chunkserver start
Starting moosefs-chunkserver:
open files limit has been set to: 16384
working directory: /var/lib/mfs
lockfile created and locked
setting glibc malloc arena max to 8
setting glibc malloc arena test to 1
initializing mfschunkserver modules ...
hdd space manager: chunkserver without meta id shouldn't use drive
with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive
definition to ignore this (dangerous)
hdd space manager: chunkserver without meta id shouldn't use drive
with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive
definition to ignore this (dangerous)
hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file
init: hdd space manager failed !!!
error occured during initialization - exiting

Its working mfs disks were mounted

# mount /dev/sdb1 /mnt/sdb
# mount /dev/sdc1 /mnt/sdc

All mfs data disks were untouched, only remounted lastly.

How can I solve this error?
Thanks in advance.

Re: [MooseFS-Users] Chunkserver failed to start after reinstallation

[Aleksander W. <ale...@mo...>]

Hi,

If you have reinstalled chunkserver you probably removed
/var/lib/mfs/chunkserverid.mfs file with chunkserver metadata ID.
Now chunkserver and chunkserver disks are in mismatch condition.

Solution is simple but very dangerous.
*Please understand - this is security solution to prevent connecting
chunkserver to wrong master!!!*
If you have 100% sure that this disks will be connected to right master
and there is no possibility that there is some mistake in configuration
please remove .metaid file from /mnt/sdb and /mnt/sdc folder.

If you connect chunks to wrong master they will be removed.

Best regards
Aleksander Wieliczko
Technical Support Engineer
MooseFS.com <moosefs.com>

On 12/03/2015 08:41 AM, 18...@gm... wrote:
> Hi, I have 1 chunkserver in the cluster need to be reinstalled, and
> after configured it, chunkserver can't start
>
> # /etc/init.d/moosefs-chunkserver start
> Starting moosefs-chunkserver:
> open files limit has been set to: 16384
> working directory: /var/lib/mfs
> lockfile created and locked
> setting glibc malloc arena max to 8
> setting glibc malloc arena test to 1
> initializing mfschunkserver modules ...
> hdd space manager: chunkserver without meta id shouldn't use drive
> with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive
> definition to ignore this (dangerous)
> hdd space manager: chunkserver without meta id shouldn't use drive
> with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive
> definition to ignore this (dangerous)
> hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file
> init: hdd space manager failed !!!
> error occured during initialization - exiting
>
> Its working mfs disks were mounted
>
> # mount /dev/sdb1 /mnt/sdb
> # mount /dev/sdc1 /mnt/sdc
>
> All mfs data disks were untouched, only remounted lastly.
>
> How can I solve this error?
> Thanks in advance.
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-Users] Chunkserver failed to start after reinstallation

[<18...@gm...>]

Hi,

I only have one master server, so this way works. I'm seeing chunks
replication happens now.

Thanks for your support.

On Thu, Dec 3, 2015 at 4:58 PM, Aleksander Wieliczko
<ale...@mo...> wrote:
> Hi,
>
> If you have reinstalled chunkserver you probably removed
> /var/lib/mfs/chunkserverid.mfs file with chunkserver metadata ID.
> Now chunkserver and chunkserver disks are in mismatch condition.
>
> Solution is simple but very dangerous.
> Please understand - this is security solution to prevent connecting
> chunkserver to wrong master!!!
> If you have 100% sure that this disks will be connected to right master and
> there is no possibility that there is some mistake in configuration please
> remove .metaid file from /mnt/sdb and /mnt/sdc folder.
>
> If you connect chunks to wrong master they will be removed.
>
> Best regards
> Aleksander Wieliczko
> Technical Support Engineer
> MooseFS.com
>
> On 12/03/2015 08:41 AM, 18...@gm... wrote:
>
> Hi, I have 1 chunkserver in the cluster need to be reinstalled, and
> after configured it, chunkserver can't start
>
> # /etc/init.d/moosefs-
> chunkserver start
> Starting moosefs-chunkserver:
> open files limit has been set to: 16384
> working directory: /var/lib/mfs
> lockfile created and locked
> setting glibc malloc arena max to 8
> setting glibc malloc arena test to 1
> initializing mfschunkserver modules ...
> hdd space manager: chunkserver without meta id shouldn't use drive
> with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive
> definition to ignore this (dangerous)
> hdd space manager: chunkserver without meta id shouldn't use drive
> with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive
> definition to ignore this (dangerous)
> hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file
> init: hdd space manager failed !!!
> error occured during initialization - exiting
>
> Its working mfs disks were mounted
>
> # mount /dev/sdb1 /mnt/sdb
> # mount /dev/sdc1 /mnt/sdc
>
> All mfs data disks were untouched, only remounted lastly.
>
> How can I solve this error?
> Thanks in advance.
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple
> OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
>

Re: [MooseFS-Users] Chunkserver failed to start after reinstallation

[Aleksander W. <ale...@mo...>]

Hi,

Thank you for your information.
We will fix this problem in the nearest MooseFS release.

Best regards
Aleksander Wieliczko
Technical Support Engineer
MooseFS.com <moosefs.com>

On 12/03/2015 11:02 AM, 18...@gm... wrote:
> Hi,
>
> I only have one master server, so this way works. I'm seeing chunks
> replication happens now.
>
> Thanks for your support.
>
> On Thu, Dec 3, 2015 at 4:58 PM, Aleksander Wieliczko
> <ale...@mo...> wrote:
>> Hi,
>>
>> If you have reinstalled chunkserver you probably removed
>> /var/lib/mfs/chunkserverid.mfs file with chunkserver metadata ID.
>> Now chunkserver and chunkserver disks are in mismatch condition.
>>
>> Solution is simple but very dangerous.
>> Please understand - this is security solution to prevent connecting
>> chunkserver to wrong master!!!
>> If you have 100% sure that this disks will be connected to right master and
>> there is no possibility that there is some mistake in configuration please
>> remove .metaid file from /mnt/sdb and /mnt/sdc folder.
>>
>> If you connect chunks to wrong master they will be removed.
>>
>> Best regards
>> Aleksander Wieliczko
>> Technical Support Engineer
>> MooseFS.com
>>
>> On 12/03/2015 08:41 AM, 18...@gm... wrote:
>>
>> Hi, I have 1 chunkserver in the cluster need to be reinstalled, and
>> after configured it, chunkserver can't start
>>
>> # /etc/init.d/moosefs-
>> chunkserver start
>> Starting moosefs-chunkserver:
>> open files limit has been set to: 16384
>> working directory: /var/lib/mfs
>> lockfile created and locked
>> setting glibc malloc arena max to 8
>> setting glibc malloc arena test to 1
>> initializing mfschunkserver modules ...
>> hdd space manager: chunkserver without meta id shouldn't use drive
>> with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive
>> definition to ignore this (dangerous)
>> hdd space manager: chunkserver without meta id shouldn't use drive
>> with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive
>> definition to ignore this (dangerous)
>> hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file
>> init: hdd space manager failed !!!
>> error occured during initialization - exiting
>>
>> Its working mfs disks were mounted
>>
>> # mount /dev/sdb1 /mnt/sdb
>> # mount /dev/sdc1 /mnt/sdc
>>
>> All mfs data disks were untouched, only remounted lastly.
>>
>> How can I solve this error?
>> Thanks in advance.
>>
>> ------------------------------------------------------------------------------
>> Go from Idea to Many App Stores Faster with Intel(R) XDK
>> Give your users amazing mobile app experiences with Intel(R) XDK.
>> Use one codebase in this all-in-one HTML5 development environment.
>> Design, debug & build mobile apps & 2D/3D high-impact games for multiple
>> OSs.
>> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
>> _________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>>