moosefs-users — Mailing list for MooseFS Users

[MooseFS-Users] MooseFS Repository - Ubuntu 16.04 ?

[Wolfgang <moo...@wo...>]

Hi Piotr!

Regarding versions - can you tell me when there will be Ubuntu 16.04 LTS 
xenial packages in the repository for MooseFS ?

Thank you very much!

Regards
Wolfgang


On 2016-08-05 12:02, Piotr Robert Konopelko wrote:
> Hi Wolfgang,
>
> it was not changed yet, because we still notice a lot of users using 
> "stable" in their repositories - there's a lot of entries with 
> "stable" in our http server logs.
> We decided to give users some extra time - it will be changed soon.
>>
>> Am I save if I use the
>> http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty
>> URL in my sources.list file
>>
> Of course! This is the best way - i.e. to decide consciously which 
> version you want to use at the moment and set it explicite in 
> sources.list and stop using "stable".
>
> In case of big installations, some users still may want to stay with 
> MooseFS 2.0 for a while, we understand this - because of this reason 
> we created "moosefs-2" - to let them stay and prepare to the conscious 
> and planned upgrade.
>
> Best regards,
>
> -- 
>
> MooseFS <https://moosefs.com>
>
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> e-mail: pio...@mo... <mailto:pio...@mo...>
> www: https://moosefs.com
>
> Twitter <https://twitter.com/MooseFS> Facebook 
> <https://www.facebook.com/moosefs> LinkedIn 
> <https://www.linkedin.com/company/moosefs> GitHub 
> <https://github.com/moosefs>
>
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they 
> are addressed. If you have received it by mistake, please let us know 
> by e-mail reply and delete it from your system; you may not copy this 
> message or disclose its contents to anyone. Finally, the recipient 
> should check this email and any attachments for the presence of 
> viruses. Core Technology accepts no liability for any damage caused by 
> any virus transmitted by this email.
>
>
>> On 05 Aug 2016, at 9:33 AM, Wolfgang <moo...@wo... 
>> <mailto:moo...@wo...>> wrote:
>>
>> Hi Peter!
>>
>> When checking the URL:
>> http://ppa.moosefs.com/stable/apt/ubuntu/trusty/pool/main/m/moosefs/
>> it still shows me the 2.0.89-1 version files - was the change at the 
>> repository structure not executed as you pointed out?
>>
>> Am I save if I use the
>> http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty
>> URL in my sources.list file?
>>
>> Thank you for this great product!
>> Wolfgang, Austria
>>
>>
>>
>>
>> On 2016-07-16 03:51, Piotr Robert Konopelko wrote:
>>> Dear MooseFS Users,
>>>
>>> please remember about those important changes in MooseFS repository structure which will be introduced in about 2 weeks.
>>>
>>>
>>> Best regards,
>>> Peter from MooseFS Team
>>>
>>> -- Piotr Robert Konopelko MooseFS Technical Support Engineer | 
>>> moosefs.com <http://moosefs.com>
>>>> >On 10 Jun 2016, at 7:20 PM, Piotr Robert Konopelko<pio...@mo...>  wrote:
>>>> >
>>>> >Dear MooseFS Users,
>>>> >
>>>> >we'd like to inform you, that we decided to change our repository structure.
>>>> >(examples based on Ubuntu 14.04)
>>>> >
>>>> >
>>>> >
>>>> >debhttp://ppa.moosefs.com/stable/apt/ubuntu/trusty  trusty main
>>>> >
>>>> >"stable" in the entry above now points to the latest stable MooseFS from 2.0 branch (at this moment - 2.0.89).
>>>> >*This behaviour will be kept until end of July 2016*
>>>> >
>>>> >*Starting from August 1, 2016, "stable" in the entry above will point to the latest stable MooseFS from 3.0 branch (at this moment - 3.0.77)*
>>>> >
>>>> >"stable" symlink is going to be removed at December 31, 2016 - this method will **NOT** work after this date.
>>>> >
>>>> >
>>>> >
>>>> >Starting from today, it is also possible to use the following entries, so you can switch your repositories consciously either to MooseFS 2 or MooseFS 3 (***we recommend reconfigure your repos before mentioned end of July 2016***):
>>>> >
>>>> >debhttp://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty  trusty main
>>>> >--> this entry points to the newest stable MooseFS 3.0.x version (3.0.77 at the time of writing this e-mail)
>>>> >
>>>> >debhttp://ppa.moosefs.com/moosefs-2/apt/ubuntu/trusty  trusty main
>>>> >--> this entry points to the newest stable MooseFS 2.0.x version (2.0.89 at the time of writing this e-mail)
>>>> >
>>>> >
>>>> >
>>>> >Of course it is still possible to use "version control" in the repository URL, i.e. version number instead of "stable", "moosefs-3" or "moosefs-2":
>>>> >
>>>> >debhttp://ppa.moosefs.com/3.0.77/apt/ubuntu/trusty  trusty main
>>>> >
>>>> >--> the entry above will still work and at the moment we don't plan to change it.
>>>> >
>>>> >
>>>> >
>>>> >This information will be published on our website soon.
>>>> >
>>>> >In case of any questions, please don't hesitate to ask!:)
>>>> >
>>>> >
>>>> >Best regards,
>>>> >Peter from MooseFS Team
>>>> >
>>>> >-- 
>>>> >Piotr Robert Konopelko
>>>> >MooseFS Technical Support Engineer |moosefs.com <http://moosefs.com>
>>> ------------------------------------------------------------------------------
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
>>> reports.http://sdm.link/zohodev2dev
>>> _________________________________________
>>> moosefs-users mailing list
>>> moo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>> ------------------------------------------------------------------------------
>> _________________________________________
>> moosefs-users mailing list
>> moo...@li... 
>> <mailto:moo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>

Re: [MooseFS-Users] IMPORTANT Changes in MooseFS Repository structure

[Piotr R. K. <pio...@mo...>]

Hi Wolfgang,

it was not changed yet, because we still notice a lot of users using "stable" in their repositories - there's a lot of entries with "stable" in our http server logs.
We decided to give users some extra time - it will be changed soon.
> Am I save if I use the
> http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty <http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty>
> URL in my sources.list file
> 

Of course! This is the best way - i.e. to decide consciously which version you want to use at the moment and set it explicite in sources.list and stop using "stable".

In case of big installations, some users still may want to stay with MooseFS 2.0 for a while, we understand this - because of this reason we created "moosefs-2" - to let them stay and prepare to the conscious and planned upgrade.

Best regards, 

--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 05 Aug 2016, at 9:33 AM, Wolfgang <moo...@wo...> wrote:
> 
> Hi Peter!
> 
> When checking the URL:
> http://ppa.moosefs.com/stable/apt/ubuntu/trusty/pool/main/m/moosefs/ <http://ppa.moosefs.com/stable/apt/ubuntu/trusty/pool/main/m/moosefs/>
> it still shows me the 2.0.89-1 version files - was the change at the repository structure not executed as you pointed out?
> 
> Am I save if I use the
> http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty <http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty>
> URL in my sources.list file?
> 
> Thank you for this great product!
> Wolfgang, Austria
> 
> 
> 
> On 2016-07-16 03:51, Piotr Robert Konopelko wrote:
>> Dear MooseFS Users,
>> 
>> please remember about those important changes in MooseFS repository structure which will be introduced in about 2 weeks.
>> 
>> 
>> Best regards,
>> Peter from MooseFS Team
>> 
>> -- 
>> Piotr Robert Konopelko
>> MooseFS Technical Support Engineer | moosefs.com
>> 
>>> > On 10 Jun 2016, at 7:20 PM, Piotr Robert Konopelko <pio...@mo...> <mailto:pio...@mo...> wrote:
>>> > 
>>> > Dear MooseFS Users,
>>> > 
>>> > we'd like to inform you, that we decided to change our repository structure.
>>> > (examples based on Ubuntu 14.04)
>>> > 
>>> > 
>>> > 
>>> > deb http://ppa.moosefs.com/stable/apt/ubuntu/trusty <http://ppa.moosefs.com/stable/apt/ubuntu/trusty> trusty main
>>> > 
>>> > "stable" in the entry above now points to the latest stable MooseFS from 2.0 branch (at this moment - 2.0.89).
>>> > *This behaviour will be kept until end of July 2016*
>>> > 
>>> > *Starting from August 1, 2016, "stable" in the entry above will point to the latest stable MooseFS from 3.0 branch (at this moment - 3.0.77)*
>>> > 
>>> > "stable" symlink is going to be removed at December 31, 2016 - this method will **NOT** work after this date.
>>> > 
>>> > 
>>> > 
>>> > Starting from today, it is also possible to use the following entries, so you can switch your repositories consciously either to MooseFS 2 or MooseFS 3 (***we recommend reconfigure your repos before mentioned end of July 2016***):
>>> > 
>>> > deb http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty <http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty> trusty main
>>> > --> this entry points to the newest stable MooseFS 3.0.x version (3.0.77 at the time of writing this e-mail)
>>> > 
>>> > deb http://ppa.moosefs.com/moosefs-2/apt/ubuntu/trusty <http://ppa.moosefs.com/moosefs-2/apt/ubuntu/trusty> trusty main
>>> > --> this entry points to the newest stable MooseFS 2.0.x version (2.0.89 at the time of writing this e-mail)
>>> > 
>>> > 
>>> > 
>>> > Of course it is still possible to use "version control" in the repository URL, i.e. version number instead of "stable", "moosefs-3" or "moosefs-2":
>>> > 
>>> > deb http://ppa.moosefs.com/3.0.77/apt/ubuntu/trusty <http://ppa.moosefs.com/3.0.77/apt/ubuntu/trusty> trusty main
>>> > 
>>> > --> the entry above will still work and at the moment we don't plan to change it.
>>> > 
>>> > 
>>> > 
>>> > This information will be published on our website soon.
>>> > 
>>> > In case of any questions, please don't hesitate to ask! :)
>>> > 
>>> > 
>>> > Best regards,
>>> > Peter from MooseFS Team
>>> > 
>>> > -- 
>>> > Piotr Robert Konopelko
>>> > MooseFS Technical Support Engineer | moosefs.com
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are 
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
>> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
>> reports.http://sdm.link/zohodev2dev
>> _________________________________________
>> moosefs-users mailing list
>> moo...@li... <mailto:moo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users <https://lists.sourceforge.net/lists/listinfo/moosefs-users>
> 
> ------------------------------------------------------------------------------
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-Users] IMPORTANT Changes in MooseFS Repository structure

[Wolfgang <moo...@wo...>]

Hi Peter!

When checking the URL:
http://ppa.moosefs.com/stable/apt/ubuntu/trusty/pool/main/m/moosefs/
it still shows me the 2.0.89-1 version files - was the change at the 
repository structure not executed as you pointed out?

Am I save if I use the
http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty
URL in my sources.list file?

Thank you for this great product!
Wolfgang, Austria




On 2016-07-16 03:51, Piotr Robert Konopelko wrote:
> Dear MooseFS Users,
>
> please remember about those important changes in MooseFS repository structure which will be introduced in about 2 weeks.
>
>
> Best regards,
> Peter from MooseFS Team
>
> -- Piotr Robert Konopelko MooseFS Technical Support Engineer | 
> moosefs.com
>> >On 10 Jun 2016, at 7:20 PM, Piotr Robert Konopelko<pio...@mo...>  wrote:
>> >
>> >Dear MooseFS Users,
>> >
>> >we'd like to inform you, that we decided to change our repository structure.
>> >(examples based on Ubuntu 14.04)
>> >
>> >
>> >
>> >debhttp://ppa.moosefs.com/stable/apt/ubuntu/trusty  trusty main
>> >
>> >"stable" in the entry above now points to the latest stable MooseFS from 2.0 branch (at this moment - 2.0.89).
>> >*This behaviour will be kept until end of July 2016*
>> >
>> >*Starting from August 1, 2016, "stable" in the entry above will point to the latest stable MooseFS from 3.0 branch (at this moment - 3.0.77)*
>> >
>> >"stable" symlink is going to be removed at December 31, 2016 - this method will **NOT** work after this date.
>> >
>> >
>> >
>> >Starting from today, it is also possible to use the following entries, so you can switch your repositories consciously either to MooseFS 2 or MooseFS 3 (***we recommend reconfigure your repos before mentioned end of July 2016***):
>> >
>> >debhttp://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty  trusty main
>> >--> this entry points to the newest stable MooseFS 3.0.x version (3.0.77 at the time of writing this e-mail)
>> >
>> >debhttp://ppa.moosefs.com/moosefs-2/apt/ubuntu/trusty  trusty main
>> >--> this entry points to the newest stable MooseFS 2.0.x version (2.0.89 at the time of writing this e-mail)
>> >
>> >
>> >
>> >Of course it is still possible to use "version control" in the repository URL, i.e. version number instead of "stable", "moosefs-3" or "moosefs-2":
>> >
>> >debhttp://ppa.moosefs.com/3.0.77/apt/ubuntu/trusty  trusty main
>> >
>> >--> the entry above will still work and at the moment we don't plan to change it.
>> >
>> >
>> >
>> >This information will be published on our website soon.
>> >
>> >In case of any questions, please don't hesitate to ask!:)
>> >
>> >
>> >Best regards,
>> >Peter from MooseFS Team
>> >
>> >-- 
>> >Piotr Robert Konopelko
>> >MooseFS Technical Support Engineer | moosefs.com
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-Users] labels and sclasses are ignored

[s p. <spa...@gm...>]

Hi,
writing to a file did in fact change the policy immediately and the file
was moved to the fast chunks, however 'touch' did not change the file
policy at all. The archived files stayed archived and new files migrated to
archive after the keep period was over. I probably misunderstood your
documentary where you stated "[...]the system starts to treat a chunk as
archive, when the last modification time (mtime) of the file it belongs to
is older than the number of days specified with -d parameter.". Since
'touch' changes the mtime I thought using it to change the mtime of various
files would be good way to test the setup, however in a real life scenario
a particular file could simply be put into a different sclass.
So the system now works like a charm. Thank you very much for the help!

Best regards,
Steffen



On 27 July 2016 at 18:56, Piotr Robert Konopelko <
pio...@mo...> wrote:

> Hi,
>
> When we consider e.g. writing to file, the create / keep / archive policy
> should be changed immediately. Regarding "touch" command - it is possible,
> that this policy is changed after some time, i.e. when one of internal
> MooseFS' loops is finished.
>
> Did policy of files you had touched 2 days ago was changed properly?
>
>
> PS: Please reply to all (incl. mailing list).
>
> Best regards,
> Peter
>
> --
> [image: MooseFS] <https://moosefs.com>
>
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> e-mail : pio...@mo...
> www : https://moosefs.com
>
> [image: Twitter] <https://twitter.com/MooseFS> [image: Facebook]
> <https://www.facebook.com/moosefs> [image: LinkedIn]
> <https://www.linkedin.com/company/moosefs> [image: GitHub]
> <https://github.com/moosefs>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received it by mistake, please let us know by e-mail reply and
> delete it from your system; you may not copy this message or disclose its
> contents to anyone. Finally, the recipient should check this email and any
> attachments for the presence of viruses. Core Technology accepts no
> liability for any damage caused by any virus transmitted by this email.
>
> On 25 Jul 2016, at 1:41 PM, s pallarz <spa...@gm...> wrote:
>
> Hi,
> thank you so much for the help. The update did help for most cases,
> however, a file which has been moved to "archive" and is then touched is
> not moved back to "keep". Is this the expected behavior?
>
> Best regards,
> Steffen
>
> On 23 July 2016 at 22:48, Piotr Robert Konopelko <
> pio...@mo...> wrote:
>
>> Hi,
>>
>> did upgrading to 3.0.80 helped you to resolve the issue?
>>
>> Best regards,
>> Peter
>>
>> --
>> <Mail Attachment.png> <https://moosefs.com/>
>>
>> Piotr Robert Konopelko
>> MooseFS Technical Support Engineer
>> e-mail : pio...@mo...
>> www : https://moosefs.com
>>
>> <Mail Attachment.png> <https://twitter.com/MooseFS> <Mail Attachment.png>
>> <https://www.facebook.com/moosefs> <Mail Attachment.png>
>> <https://www.linkedin.com/company/moosefs> <Mail Attachment.png>
>> <https://github.com/moosefs>
>>
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they are
>> addressed. If you have received it by mistake, please let us know by e-mail
>> reply and delete it from your system; you may not copy this message or
>> disclose its contents to anyone. Finally, the recipient should check this
>> email and any attachments for the presence of viruses. Core Technology
>> accepts no liability for any damage caused by any virus transmitted by this
>> email.
>>
>> On 21 Jul 2016, at 12:37 AM, Piotr Robert Konopelko <
>> pio...@mo...> wrote:
>>
>> Hi,
>>
>> please check MooseFS v. 3.0.80 and let us know, did upgrading to 3.0.80
>> helped. We released this version last week. It fixes some labels-related
>> issues.
>>
>> You can find recent changes in MooseFS on the following website:
>> https://moosefs.com/documentation/changes-in-moosefs-3-0.html
>>
>>
>> Best regards,
>> Peter
>>
>> --
>> <Mail Attachment.png> <https://moosefs.com/>
>>
>> Piotr Robert Konopelko
>> MooseFS Technical Support Engineer
>> e-mail : pio...@mo...
>> www : https://moosefs.com
>>
>> <Mail Attachment.png> <https://twitter.com/MooseFS> <Mail Attachment.png>
>> <https://www.facebook.com/moosefs> <Mail Attachment.png>
>> <https://www.linkedin.com/company/moosefs> <Mail Attachment.png>
>> <https://github.com/moosefs>
>>
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they are
>> addressed. If you have received it by mistake, please let us know by e-mail
>> reply and delete it from your system; you may not copy this message or
>> disclose its contents to anyone. Finally, the recipient should check this
>> email and any attachments for the presence of viruses. Core Technology
>> accepts no liability for any damage caused by any virus transmitted by this
>> email.
>>
>> On 20 Jul 2016, at 5:14 PM, s pallarz <spa...@gm...> wrote:
>>
>> Hi,
>> I just started using moosefs v. 3.0.79. My setup is 5 computers (1
>> master, 2 fast chunkserver (Label: F) and 2 slow chunkserver (Label: S)). I
>> created a storage class which was supposed to create chunks on the fast
>> chunks (-C 2F), keep the chunks on those fast servers (-K 2F) and finally
>> archive them after 2 days to the slow servers (-A 2S -d 2).
>> Sadly non of it works. The chunks are created arbitrarily on any of the 4
>> servers, archiving does not happen at all.
>> I tried changing the mode from default to strict (-m S), but this did not
>> help either.
>>
>> >mfsscadmin list -l
>> main2 : 2 ; admin_only: NO ; create_mode: STRICT ; create_labels: [F] ,
>> [F] ; keep_labels: [F] , [F] ; arch_labels: [S] , [S] ; arch_delay: 2d
>>
>> all drives have over 95% free space.
>>
>> What am I doing wrong?
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.
>> http://sdm.link/zohodev2dev_________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.
>> http://sdm.link/zohodev2dev_________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>>
>>
>
>

Re: [MooseFS-Users] labels and sclasses are ignored

[Piotr R. K. <pio...@mo...>]

Hi,

When we consider e.g. writing to file, the create / keep / archive policy should be changed immediately. Regarding "touch" command - it is possible, that this policy is changed after some time, i.e. when one of internal MooseFS' loops is finished.

Did policy of files you had touched 2 days ago was changed properly?


PS: Please reply to all (incl. mailing list).
Best regards, 
Peter

--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 25 Jul 2016, at 1:41 PM, s pallarz <spa...@gm...> wrote:
> 
> Hi,
> thank you so much for the help. The update did help for most cases, however, a file which has been moved to "archive" and is then touched is not moved back to "keep". Is this the expected behavior?
> 
> Best regards,
> Steffen
> 
> On 23 July 2016 at 22:48, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote:
> Hi,
> 
> did upgrading to 3.0.80 helped you to resolve the issue?
> Best regards, 
> Peter
> 
> --
> 
> <Mail Attachment.png> <https://moosefs.com/>
> 
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> e-mail : pio...@mo... <mailto:pio...@mo...>
> www : https://moosefs.com <https://moosefs.com/>
> 
> <Mail Attachment.png>  <https://twitter.com/MooseFS><Mail Attachment.png>  <https://www.facebook.com/moosefs><Mail Attachment.png>  <https://www.linkedin.com/company/moosefs><Mail Attachment.png> <https://github.com/moosefs>
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.
> 
> 
>> On 21 Jul 2016, at 12:37 AM, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote:
>> 
>> Hi,
>> 
>> please check MooseFS v. 3.0.80 and let us know, did upgrading to 3.0.80 helped. We released this version last week. It fixes some labels-related issues.
>> 
>> You can find recent changes in MooseFS on the following website:
>> https://moosefs.com/documentation/changes-in-moosefs-3-0.html <https://moosefs.com/documentation/changes-in-moosefs-3-0.html>
>> 
>> Best regards, 
>> Peter
>> 
>> --
>> 
>> <Mail Attachment.png> <https://moosefs.com/>
>> 
>> Piotr Robert Konopelko
>> MooseFS Technical Support Engineer
>> e-mail : pio...@mo... <mailto:pio...@mo...>
>> www : https://moosefs.com <https://moosefs.com/>
>> 
>> <Mail Attachment.png>  <https://twitter.com/MooseFS><Mail Attachment.png>  <https://www.facebook.com/moosefs><Mail Attachment.png>  <https://www.linkedin.com/company/moosefs><Mail Attachment.png> <https://github.com/moosefs>
>> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.
>> 
>> 
>>> On 20 Jul 2016, at 5:14 PM, s pallarz <spa...@gm... <mailto:spa...@gm...>> wrote:
>>> 
>>> Hi,
>>> I just started using moosefs v. 3.0.79. My setup is 5 computers (1 master, 2 fast chunkserver (Label: F) and 2 slow chunkserver (Label: S)). I created a storage class which was supposed to create chunks on the fast chunks (-C 2F), keep the chunks on those fast servers (-K 2F) and finally archive them after 2 days to the slow servers (-A 2S -d 2).
>>> Sadly non of it works. The chunks are created arbitrarily on any of the 4 servers, archiving does not happen at all.
>>> I tried changing the mode from default to strict (-m S), but this did not help either.
>>> 
>>> >mfsscadmin list -l
>>> main2 : 2 ; admin_only: NO ; create_mode: STRICT ; create_labels: [F] , [F] ; keep_labels: [F] , [F] ; arch_labels: [S] , [S] ; arch_delay: 2d
>>> 
>>> all drives have over 95% free space.
>>> 
>>> What am I doing wrong?
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols are 
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
>>> reports.http://sdm.link/zohodev2dev_________________________________________ <http://sdm.link/zohodev2dev_________________________________________>
>>> moosefs-users mailing list
>>> moo...@li... <mailto:moo...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users <https://lists.sourceforge.net/lists/listinfo/moosefs-users>
>> 
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are 
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
>> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
>> reports.http://sdm.link/zohodev2dev_________________________________________ <http://sdm.link/zohodev2dev_________________________________________>
>> moosefs-users mailing list
>> moo...@li... <mailto:moo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users <https://lists.sourceforge.net/lists/listinfo/moosefs-users>
> 
> 

Re: [MooseFS-Users] Xor replication

[Daniel F. B. <df...@it...>]

That's great news, space efficiency with no penalties.
We are starting with 4 servers, but the initial plan is to rapidly grow 
to 12 with a 3 goal, so perfect.
Keep us informed when there are something to test.

Thank again

Daniel


On 07/27/2016 09:50 AM, Jakub Kruszona-Zawadzki wrote:
> On 26 Jul, 2016, at 15:44, Daniel Feliciano Branco <df...@it...> wrote:
>
>> Hi all,
>>
>>   We are testing moosefs for our backup/storage service (brilliant so
>> far, thank you for sharing your hard work).
>>
>>   On version 3.0.1-1 (2015-01-28) it was added xor-replication but I'm
>> unable to find any information on the subject. Other then the hard code
>> on github.
> This was added just "for future use". Now we are working hard to bring "raid" feature in upcoming MooseFS 4.x.
>
>>   Is it possible to test this functionality? As I understand it, you can
>> have a raid5 (or 6) space efficiency and performance penalty, right?
>>
>>    Can any one shed some light on this issue?
>>
>>   Thank you
>>
>> Daniel Branco
> I hope that there will be no performance penalties in case of using "raid". Our approach is that files will be written using classic goal (few copies) and then after a few days automatically changed to "raid"-like method. This means that all temporary files will be stored in copies (such files occupy relatively small amount of space), but all the rest will be stored in more space-efficient "raid"-like method (and those files usually occupy large amount of space). In such approach I hope that we will have no performance penalties and will be able to save a lot of space.
>
> Our "raid" system is designed to have up to 9 checksum per 8 blocks. 8 blocks and 1 checksum will give safety similar to goal 2, 8 + 2 will give safety of goal 3 and so on. Probably the recommended method will be 8+2 (files occupy 10/8 = 125% of their space with safety of goal 3). Of course you will need at least 12 chunkservers to achieve that. Our "raid" is designed for rather "large" moosefs installations, because mainly in large (hundreds of TB) installations you need to save space. In small installations it doesn't really matter.
>
>> -- 
>> Serviço de Informática - http://si.itqb.unl.pt
>> Instituto de Tecnologia Quimica e Biológica
>> Universidade Nova de Lisboa - http://www.itqb.unl.pt
>> Avenida da República
>> Apartado 127
>> 2781-901 Oeiras
>> Portugal
>> Tel. (+351) 21 446 9470
>>
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
>> reports.http://sdm.link/zohodev2dev
>> _________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users


-- 
Serviço de Informática - http://si.itqb.unl.pt
Instituto de Tecnologia Quimica e Biológica
Universidade Nova de Lisboa - http://www.itqb.unl.pt
Avenida da República
Apartado 127
2781-901 Oeiras
Portugal
Tel. (+351) 21 446 9470

Re: [MooseFS-Users] Xor replication

[Jakub Kruszona-Z. <jak...@ge...>]

On 26 Jul, 2016, at 15:44, Daniel Feliciano Branco <df...@it...> wrote:

> Hi all,
> 
>  We are testing moosefs for our backup/storage service (brilliant so 
> far, thank you for sharing your hard work).
> 
>  On version 3.0.1-1 (2015-01-28) it was added xor-replication but I'm 
> unable to find any information on the subject. Other then the hard code 
> on github.

This was added just "for future use". Now we are working hard to bring "raid" feature in upcoming MooseFS 4.x. 

> 
>  Is it possible to test this functionality? As I understand it, you can 
> have a raid5 (or 6) space efficiency and performance penalty, right?
> 
>   Can any one shed some light on this issue?
> 
>  Thank you
> 
> Daniel Branco

I hope that there will be no performance penalties in case of using "raid". Our approach is that files will be written using classic goal (few copies) and then after a few days automatically changed to "raid"-like method. This means that all temporary files will be stored in copies (such files occupy relatively small amount of space), but all the rest will be stored in more space-efficient "raid"-like method (and those files usually occupy large amount of space). In such approach I hope that we will have no performance penalties and will be able to save a lot of space.

Our "raid" system is designed to have up to 9 checksum per 8 blocks. 8 blocks and 1 checksum will give safety similar to goal 2, 8 + 2 will give safety of goal 3 and so on. Probably the recommended method will be 8+2 (files occupy 10/8 = 125% of their space with safety of goal 3). Of course you will need at least 12 chunkservers to achieve that. Our "raid" is designed for rather "large" moosefs installations, because mainly in large (hundreds of TB) installations you need to save space. In small installations it doesn't really matter.

> 
> -- 
> Serviço de Informática - http://si.itqb.unl.pt
> Instituto de Tecnologia Quimica e Biológica
> Universidade Nova de Lisboa - http://www.itqb.unl.pt
> Avenida da República
> Apartado 127
> 2781-901 Oeiras
> Portugal
> Tel. (+351) 21 446 9470
> 
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

-- 
Regards,
Jakub Kruszona-Zawadzki
- - - - - - - - - - - - - - - -
Segmentation fault (core dumped)
Phone: +48 602 212 039

[MooseFS-Users] Xor replication

[Daniel F. B. <df...@it...>]

Hi all,

  We are testing moosefs for our backup/storage service (brilliant so 
far, thank you for sharing your hard work).

  On version 3.0.1-1 (2015-01-28) it was added xor-replication but I'm 
unable to find any information on the subject. Other then the hard code 
on github.

  Is it possible to test this functionality? As I understand it, you can 
have a raid5 (or 6) space efficiency and performance penalty, right?

   Can any one shed some light on this issue?

  Thank you

Daniel Branco

-- 
Serviço de Informática - http://si.itqb.unl.pt
Instituto de Tecnologia Quimica e Biológica
Universidade Nova de Lisboa - http://www.itqb.unl.pt
Avenida da República
Apartado 127
2781-901 Oeiras
Portugal
Tel. (+351) 21 446 9470

Re: [MooseFS-Users] oddness with chunkserver 3.0.80 on BSD

[Piotr R. K. <pio...@mo...>]

Hi,

could you please write an update in issue #15 on MooseFS GitHub? https://github.com/moosefs/moosefs/issues/15 <https://github.com/moosefs/moosefs/issues/15>
I pasted an URL there, but your last message sent to the list seems to be empty on MooseFS-Users Mailing List archive.

Thanks,
Peter
--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 22 Jul 2016, at 4:40 PM, Ben Harker <bj...@ba...> wrote:
> 
> hello all - just reporting back - reinstalled with FreeBSD [original install was TrueOS/PC-BSD which i genuinely thought wouldn't give me any issues!] 10.3 and everything is working brilliantly now!
> 
> thanks for trying to help me figure it out though!
> 
> 
> Ben Harker
> 
> Apple / Linux Specialist
> Barton Peveril College
> Mob: 07525175882
> Tel: 02380367224
> Ext: 2731
> 
> GitHub: https://github.com/tehbenneh/
>  <https://github.com/tehbenneh/>
> DockerHub: https://hub.docker.com/r/tehbenneh/ <https://hub.docker.com/r/tehbenneh/>
> 
> >>> Aleksander Wieliczko <ale...@mo...> 7/22/2016 10:23 AM >>>
> Hi,
> 
> This is really strange.
> 
> Try to do this steps:
> mv /etc/pkg/moosefs.conf /tmp
> pkg clean -a
> mv /tmp/moosefs.conf /etc/pkg/MooseFS.conf
> pkg update
> pkg search moosefs
> 
> By the way. Are you able to ping ppa.moosefs.com from your FreeBSD machine?
> 
> Best regards
> Aleksander Wieliczko
> Technical Support Engineer
> MooseFS.com <x-msg://22/moosefs.com>------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-Users] IMPORTANT Changes in MooseFS Repository structure

[Piotr R. K. <pio...@mo...>]

Dear MooseFS Users,

please remember about those important changes in MooseFS repository structure which will be introduced in about a week.


Best regards,
Peter

-- 
Piotr Robert Konopelko
MooseFS Technical Support Engineer | moosefs.com

> On 16 Jul 2016, at 3:51 AM, Piotr Robert Konopelko <pio...@mo...> wrote:
> 
> Dear MooseFS Users,
> 
> please remember about those important changes in MooseFS repository structure which will be introduced in about 2 weeks.
> 
> 
> Best regards,
> Peter from MooseFS Team
> 
> -- 
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer | moosefs.com
> 
>> On 10 Jun 2016, at 7:20 PM, Piotr Robert Konopelko <pio...@mo...> wrote:
>> 
>> Dear MooseFS Users,
>> 
>> we'd like to inform you, that we decided to change our repository structure.
>> (examples based on Ubuntu 14.04)
>> 
>> 
>> 
>> deb http://ppa.moosefs.com/stable/apt/ubuntu/trusty trusty main
>> 
>> "stable" in the entry above now points to the latest stable MooseFS from 2.0 branch (at this moment - 2.0.89).
>> *This behaviour will be kept until end of July 2016*
>> 
>> *Starting from August 1, 2016, "stable" in the entry above will point to the latest stable MooseFS from 3.0 branch (at this moment - 3.0.77)*
>> 
>> "stable" symlink is going to be removed at December 31, 2016 - this method will **NOT** work after this date.
>> 
>> 
>> 
>> Starting from today, it is also possible to use the following entries, so you can switch your repositories consciously either to MooseFS 2 or MooseFS 3 (***we recommend reconfigure your repos before mentioned end of July 2016***):
>> 
>> deb http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty trusty main
>> --> this entry points to the newest stable MooseFS 3.0.x version (3.0.77 at the time of writing this e-mail)
>> 
>> deb http://ppa.moosefs.com/moosefs-2/apt/ubuntu/trusty trusty main
>> --> this entry points to the newest stable MooseFS 2.0.x version (2.0.89 at the time of writing this e-mail)
>> 
>> 
>> 
>> Of course it is still possible to use "version control" in the repository URL, i.e. version number instead of "stable", "moosefs-3" or "moosefs-2":
>> 
>> deb http://ppa.moosefs.com/3.0.77/apt/ubuntu/trusty trusty main
>> 
>> --> the entry above will still work and at the moment we don't plan to change it.
>> 
>> 
>> 
>> This information will be published on our website soon.
>> 
>> In case of any questions, please don't hesitate to ask! :)
>> 
>> 
>> Best regards,
>> Peter from MooseFS Team
>> 
>> -- 
>> Piotr Robert Konopelko
>> MooseFS Technical Support Engineer | moosefs.com
> 
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-Users] labels and sclasses are ignored

[Piotr R. K. <pio...@mo...>]

Hi,

did upgrading to 3.0.80 helped you to resolve the issue?
Best regards, 
Peter

--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 21 Jul 2016, at 12:37 AM, Piotr Robert Konopelko <pio...@mo...> wrote:
> 
> Hi,
> 
> please check MooseFS v. 3.0.80 and let us know, did upgrading to 3.0.80 helped. We released this version last week. It fixes some labels-related issues.
> 
> You can find recent changes in MooseFS on the following website:
> https://moosefs.com/documentation/changes-in-moosefs-3-0.html <https://moosefs.com/documentation/changes-in-moosefs-3-0.html>
> 
> Best regards, 
> Peter
> 
> --
> 
> <Mail Attachment.png> <https://moosefs.com/>
> 
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> e-mail : pio...@mo... <mailto:pio...@mo...>
> www : https://moosefs.com <https://moosefs.com/>
> 
> <Mail Attachment.png>  <https://twitter.com/MooseFS><Mail Attachment.png>  <https://www.facebook.com/moosefs><Mail Attachment.png>  <https://www.linkedin.com/company/moosefs><Mail Attachment.png> <https://github.com/moosefs>
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.
> 
> 
>> On 20 Jul 2016, at 5:14 PM, s pallarz <spa...@gm... <mailto:spa...@gm...>> wrote:
>> 
>> Hi,
>> I just started using moosefs v. 3.0.79. My setup is 5 computers (1 master, 2 fast chunkserver (Label: F) and 2 slow chunkserver (Label: S)). I created a storage class which was supposed to create chunks on the fast chunks (-C 2F), keep the chunks on those fast servers (-K 2F) and finally archive them after 2 days to the slow servers (-A 2S -d 2).
>> Sadly non of it works. The chunks are created arbitrarily on any of the 4 servers, archiving does not happen at all.
>> I tried changing the mode from default to strict (-m S), but this did not help either.
>> 
>> >mfsscadmin list -l
>> main2 : 2 ; admin_only: NO ; create_mode: STRICT ; create_labels: [F] , [F] ; keep_labels: [F] , [F] ; arch_labels: [S] , [S] ; arch_delay: 2d
>> 
>> all drives have over 95% free space.
>> 
>> What am I doing wrong?
>> 
>> 
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are 
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
>> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
>> reports.http://sdm.link/zohodev2dev_________________________________________ <http://sdm.link/zohodev2dev_________________________________________>
>> moosefs-users mailing list
>> moo...@li... <mailto:moo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-Users] oddness with chunkserver 3.0.80 on BSD

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

Hi,

This is really strange.

Try to do this steps:
mv /etc/pkg/moosefs.conf /tmp
pkg clean -a
mv /tmp/moosefs.conf /etc/pkg/MooseFS.conf
pkg update
pkg search moosefs

By the way. Are you able to ping ppa.moosefs.com from your FreeBSD machine?

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

Re: [MooseFS-Users] oddness with chunkserver 3.0.80 on BSD

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

Hi,

Please check your /etc/pkg/moosefs.conf file permissions.
It should be the same as FreeBSD.conf

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

On 07/22/2016 10:58 AM, Ben Harker wrote:
>
> Hi Aleksander - just tried this on a second box that's on my desk,
> thought i'd try from scratch;
>
>
> [administrator@mfsbsd2] /usr/home/administrator# cat
> /etc/pkg/moosefs.conf ; pkg update ; pkg search moosefs
>
> moosefs: {
>
> url: "/_http://ppa.moosefs.com/moosefs-3/freebsd/10:x86:64_/",
>
> enabled: yes,
>
> mirror_type: NONE
>
> }
>
> Updating pcbsd-major repository catalogue...
>
> pcbsd-major repository is up-to-date.
>
> All repositories are up-to-date.
>
> moosefs-cgi-2.0.89             MooseFS CGI interface
>
> moosefs-cgiserv-2.0.89         MooseFS CGI webserver
>
> moosefs-chunkserver-2.0.89     MooseFS data storage and
> synchronization component
>
> moosefs-cli-2.0.89             MooseFS command line interface
>
> moosefs-client-2.0.89          MooseFS client tools
>
> moosefs-master-2.0.89          Fault-tolerant distributed filesystem
>
> moosefs-metalogger-2.0.89      MooseFS metadata backup server
>
> moosefs-netdump-2.0.89         MooseFS network packet dump utility
>
>
> ^^^ same result as you can see :(
>
>
> Ben Harker
>
> Apple / Linux Specialist
> Barton Peveril College
> Mob: 07525175882
> Tel: 02380367224
> Ext: 2731
>
> GitHub: https://github.com/tehbenneh/ <https://github.com/tehbenneh/%0D>
> DockerHub: https://hub.docker.com/r/tehbenneh/
>
> >>> Aleksander Wieliczko <ale...@mo...> 7/22/2016
> 7:20 AM >>>
> Hi Ben,
> Would you be so kind and execute this commands:
> pkg update
> pkg search moosefs
>
> Do you see MooseFS 3.0.80 on this list?
>
>
> This is how MooseFS.conf file should look like for FreeBSD 10
>
> moosefs: {
>   url: "http://ppa.moosefs.com/moosefs-3/freebsd/10:x86:64",
>   enabled: yes,
>   mirror_type: NONE
> }
>
>
> Best regards
> Aleksander Wieliczko
> Technical Support Engineer
> MooseFS.com <moosefs.com>
>

Re: [MooseFS-Users] oddness with chunkserver 3.0.80 on BSD

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

Hi Ben,
Would you be so kind and execute this commands:
pkg update
pkg search moosefs

Do you see MooseFS 3.0.80 on this list?


This is how MooseFS.conf file should look like for FreeBSD 10

moosefs: {
  url: "http://ppa.moosefs.com/moosefs-3/freebsd/10:x86:64",
  enabled: yes,
  mirror_type: NONE
}


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

Re: [MooseFS-Users] oddness with chunkserver 3.0.80 on BSD

[<li...@ol...>]

Hi,

This probably happens because the official PC-BSD or FreeBSD repository has a higher priority than the MooseFS repo. As far as I know, pkg reads repo files in lexical order, and first match wins. Did you try to rename the repo files so that the MooseFS repo appears first? Like:

10-moosefs.conf
20-freebsd.conf

Hope it helps,

Marin.

De : Ben Harker

Re: [MooseFS-Users] labels and sclasses are ignored

[Piotr R. K. <pio...@mo...>]

Hi,

please check MooseFS v. 3.0.80 and let us know, did upgrading to 3.0.80 helped. We released this version last week. It fixes some labels-related issues.

You can find recent changes in MooseFS on the following website:
https://moosefs.com/documentation/changes-in-moosefs-3-0.html <https://moosefs.com/documentation/changes-in-moosefs-3-0.html>

Best regards, 
Peter

--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 20 Jul 2016, at 5:14 PM, s pallarz <spa...@gm...> wrote:
> 
> Hi,
> I just started using moosefs v. 3.0.79. My setup is 5 computers (1 master, 2 fast chunkserver (Label: F) and 2 slow chunkserver (Label: S)). I created a storage class which was supposed to create chunks on the fast chunks (-C 2F), keep the chunks on those fast servers (-K 2F) and finally archive them after 2 days to the slow servers (-A 2S -d 2).
> Sadly non of it works. The chunks are created arbitrarily on any of the 4 servers, archiving does not happen at all.
> I tried changing the mode from default to strict (-m S), but this did not help either.
> 
> >mfsscadmin list -l
> main2 : 2 ; admin_only: NO ; create_mode: STRICT ; create_labels: [F] , [F] ; keep_labels: [F] , [F] ; arch_labels: [S] , [S] ; arch_delay: 2d
> 
> all drives have over 95% free space.
> 
> What am I doing wrong?
> 
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

[MooseFS-Users] labels and sclasses are ignored

[s p. <spa...@gm...>]

Hi,
I just started using moosefs v. 3.0.79. My setup is 5 computers (1 master,
2 fast chunkserver (Label: F) and 2 slow chunkserver (Label: S)). I created
a storage class which was supposed to create chunks on the fast chunks (-C
2F), keep the chunks on those fast servers (-K 2F) and finally archive them
after 2 days to the slow servers (-A 2S -d 2).
Sadly non of it works. The chunks are created arbitrarily on any of the 4
servers, archiving does not happen at all.
I tried changing the mode from default to strict (-m S), but this did not
help either.

>mfsscadmin list -l
main2 : 2 ; admin_only: NO ; create_mode: STRICT ; create_labels: [F] , [F]
; keep_labels: [F] , [F] ; arch_labels: [S] , [S] ; arch_delay: 2d

all drives have over 95% free space.

What am I doing wrong?

Re: [MooseFS-Users] IMPORTANT Changes in MooseFS Repository structure

[Piotr R. K. <pio...@mo...>]

Dear MooseFS Users,

please remember about those important changes in MooseFS repository structure which will be introduced in about 2 weeks.


Best regards,
Peter from MooseFS Team

-- 
Piotr Robert Konopelko
MooseFS Technical Support Engineer | moosefs.com

> On 10 Jun 2016, at 7:20 PM, Piotr Robert Konopelko <pio...@mo...> wrote:
> 
> Dear MooseFS Users,
> 
> we'd like to inform you, that we decided to change our repository structure.
> (examples based on Ubuntu 14.04)
> 
> 
> 
> deb http://ppa.moosefs.com/stable/apt/ubuntu/trusty trusty main
> 
> "stable" in the entry above now points to the latest stable MooseFS from 2.0 branch (at this moment - 2.0.89).
> *This behaviour will be kept until end of July 2016*
> 
> *Starting from August 1, 2016, "stable" in the entry above will point to the latest stable MooseFS from 3.0 branch (at this moment - 3.0.77)*
> 
> "stable" symlink is going to be removed at December 31, 2016 - this method will **NOT** work after this date.
> 
> 
> 
> Starting from today, it is also possible to use the following entries, so you can switch your repositories consciously either to MooseFS 2 or MooseFS 3 (***we recommend reconfigure your repos before mentioned end of July 2016***):
> 
> deb http://ppa.moosefs.com/moosefs-3/apt/ubuntu/trusty trusty main
> --> this entry points to the newest stable MooseFS 3.0.x version (3.0.77 at the time of writing this e-mail)
> 
> deb http://ppa.moosefs.com/moosefs-2/apt/ubuntu/trusty trusty main
> --> this entry points to the newest stable MooseFS 2.0.x version (2.0.89 at the time of writing this e-mail)
> 
> 
> 
> Of course it is still possible to use "version control" in the repository URL, i.e. version number instead of "stable", "moosefs-3" or "moosefs-2":
> 
> deb http://ppa.moosefs.com/3.0.77/apt/ubuntu/trusty trusty main
> 
> --> the entry above will still work and at the moment we don't plan to change it.
> 
> 
> 
> This information will be published on our website soon.
> 
> In case of any questions, please don't hesitate to ask! :)
> 
> 
> Best regards,
> Peter from MooseFS Team
> 
> -- 
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer | moosefs.com

Re: [MooseFS-Users] mfs breakdown, and failed to restore the error metedata.Is there any other way to repair?

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

Hi,
Can you tell us little more about this issue.
Do you have MooseFS metalloger in you cluster?

By the way, MooseFS does not store files with "ls" extension.
You should see files like *.mfs or *.mfs.back

First of all please try to backup all metadata files(default path in
linux OS is /var/lib/mfs) and start mfsmaster with auto restore option:

mfsmaster -a

I'm looking forward to hearing from you.
Best regards,
Aleksander Wieliczko
Technical Support Engineer
MooseFS.com <moosefs.com>

On 07/14/2016 01:26 AM, wshzhn wrote:
> mfs breakdown,and failed to restore the error metedata.Is there any
> other way to repair?
> Thanks.
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
>
>
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

[MooseFS-Users] mfs breakdown, and failed to restore the error metedata.Is there any other way to repair?

[wshzhn <ws...@gm...>]

mfs breakdown,and failed to restore the error metedata.Is there any other
way to repair?
Thanks.

Re: [MooseFS-Users] IMPORTANT change in FreeBSD MooseFS ports structure

[Piotr R. K. <pio...@mo...>]

Hi all,
small errata - of course while typing

>  Feld form FreeBSD

I meant Feld (Mark Felder) from FreeBSD - he's assigned to the ticket on FreeBSD Bugzilla.
I'm sorry for the mistake.

Best regards, 
Peter

--
  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 08 Jul 2016, at 4:08 PM, Piotr Robert Konopelko <pio...@mo...> wrote:
> 
> Hi all MooseFS Users,
> 
> We'd like to let you know, that yesterday, together with Feld form FreeBSD, we changed MooseFS ports structure on FreeBSD.
> 
> moosefs-* ports has been moved to moosefs2-* ports to make space for MooseFS 3.0 ports (moosefs3-*) and any future major releases.
> 
> Please find below Bugzilla bug and SVN commit which reference this change:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210306 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210306>
> https://svnweb.freebsd.org/ports?view=revision&revision=418199 <https://svnweb.freebsd.org/ports?view=revision&revision=418199>
> 
> I also updated our GitHub MooseFS ports repository to be consistent with those changes:
> https://github.com/moosefs/FreeBSD-ports/commit/0bc47868ed1b511bc79c51d2edd7081c41459565 <https://github.com/moosefs/FreeBSD-ports/commit/0bc47868ed1b511bc79c51d2edd7081c41459565>
> https://github.com/moosefs/FreeBSD-ports/commit/e937e55e9da64cfdc5c01b060f539a7e13c73faa <https://github.com/moosefs/FreeBSD-ports/commit/e937e55e9da64cfdc5c01b060f539a7e13c73faa>
> 
> 
> At this moment MooseFS 3.0 ports match new ports structure and are ready to be released:
> https://github.com/moosefs/FreeBSD-ports/commits/master <https://github.com/moosefs/FreeBSD-ports/commits/master>
> 
> Any extra check on these ports would be appreciated, so if you have some free time, feel free to test them and send us some feedback!
> 
> Best regards, 
> Peter
> 
> --
> 
> <Mail Attachment.png> <https://moosefs.com/>
> 
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> e-mail : pio...@mo... <mailto:pio...@mo...>
> www : https://moosefs.com <https://moosefs.com/>
> 
> <Mail Attachment.png>  <https://twitter.com/MooseFS><Mail Attachment.png>  <https://www.facebook.com/moosefs><Mail Attachment.png>  <https://www.linkedin.com/company/moosefs><Mail Attachment.png> <https://github.com/moosefs>
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.
> 
> 
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

[MooseFS-Users] IMPORTANT change in FreeBSD MooseFS ports structure

[Piotr R. K. <pio...@mo...>]

Hi all MooseFS Users,

We'd like to let you know, that yesterday, together with Feld form FreeBSD, we changed MooseFS ports structure on FreeBSD.

moosefs-* ports has been moved to moosefs2-* ports to make space for MooseFS 3.0 ports (moosefs3-*) and any future major releases.

Please find below Bugzilla bug and SVN commit which reference this change:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210306 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210306>
https://svnweb.freebsd.org/ports?view=revision&revision=418199 <https://svnweb.freebsd.org/ports?view=revision&revision=418199>

I also updated our GitHub MooseFS ports repository to be consistent with those changes:
https://github.com/moosefs/FreeBSD-ports/commit/0bc47868ed1b511bc79c51d2edd7081c41459565 <https://github.com/moosefs/FreeBSD-ports/commit/0bc47868ed1b511bc79c51d2edd7081c41459565>
https://github.com/moosefs/FreeBSD-ports/commit/e937e55e9da64cfdc5c01b060f539a7e13c73faa <https://github.com/moosefs/FreeBSD-ports/commit/e937e55e9da64cfdc5c01b060f539a7e13c73faa>


At this moment MooseFS 3.0 ports match new ports structure and are ready to be released:
https://github.com/moosefs/FreeBSD-ports/commits/master <https://github.com/moosefs/FreeBSD-ports/commits/master>

Any extra check on these ports would be appreciated, so if you have some free time, feel free to test them and send us some feedback!

Best regards, 
Peter

--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.

Re: [MooseFS-Users] Oldest binary request

[Alex M. <al...@is...>]

Thanks a lot!


Regards,
Alex.

On Mon, Jul 4, 2016 at 12:41 PM, Piotr Robert Konopelko <
pio...@mo...> wrote:

> Hi Alex,
>
> just use the following entry in /etc/apt/sources.list.d/moosefs.list:
>
> deb http://ppa.moosefs.com/2.0.81/apt/ubuntu/precise precise main
>
>
> Best regards,
> Peter
>
> --
> [image: MooseFS] <https://moosefs.com>
>
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> e-mail : pio...@mo...
> www : https://moosefs.com
>
> [image: Twitter] <https://twitter.com/MooseFS> [image: Facebook]
> <https://www.facebook.com/moosefs> [image: LinkedIn]
> <https://www.linkedin.com/company/moosefs> [image: GitHub]
> <https://github.com/moosefs>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received it by mistake, please let us know by e-mail reply and
> delete it from your system; you may not copy this message or disclose its
> contents to anyone. Finally, the recipient should check this email and any
> attachments for the presence of viruses. Core Technology accepts no
> liability for any damage caused by any virus transmitted by this email.
>
> On 04 Jul 2016, at 9:03 AM, Alex Milzon <al...@is...> wrote:
>
> Hello,
> I'm looking to download moosefs-client version 2.0.81-1 for Ubuntu 12.04
> Precise, amd64.
> Can you please help me with it?
>
> Thanks in advance,
> Alex.
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
>
>

Re: [MooseFS-Users] Oldest binary request

[Piotr R. K. <pio...@mo...>]

Hi Alex,

just use the following entry in /etc/apt/sources.list.d/moosefs.list:

deb http://ppa.moosefs.com/2.0.81/apt/ubuntu/precise precise main


Best regards,
Peter
--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 04 Jul 2016, at 9:03 AM, Alex Milzon <al...@is...> wrote:
> 
> Hello,
> I'm looking to download moosefs-client version 2.0.81-1 for Ubuntu 12.04 Precise, amd64.
> Can you please help me with it?
> 
> Thanks in advance,
> Alex.
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

[MooseFS-Users] Oldest binary request

[Alex M. <al...@is...>]

Hello,
I'm looking to download moosefs-client version 2.0.81-1 for Ubuntu 12.04
Precise, amd64.
Can you please help me with it?

Thanks in advance,
Alex.