Menu
▾
▴
moosefs-users — Mailing list for MooseFS Users
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(20) |
Feb
(11) |
Mar
(11) |
Apr
(9) |
May
(22) |
Jun
(85) |
Jul
(94) |
Aug
(80) |
Sep
(72) |
Oct
(64) |
Nov
(69) |
Dec
(89) |
| 2011 |
Jan
(72) |
Feb
(109) |
Mar
(116) |
Apr
(117) |
May
(117) |
Jun
(102) |
Jul
(91) |
Aug
(72) |
Sep
(51) |
Oct
(41) |
Nov
(55) |
Dec
(74) |
| 2012 |
Jan
(45) |
Feb
(77) |
Mar
(99) |
Apr
(113) |
May
(132) |
Jun
(75) |
Jul
(70) |
Aug
(58) |
Sep
(58) |
Oct
(37) |
Nov
(51) |
Dec
(15) |
| 2013 |
Jan
(28) |
Feb
(16) |
Mar
(25) |
Apr
(38) |
May
(23) |
Jun
(39) |
Jul
(42) |
Aug
(19) |
Sep
(41) |
Oct
(31) |
Nov
(18) |
Dec
(18) |
| 2014 |
Jan
(17) |
Feb
(19) |
Mar
(39) |
Apr
(16) |
May
(10) |
Jun
(13) |
Jul
(17) |
Aug
(13) |
Sep
(8) |
Oct
(53) |
Nov
(23) |
Dec
(7) |
| 2015 |
Jan
(35) |
Feb
(13) |
Mar
(14) |
Apr
(56) |
May
(8) |
Jun
(18) |
Jul
(26) |
Aug
(33) |
Sep
(40) |
Oct
(37) |
Nov
(24) |
Dec
(20) |
| 2016 |
Jan
(38) |
Feb
(20) |
Mar
(25) |
Apr
(14) |
May
(6) |
Jun
(36) |
Jul
(27) |
Aug
(19) |
Sep
(36) |
Oct
(24) |
Nov
(15) |
Dec
(16) |
| 2017 |
Jan
(8) |
Feb
(13) |
Mar
(17) |
Apr
(20) |
May
(28) |
Jun
(10) |
Jul
(20) |
Aug
(3) |
Sep
(18) |
Oct
(8) |
Nov
|
Dec
(5) |
| 2018 |
Jan
(15) |
Feb
(9) |
Mar
(12) |
Apr
(7) |
May
(123) |
Jun
(41) |
Jul
|
Aug
(14) |
Sep
|
Oct
(15) |
Nov
|
Dec
(7) |
| 2019 |
Jan
(2) |
Feb
(9) |
Mar
(2) |
Apr
(9) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(6) |
Oct
(1) |
Nov
(12) |
Dec
(2) |
| 2020 |
Jan
(2) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(18) |
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(3) |
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Casper L. <cas...@pr...> - 2016-06-25 14:35:55
|
Hi All,
I have created a script to monitor my MooseFS masters with Nagios, and I
find that quite some times the follower master is in desync state.
On a check interval of 5 minutes, a desync state happens about a dozen
times a day. The amount of time time happens seems to be correlating with
the (write?) load the file system is taking. I'm guessing this is expected
behaviour?
I'm reading the MATOCL_INFO (PROTO_BASE+511) data, the same mfs.cgi does in
line 1836:
*workingstate,nextstate,stablestate,sync,leaderip,changetime,metaversion
= struct.unpack(">BBBBLLQ",data[101:121])*
*sync* seems to be 1 most of the time, but sometimes 0. *metaversion* is
updated continuously, but *changetime* is always the same. On my system it
is a timestamp set at the date and time my master started. Should
*changetime* be the date and time of *metaversion*? i.e., continuously
updating on any file system changes? If that is the case I can change my
nagios script to only warn me if the follower is a certain number of
seconds behind.
Is there a better way to monitor follower master status?
Greetings, Casper
|
|
From: Paweł K. <ma...@gm...> - 2016-06-24 07:24:26
|
Hello, client : FreeBSD 10.0, mfs 3.0.78-1. After mount mfs in client, i see in kern log : mfsmount[68215]: sysctl(kern.proc.filedesc) error: ESRCH (No such process) mfsmount[68215]: sysctl(kern.proc.filedesc) error: ESRCH (No such process) mfsmount[68221]: sysctl(kern.proc.filedesc) error: ESRCH (No such process) What could be the reason ? -- Paweł Kowalski |
|
From: 张能 <zha...@qq...> - 2016-06-17 10:40:39
|
At the first i modify the mfschunkserver.cfg with , but not reload the Chunkserver; I think maybe the reason is the confing is not effective and also is not registered on the Mfsmaster！
------------------ 原始邮件 ------------------
发件人: "能能";<103...@qq...>;
发送时间: 2016年6月17日(星期五) 晚上6:27
收件人: "piotr.konopelko"<pio...@mo...>;
抄送: "张能"<zha...@qq...>; "moosefs-users"<moo...@li...>;
主题: Re: [MooseFS-Users] hello！need help！
I have solved the problem now. I reload
the Chunkserver and restart the Mfsmaster ,then the copy can store on the named label now!
发自我的小米手机
在 Piotr Robert Konopelko <pio...@mo...>，2016年6月17日 下午6:15写道：
Hi,
thanks again!i will update moosefs version soon and thanks for the great soft again!
It's nice to hear this, thanks! :)
To help us resolve your problem, please send us information I asked you, because the bug I mentioned is not related to your issue:
Could you please send us a screenshot of "Resources" tab from MFS CGI?
Please also send us the result of the following commands:
mfsgetsclass /data/dataX/ppppp
and also:
mfslistsclass -l /data
Best regards,
--
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo...
www : https://moosefs.com
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 17 Jun 2016, at 12:10 PM, 103951999 <103...@qq...> wrote:
thanks again!i will update moosefs version soon and thanks for the great soft again!
发自我的小米手机
在 Piotr Robert Konopelko <pio...@mo...>，2016年6月17日 下午5:53写道：
Hi again,
please also update your MooseFS instance to version 3.0.78 (1. Metalogger, 2. Master Server, 3. Chunkservers, 4. Clients), because of a serious bug found in 3.0.77:
I'm attaching BUG NOTIFICATION:
https://sourceforge.net/p/moosefs/mailman/message/35157580/
Best regards,
--
<Mail Attachment.png>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo...
www : https://moosefs.com
<Mail Attachment.png> <Mail Attachment.png> <Mail Attachment.png> <Mail Attachment.png>
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 17 Jun 2016, at 11:45 AM, Piotr Robert Konopelko <pio...@mo...> wrote:
Hi,
we're very happy that you are using MooseFS! :)
Could you please send us a screenshot of "Resources" tab from MFS CGI?
Please also send us the result of the following commands:
mfsgetsclass /data/dataX/ppppp
and also:
mfslistsclass -l /data
Best regards,
--
<Mail Attachment.png>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo...
www : https://moosefs.com
<Mail Attachment.png> <Mail Attachment.png> <Mail Attachment.png> <Mail Attachment.png>
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 17 Jun 2016, at 9:54 AM, 张能 <zha...@qq...> wrote:
hello！
I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2
，and the dir is <2D0BFC08@1083F241.A9AC6357>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<3103F603@1083F241.A9AC6357>;so where is the mistake i have? please!!!!!!help
<3205FB08@1083F241.A9AC6357>
------------------------------------------------------------------------------
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/zohomanageengine_________________________________________
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/zohomanageengine_________________________________________
moosefs-users mailing list
moo...@li...
https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-17 10:36:31
|
Great! But actually restart of Master or Chunkserver shouldn't be necessary. As you noticed, you have to create and define a Storage Class first, then assign it to files / directories. Actually I suppose, that your problem might have been connected with chunk creation modes (strict, default, loose) - but of course I'm not sure, because I didn't get more info from you. Anyway - please take a look at page 14 - paragraph 2.9 "Chunk creation modes" of "MooseFS Storage Classes Manual": https://moosefs.com/Content/Downloads/moosefs-storage-classes-manual.pdf <https://moosefs.com/Content/Downloads/moosefs-storage-classes-manual.pdf> Maybe it would be more clear for you, how chunks are created and why sometimes chunks are created on different servers than selected by Storage Class. Of course it is configurable. In case of any questions, please don't hesitate to contact MooseFS-Users mailing list. I also encourage you to subscribe to our list, because important information is sent to the list firstly. You can subscribe here if you want: https://lists.sourceforge.net/lists/listinfo/moosefs-users <https://lists.sourceforge.net/lists/listinfo/moosefs-users> 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 17 Jun 2016, at 12:27 PM, 103951999 <103...@qq...> wrote: > > I have solved the problem now. I reload > the Chunkserver and restart the Mfsmaster ,then the copy can store on the named label now! > > > > 发自我的小米手机 > 在 Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>>，2016年6月17日 下午6:15写道： > > Hi, > >> thanks again!i will update moosefs version soon and thanks for the great soft again! > > It's nice to hear this, thanks! :) > > > To help us resolve your problem, please send us information I asked you, because the bug I mentioned is not related to your issue: > >> >> Could you please send us a screenshot of "Resources" tab from MFS CGI? >> >> >> Please also send us the result of the following commands: >> >> mfsgetsclass /data/dataX/ppppp >> >> and also: >> >> mfslistsclass -l /data >> > > > Best regards, > > -- > > <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 17 Jun 2016, at 12:10 PM, 103951999 <103...@qq... <mailto:103...@qq...>> wrote: >> >> thanks again!i will update moosefs version soon and thanks for the great soft again! >> >> >> >> 发自我的小米手机 >> 在 Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>>，2016年6月17日 下午5:53写道： >> >> Hi again, >> >> please also update your MooseFS instance to version 3.0.78 (1. Metalogger, 2. Master Server, 3. Chunkservers, 4. Clients), because of a serious bug found in 3.0.77: >> >> I'm attaching BUG NOTIFICATION: >> https://sourceforge.net/p/moosefs/mailman/message/35157580/ <https://sourceforge.net/p/moosefs/mailman/message/35157580/> >> >> >> Best regards, >> >> -- >> >> <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 17 Jun 2016, at 11:45 AM, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote: >>> >>> Hi, >>> >>> we're very happy that you are using MooseFS! :) >>> >>> Could you please send us a screenshot of "Resources" tab from MFS CGI? >>> >>> >>> Please also send us the result of the following commands: >>> >>> mfsgetsclass /data/dataX/ppppp >>> >>> and also: >>> >>> mfslistsclass -l /data >>> >>> >>> Best regards, >>> >>> -- >>> >>> <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 17 Jun 2016, at 9:54 AM, 张能 <zha...@qq... <mailto:zha...@qq...>> wrote: >>>> >>>> hello！ >>>> I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2 >>>> ，and the dir is <2D0BFC08@1083F241.A9AC6357>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<3103F603@1083F241.A9AC6357>;so where is the mistake i have? please!!!!!!help >>>> <3205FB08@1083F241.A9AC6357> >>>> ------------------------------------------------------------------------------ >>>> 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/zohomanageengine_________________________________________ <http://sdm.link/zohomanageengine_________________________________________> >>>> 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/zohomanageengine_________________________________________ <http://sdm.link/zohomanageengine_________________________________________> >>> 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> |
|
From: 103951999 <103...@qq...> - 2016-06-17 10:27:18
|
<div dir="ltr">I have solved the problem now. I reload<br>
</div><div dir="ltr">the Chunkserver and restart the Mfsmaster ,then the copy can store on the named label now!<br>
</div><div dir="ltr"><br>
</div><div dir="ltr"><br>
</div><div dir="ltr"><br>
</div><div class="wps_signature">发自我的小米手机</div><div class="wps_quotion">在 Piotr Robert Konopelko <pio...@mo...>，2016年6月17日 下午6:15写道：<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p></p><html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div dir="ltr" class="">thanks again!i will update moosefs version soon and thanks for the great soft again!</div></blockquote><br class=""></div><div class="">It's nice to hear this, thanks! :)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">To help us resolve your problem, please send us information I asked you, because the bug I mentioned is not related to your issue:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="" style="font-family: ArialMT;"><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><br class=""></div><div class="">Could you please send us a screenshot of "Resources" tab from MFS CGI?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please also send us the result of the following commands:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">mfsgetsclass /data/dataX/ppppp</font></div><div class=""><br class=""></div><div class="">and also:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">mfslistsclass -l /data</font></div><div class=""><br class=""></div></div></div></blockquote><div class=""><br class=""></div><br class=""><div class="">
<p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33);" class="">
Best regards,
<br class="">
<br class="">
--
</p>
<a style="text-decoration: none" href="https://moosefs.com" class="">
<img alt="MooseFS" border="0" style="float: left; margin-right: 5px;" id="E8A6C401-1927-4974-8611-C34B8C4F8A50" height="70" width="70" src="cid:245...@mo..." class="">
</a>
<p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33); margin-bottom: 10px;" class="">
</p><div style="font-weight: bold; display: inline-block; margin-top: 15px;" class="">Piotr Robert Konopelko</div>
<div class="">MooseFS Technical Support Engineer</div>
<div style="margin-top: 2px;" class=""><span style="width: 40px; float: left;" class="">e-mail</span><span style="display: inline-block;" class=""> : <a href="mailto:pio...@mo..." style="color: rgba(18,121,190,1); text-decoration: none;" class="">pio...@mo...</a></span></div>
<div style="margin-top: 0px;" class=""><span style="width: 40px; float: left;" class="">www</span><span style="display: inline-block;" class=""> : <a href="https://moosefs.com" style="color: rgba(18,121,190,1); text-decoration: none;" class="">https://moosefs.com</a></span></div>
<p class=""></p>
<p style="font-size: 0px; line-height: 16px; margin-top: 3px; font-family: Helvetica, Arial, sans-serif;" class="">
<a style="text-decoration: none; display: inline;" href="https://twitter.com/MooseFS" class="">
<img alt="Twitter" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="C187D73E-6CC4-4EE1-B55E-779D5E9812B3" src="cid:867...@mo..." class="">
</a>
<a style="text-decoration: none; display: inline;" href="https://www.facebook.com/moosefs" class="">
<img alt="Facebook" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="A8A417F1-B362-4C63-B295-8FF35B97C21D" src="cid:9A7...@mo..." class="">
</a>
<a style="text-decoration: none; display: inline;" href="https://www.linkedin.com/company/moosefs" class="">
<img alt="LinkedIn" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="C7911375-430C-4225-83ED-A01326D72E22" src="cid:F8D...@mo..." class="">
</a>
<a style="display: inline; text-decoration: none;" href="https://github.com/moosefs" class="">
<img alt="GitHub" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="24B26B97-5D60-4D9D-98F7-13F55E2E4A41" src="cid:B1D...@mo..." class="">
</a>
</p>
<p style="font-family: Helvetica, Arial, sans-serif; color: #212121; font-size: 9px; line-height: 12px;" class="">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.</p>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 17 Jun 2016, at 12:10 PM, 103951999 <<a href="mailto:103...@qq..." class="">103...@qq...</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">thanks again!i will update moosefs version soon and thanks for the great soft again!<br class="">
</div><div dir="ltr" class=""><br class="">
</div><div dir="ltr" class=""><br class="">
</div><div dir="ltr" class=""><br class="">
</div><div class="wps_signature">发自我的小米手机</div><div class="wps_quotion">在 Piotr Robert Konopelko <<a href="mailto:pio...@mo..." class="">pio...@mo...</a>>，2016年6月17日 下午5:53写道：<br type="attribution" class=""><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br class="webkit-block-placeholder"></div><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi again,<div class=""><br class=""></div><div class="">please also update your MooseFS instance to version 3.0.78 (1. Metalogger, 2. Master Server, 3. Chunkservers, 4. Clients), because of a serious bug found in 3.0.77:</div><div class=""><br class=""></div><div class="">I'm attaching BUG NOTIFICATION:</div><div class=""><a href="https://sourceforge.net/p/moosefs/mailman/message/35157580/" class="">https://sourceforge.net/p/moosefs/mailman/message/35157580/</a></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33);" class="">
Best regards,
<br class="">
<br class="">
--
</p>
<a style="text-decoration: none" href="https://moosefs.com/" class="">
<span id="cid:245...@mo..."><Mail Attachment.png></span>
</a><div style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33); margin-bottom: 10px;" class="">
<br class="webkit-block-placeholder"></div><div style="font-weight: bold; display: inline-block; margin-top: 15px;" class="">Piotr Robert Konopelko</div>
<div class="">MooseFS Technical Support Engineer</div>
<div style="margin-top: 2px;" class=""><span style="width: 40px; float: left;" class="">e-mail</span><span style="display: inline-block;" class=""> : <a href="mailto:pio...@mo..." style="color: rgba(18,121,190,1); text-decoration: none;" class="">pio...@mo...</a></span></div>
<div style="margin-top: 0px;" class=""><span style="width: 40px; float: left;" class="">www</span><span style="display: inline-block;" class=""> : <a href="https://moosefs.com/" style="color: rgba(18,121,190,1); text-decoration: none;" class="">https://moosefs.com</a></span></div><div class=""><br class="webkit-block-placeholder"></div><p style="font-size: 0px; line-height: 16px; margin-top: 3px; font-family: Helvetica, Arial, sans-serif;" class="">
<a style="text-decoration: none; display: inline;" href="https://twitter.com/MooseFS" class="">
<span id="cid:867...@mo..."><Mail Attachment.png></span>
</a>
<a style="text-decoration: none; display: inline;" href="https://www.facebook.com/moosefs" class="">
<span id="cid:9A7...@mo..."><Mail Attachment.png></span>
</a>
<a style="text-decoration: none; display: inline;" href="https://www.linkedin.com/company/moosefs" class="">
<span id="cid:F8D...@mo..."><Mail Attachment.png></span>
</a>
<a style="display: inline; text-decoration: none;" href="https://github.com/moosefs" class="">
<span id="cid:B1D...@mo..."><Mail Attachment.png></span>
</a>
</p><p style="font-family: Helvetica, Arial, sans-serif; color: #212121; font-size: 9px; line-height: 12px;" class="">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.</p>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On 17 Jun 2016, at 11:45 AM, Piotr Robert Konopelko <<a href="mailto:pio...@mo..." class="">pio...@mo...</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">we're very happy that you are using MooseFS! :)</div><div class=""><br class=""></div><div class="">Could you please send us a screenshot of "Resources" tab from MFS CGI?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please also send us the result of the following commands:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">mfsgetsclass /data/dataX/ppppp</font></div><div class=""><br class=""></div><div class="">and also:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">mfslistsclass -l /data</font></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33);" class="">
Best regards,
<br class="">
<br class="">
--
</p>
<a style="text-decoration: none" href="https://moosefs.com/" class="">
<span id="cid:245...@mo..." class=""><Mail Attachment.png></span>
</a><div style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33); margin-bottom: 10px;" class="">
<br class="webkit-block-placeholder"></div><div style="font-weight: bold; display: inline-block; margin-top: 15px;" class="">Piotr Robert Konopelko</div>
<div class="">MooseFS Technical Support Engineer</div>
<div style="margin-top: 2px;" class=""><span style="width: 40px; float: left;" class="">e-mail</span><span style="display: inline-block;" class=""> : <a href="mailto:pio...@mo..." style="color: rgba(18,121,190,1); text-decoration: none;" class="">pio...@mo...</a></span></div>
<div style="margin-top: 0px;" class=""><span style="width: 40px; float: left;" class="">www</span><span style="display: inline-block;" class=""> : <a href="https://moosefs.com/" style="color: rgba(18,121,190,1); text-decoration: none;" class="">https://moosefs.com</a></span></div><div class=""><br class="webkit-block-placeholder"></div><p style="font-size: 0px; line-height: 16px; margin-top: 3px; font-family: Helvetica, Arial, sans-serif;" class="">
<a style="text-decoration: none; display: inline;" href="https://twitter.com/MooseFS" class="">
<span id="cid:867...@mo..." class=""><Mail Attachment.png></span>
</a>
<a style="text-decoration: none; display: inline;" href="https://www.facebook.com/moosefs" class="">
<span id="cid:9A7...@mo..." class=""><Mail Attachment.png></span>
</a>
<a style="text-decoration: none; display: inline;" href="https://www.linkedin.com/company/moosefs" class="">
<span id="cid:F8D...@mo..." class=""><Mail Attachment.png></span>
</a>
<a style="display: inline; text-decoration: none;" href="https://github.com/moosefs" class="">
<span id="cid:B1D...@mo..." class=""><Mail Attachment.png></span>
</a>
</p><p style="font-family: Helvetica, Arial, sans-serif; color: #212121; font-size: 9px; line-height: 12px;" class="">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.</p>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On 17 Jun 2016, at 9:54 AM, 张能 <<a href="mailto:zha...@qq..." class="">zha...@qq...</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">hello！<br class="">
I am a moosefs user，but now i have a problem about the label can‘t be
solved。This is my web-show，i have setted label-A on host
10.1.236.93and10.1.236.92 with the copy 2<br class="">
，and the dir is <span id="cid:2D0BFC08@1083F241.A9AC6357" class=""><2D0BFC08@1083F241.A9AC6357></span>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<span id="cid:3103F603@1083F241.A9AC6357" class=""><3103F603@1083F241.A9AC6357></span>;so where is the mistake i have? please!!!!!!help <br class="">
<span id="cid:3205FB08@1083F241.A9AC6357" class=""><3205FB08@1083F241.A9AC6357></span><br class=""></div>------------------------------------------------------------------------------<br class="">What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic<br class="">patterns at an interface-level. Reveals which users, apps, and protocols are <br class="">consuming the most bandwidth. Provides multi-vendor support for NetFlow, <br class="">J-Flow, sFlow and other flows. Make informed decisions using capacity planning<br class="">reports. <a href="http://sdm.link/zohomanageengine_________________________________________" class="">http://sdm.link/zohomanageengine_________________________________________</a><br class="">moosefs-users mailing list<br class=""><a href="mailto:moo...@li..." class="">moo...@li...</a><br class=""><a href="https://lists.sourceforge.net/lists/listinfo/moosefs-users" class="">https://lists.sourceforge.net/lists/listinfo/moosefs-users</a><br class=""></div></blockquote></div><br class=""></div></div>------------------------------------------------------------------------------<br class="">What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic<br class="">patterns at an interface-level. Reveals which users, apps, and protocols are <br class="">consuming the most bandwidth. Provides multi-vendor support for NetFlow, <br class="">J-Flow, sFlow and other flows. Make informed decisions using capacity planning<br class="">reports. <a href="http://sdm.link/zohomanageengine_________________________________________" class="">http://sdm.link/zohomanageengine_________________________________________</a><br class="">moosefs-users mailing list<br class=""><a href="mailto:moo...@li..." class="">moo...@li...</a><br class=""><a href="https://lists.sourceforge.net/lists/listinfo/moosefs-users" class="">https://lists.sourceforge.net/lists/listinfo/moosefs-users</a><br class=""></div></blockquote></div><br class=""></div></div>
</blockquote></div></div></blockquote></div><br class=""></div></body></html>
</blockquote></div> |
|
From: 103951999 <103...@qq...> - 2016-06-17 10:26:47
|
<div dir="ltr">thanks again!i will update moosefs version soon and thanks for the great soft again!<br> </div><div dir="ltr"><br> </div><div dir="ltr"><br> </div><div dir="ltr"><br> </div><div class="wps_signature">发自我的小米手机</div><div class="wps_quotion">在 Piotr Robert Konopelko <pio...@mo...>，2016年6月17日 下午5:53写道：<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p></p><html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi again,<div class=""><br class=""></div><div class="">please also update your MooseFS instance to version 3.0.78 (1. Metalogger, 2. Master Server, 3. Chunkservers, 4. Clients), because of a serious bug found in 3.0.77:</div><div class=""><br class=""></div><div class="">I'm attaching BUG NOTIFICATION:</div><div class=""><a href="https://sourceforge.net/p/moosefs/mailman/message/35157580/" class="">https://sourceforge.net/p/moosefs/mailman/message/35157580/</a></div><div class=""><br class=""></div><div class=""><br class=""><div class=""> <p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33);" class=""> Best regards, <br class=""> <br class=""> -- </p> <a style="text-decoration: none" href="https://moosefs.com" class=""> <img alt="MooseFS" border="0" style="float: left; margin-right: 5px;" id="EAE29586-E0E8-45B9-9740-7E9A18F4145E" height="70" width="70" src="cid:245...@mo..." class=""> </a> <p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33); margin-bottom: 10px;" class=""> </p><div style="font-weight: bold; display: inline-block; margin-top: 15px;" class="">Piotr Robert Konopelko</div> <div class="">MooseFS Technical Support Engineer</div> <div style="margin-top: 2px;" class=""><span style="width: 40px; float: left;" class="">e-mail</span><span style="display: inline-block;" class=""> : <a href="mailto:pio...@mo..." style="color: rgba(18,121,190,1); text-decoration: none;" class="">pio...@mo...</a></span></div> <div style="margin-top: 0px;" class=""><span style="width: 40px; float: left;" class="">www</span><span style="display: inline-block;" class=""> : <a href="https://moosefs.com" style="color: rgba(18,121,190,1); text-decoration: none;" class="">https://moosefs.com</a></span></div> <p class=""></p> <p style="font-size: 0px; line-height: 16px; margin-top: 3px; font-family: Helvetica, Arial, sans-serif;" class=""> <a style="text-decoration: none; display: inline;" href="https://twitter.com/MooseFS" class=""> <img alt="Twitter" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="3B892D1B-93C2-466A-9BF2-D0DC5C477D75" src="cid:867...@mo..." class=""> </a> <a style="text-decoration: none; display: inline;" href="https://www.facebook.com/moosefs" class=""> <img alt="Facebook" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="B750C1FB-C71A-4A46-A270-B6A9316BDF63" src="cid:9A7...@mo..." class=""> </a> <a style="text-decoration: none; display: inline;" href="https://www.linkedin.com/company/moosefs" class=""> <img alt="LinkedIn" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="A52DC846-1100-4F97-80E9-CAF2C968C239" src="cid:F8D...@mo..." class=""> </a> <a style="display: inline; text-decoration: none;" href="https://github.com/moosefs" class=""> <img alt="GitHub" width="16" style="margin-bottom: 2px; margin-right: 2px; border: none; display: inline;" height="16" id="6A50E66C-E1CE-4CBA-AE4B-2CEB734C07F8" src="cid:B1D...@mo..." class=""> </a> </p> <p style="font-family: Helvetica, Arial, sans-serif; color: #212121; font-size: 9px; line-height: 12px;" class="">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.</p> </div> <br class=""><div><blockquote type="cite" class=""><div class="">On 17 Jun 2016, at 11:45 AM, Piotr Robert Konopelko <<a href="mailto:pio...@mo..." class="">pio...@mo...</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">we're very happy that you are using MooseFS! :)</div><div class=""><br class=""></div><div class="">Could you please send us a screenshot of "Resources" tab from MFS CGI?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please also send us the result of the following commands:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">mfsgetsclass /data/dataX/ppppp</font></div><div class=""><br class=""></div><div class="">and also:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">mfslistsclass -l /data</font></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><p style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33);" class=""> Best regards, <br class=""> <br class=""> -- </p> <a style="text-decoration: none" href="https://moosefs.com/" class=""> <span id="cid:245...@mo..."><Mail Attachment.png></span> </a><div style="font-family: Helvetica, Arial, sans-serif; font-size: 12px; line-height: 12px; color: rgb(33, 33, 33); margin-bottom: 10px;" class=""> <br class="webkit-block-placeholder"></div><div style="font-weight: bold; display: inline-block; margin-top: 15px;" class="">Piotr Robert Konopelko</div> <div class="">MooseFS Technical Support Engineer</div> <div style="margin-top: 2px;" class=""><span style="width: 40px; float: left;" class="">e-mail</span><span style="display: inline-block;" class=""> : <a href="mailto:pio...@mo..." style="color: rgba(18,121,190,1); text-decoration: none;" class="">pio...@mo...</a></span></div> <div style="margin-top: 0px;" class=""><span style="width: 40px; float: left;" class="">www</span><span style="display: inline-block;" class=""> : <a href="https://moosefs.com/" style="color: rgba(18,121,190,1); text-decoration: none;" class="">https://moosefs.com</a></span></div><div class=""><br class="webkit-block-placeholder"></div><p style="font-size: 0px; line-height: 16px; margin-top: 3px; font-family: Helvetica, Arial, sans-serif;" class=""> <a style="text-decoration: none; display: inline;" href="https://twitter.com/MooseFS" class=""> <span id="cid:867...@mo..."><Mail Attachment.png></span> </a> <a style="text-decoration: none; display: inline;" href="https://www.facebook.com/moosefs" class=""> <span id="cid:9A7...@mo..."><Mail Attachment.png></span> </a> <a style="text-decoration: none; display: inline;" href="https://www.linkedin.com/company/moosefs" class=""> <span id="cid:F8D...@mo..."><Mail Attachment.png></span> </a> <a style="display: inline; text-decoration: none;" href="https://github.com/moosefs" class=""> <span id="cid:B1D...@mo..."><Mail Attachment.png></span> </a> </p><p style="font-family: Helvetica, Arial, sans-serif; color: #212121; font-size: 9px; line-height: 12px;" class="">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.</p> </div> <br class=""><div class=""><blockquote type="cite" class=""><div class="">On 17 Jun 2016, at 9:54 AM, 张能 <<a href="mailto:zha...@qq..." class="">zha...@qq...</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">hello！<br class=""> I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2<br class=""> ，and the dir is <span id="cid:2D0BFC08@1083F241.A9AC6357" class=""><2D0BFC08@1083F241.A9AC6357></span>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<span id="cid:3103F603@1083F241.A9AC6357" class=""><3103F603@1083F241.A9AC6357></span>;so where is the mistake i have? please!!!!!!help <br class=""> <span id="cid:3205FB08@1083F241.A9AC6357" class=""><3205FB08@1083F241.A9AC6357></span><br class=""></div>------------------------------------------------------------------------------<br class="">What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic<br class="">patterns at an interface-level. Reveals which users, apps, and protocols are <br class="">consuming the most bandwidth. Provides multi-vendor support for NetFlow, <br class="">J-Flow, sFlow and other flows. Make informed decisions using capacity planning<br class="">reports. <a href="http://sdm.link/zohomanageengine_________________________________________" class="">http://sdm.link/zohomanageengine_________________________________________</a><br class="">moosefs-users mailing list<br class=""><a href="mailto:moo...@li..." class="">moo...@li...</a><br class=""><a href="https://lists.sourceforge.net/lists/listinfo/moosefs-users" class="">https://lists.sourceforge.net/lists/listinfo/moosefs-users</a><br class=""></div></blockquote></div><br class=""></div></div>------------------------------------------------------------------------------<br class="">What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic<br class="">patterns at an interface-level. Reveals which users, apps, and protocols are <br class="">consuming the most bandwidth. Provides multi-vendor support for NetFlow, <br class="">J-Flow, sFlow and other flows. Make informed decisions using capacity planning<br class="">reports. <a href="http://sdm.link/zohomanageengine_________________________________________" class="">http://sdm.link/zohomanageengine_________________________________________</a><br class="">moosefs-users mailing list<br class=""><a href="mailto:moo...@li..." class="">moo...@li...</a><br class="">https://lists.sourceforge.net/lists/listinfo/moosefs-users<br class=""></div></blockquote></div><br class=""></div></body></html> </blockquote></div> |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-17 10:15:14
|
Hi, > thanks again!i will update moosefs version soon and thanks for the great soft again! It's nice to hear this, thanks! :) To help us resolve your problem, please send us information I asked you, because the bug I mentioned is not related to your issue: > > Could you please send us a screenshot of "Resources" tab from MFS CGI? > > > Please also send us the result of the following commands: > > mfsgetsclass /data/dataX/ppppp > > and also: > > mfslistsclass -l /data > 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 17 Jun 2016, at 12:10 PM, 103951999 <103...@qq...> wrote: > > thanks again!i will update moosefs version soon and thanks for the great soft again! > > > > 发自我的小米手机 > 在 Piotr Robert Konopelko <pio...@mo...>，2016年6月17日 下午5:53写道： > > Hi again, > > please also update your MooseFS instance to version 3.0.78 (1. Metalogger, 2. Master Server, 3. Chunkservers, 4. Clients), because of a serious bug found in 3.0.77: > > I'm attaching BUG NOTIFICATION: > https://sourceforge.net/p/moosefs/mailman/message/35157580/ <https://sourceforge.net/p/moosefs/mailman/message/35157580/> > > > Best regards, > > -- > > <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 17 Jun 2016, at 11:45 AM, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote: >> >> Hi, >> >> we're very happy that you are using MooseFS! :) >> >> Could you please send us a screenshot of "Resources" tab from MFS CGI? >> >> >> Please also send us the result of the following commands: >> >> mfsgetsclass /data/dataX/ppppp >> >> and also: >> >> mfslistsclass -l /data >> >> >> Best regards, >> >> -- >> >> <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 17 Jun 2016, at 9:54 AM, 张能 <zha...@qq... <mailto:zha...@qq...>> wrote: >>> >>> hello！ >>> I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2 >>> ，and the dir is <2D0BFC08@1083F241.A9AC6357>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<3103F603@1083F241.A9AC6357>;so where is the mistake i have? please!!!!!!help >>> <3205FB08@1083F241.A9AC6357> >>> ------------------------------------------------------------------------------ >>> 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/zohomanageengine_________________________________________ <http://sdm.link/zohomanageengine_________________________________________> >>> 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/zohomanageengine_________________________________________ <http://sdm.link/zohomanageengine_________________________________________> >> moosefs-users mailing list >> moo...@li... <mailto:moo...@li...> >> https://lists.sourceforge.net/lists/listinfo/moosefs-users > |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-17 09:53:21
|
Hi again, please also update your MooseFS instance to version 3.0.78 (1. Metalogger, 2. Master Server, 3. Chunkservers, 4. Clients), because of a serious bug found in 3.0.77: I'm attaching BUG NOTIFICATION: https://sourceforge.net/p/moosefs/mailman/message/35157580/ <https://sourceforge.net/p/moosefs/mailman/message/35157580/> 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 17 Jun 2016, at 11:45 AM, Piotr Robert Konopelko <pio...@mo...> wrote: > > Hi, > > we're very happy that you are using MooseFS! :) > > Could you please send us a screenshot of "Resources" tab from MFS CGI? > > > Please also send us the result of the following commands: > > mfsgetsclass /data/dataX/ppppp > > and also: > > mfslistsclass -l /data > > > Best regards, > > -- > > <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 17 Jun 2016, at 9:54 AM, 张能 <zha...@qq... <mailto:zha...@qq...>> wrote: >> >> hello！ >> I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2 >> ，and the dir is <2D0BFC08@1083F241.A9AC6357>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<3103F603@1083F241.A9AC6357>;so where is the mistake i have? please!!!!!!help >> <3205FB08@1083F241.A9AC6357> >> ------------------------------------------------------------------------------ >> 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/zohomanageengine_________________________________________ <http://sdm.link/zohomanageengine_________________________________________> >> 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/zohomanageengine_________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-17 09:45:46
|
Hi, we're very happy that you are using MooseFS! :) Could you please send us a screenshot of "Resources" tab from MFS CGI? Please also send us the result of the following commands: mfsgetsclass /data/dataX/ppppp and also: mfslistsclass -l /data 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 17 Jun 2016, at 9:54 AM, 张能 <zha...@qq...> wrote: > > hello！ > I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2 > ，and the dir is <2D0BFC08@1083F241.A9AC6357>;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but<3103F603@1083F241.A9AC6357>;so where is the mistake i have? please!!!!!!help > <3205FB08@1083F241.A9AC6357> > ------------------------------------------------------------------------------ > 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/zohomanageengine_________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: 张能 <zha...@qq...> - 2016-06-17 07:54:30
|
hello！ I am a moosefs user，but now i have a problem about the label can‘t be solved。This is my web-show，i have setted label-A on host 10.1.236.93and10.1.236.92 with the copy 2 ，and the dir is ;now ! i creat a new file,but the copy of file not be stored on 92 and 93 but;so where is the mistake i have? please!!!!!!help |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-15 13:29:30
|
Dear Paweł, In MooseFS 3.0.75 setting "Label goal" has been extended to Storage Classes. Now you can define a Storage Class (with name) and its definition (e.g. mentioned 2A). Please read the updated "MooseFS Storage Classes Manual". You can obtain it from the following website: https://moosefs.com/documentation.html <https://moosefs.com/documentation.html> 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 15 Jun 2016, at 3:22 PM, Paweł Kowalski <ma...@gm...> wrote: > > Hello, > > > moosefs-client 3.0.78-1 > Debian Jessie 8.5 > > When i type : > > mfssetgoal 2A /moose > > i getting : > > 2A: wrong goal definition > set objects goal (desired number of copies) > > > What I'm doing/understand wrong ? > > -- > > Paweł Kowalski > ------------------------------------------------------------------------------ > 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://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381_________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Paweł K. <ma...@gm...> - 2016-06-15 13:22:32
|
Hello, moosefs-client 3.0.78-1 Debian Jessie 8.5 When i type : mfssetgoal 2A /moose i getting : 2A: wrong goal definition set objects goal (desired number of copies) What I'm doing/understand wrong ? -- Paweł Kowalski |
|
From: Krzysztof K. <krz...@mo...> - 2016-06-14 09:41:27
|
Dear MooseFS Users, Today we have identified serious bug that affects MooseFS versions: - 3.0.75 Pro and Community Edition - 3.0.76 Pro and Community Edition - 3.0.77 Pro and Community Edition The bug manifests in mfschunkserver component in rare and specific conditions involving sparse files (containing blocks of zeros larger than 512) and might lead to silent chunk corruption. Solution If you are running one of the affected versions we strongly recommend updating as soon as possible (starting from mfschunkserver components) to MooseFS 3.0.78 that was released today. In case of any questions please contact MooseFS Support (su...@mo... <mailto:su...@mo...>). Best Regards, Krzysztof Kielak Moosefs.com | Director of Operations and Customer Support |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-10 17:21:12
|
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 |
|
From: Krzysztof K. <krz...@mo...> - 2016-06-10 07:30:36
|
Hello Alexander, MooseFS reports disk transfers based on time it takes to complete the write operation (write() system call) for the chunkserver process. Since MooseFS does not use direct I/O, all writes are using local filesystem cache (buffer cache on chunkserver). One could say, that mfscgi/mfscli are reporting time/transfer to physical device through buffer cache. If your system is busy, that you might see drops in transfer rates due to the fact, that system needs to do buffer cache flushes more often. You can observe the same behaviour with simple dd command test. Let’s simulate chunk write (64MiB using block size of 64KiB) operation using dd command: [root@pg2 home]# sync ; sync [root@pg2 home]# time dd if=/dev/zero of=test01.dat bs=64k count=1024 1024+0 records in 1024+0 records out 67108864 bytes (67 MB) copied, 0.0295609 s, 2.3 GB/s real 0m0.030s user 0m0.001s sys 0m0.029s The time (0.030 s), and in consequence, the transfer rate (2.3GB/s) that you get is from the Linux buffer cache. To calculate the actual transfer to the disk, you should also take into account the time it takes to do the sync operation, which flushes dirty pages from buffer cache to the disk (Please note, that I’ve performed sync command before dd, to flush any dirty pages already in buffer cache, so to have as clean buffer cache as possible before dd command) [root@pg2 home]# time sync real 0m0.508s user 0m0.001s sys 0m0.012s As you can see to complete sync system needed additional 0.508 s for actual transfer from buffer cache to physical device. If you do the math, you’ll get the transfer rate of ~118 MiB/s [root@pg2 home]# bc bc 1.06.95 Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. scale=4 67108864/(0.030 + 0.508) 124737665.4275 ./(1024*1024) 118.9591 I hope that explanation was clear enough, but in case of further questions please don’t hesitate to contact us. Best Regards, Krzysztof Kielak Moosefs.com | Director of Operations and Customer Support Mobile: +48 601 476 440 > On 10 Jun 2016, at 02:07, Alexander Lazarev <gu...@gm...> wrote: > > Hello everyone! > > I’m getting weird disk statistics(write transfer) in web monitor(cgiserv). It shows like from 500 to 900 MiB/s per single sata disk. Am I doing/understanding something wrong or this stats are incorrect? > Cheers. > Alexander Lazarev. > ------------------------------------------------------------------------------ > 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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Alexander L. <gu...@gm...> - 2016-06-10 00:07:13
|
Hello everyone! I’m getting weird disk statistics(write transfer) in web monitor(cgiserv). It shows like from 500 to 900 MiB/s per single sata disk. Am I doing/understanding something wrong or this stats are incorrect? Cheers. Alexander Lazarev. |
|
From: web u. <web...@gm...> - 2016-06-09 22:10:16
|
I had a old ppa in /etc/apt/source.list replaced it with /etc/apt/source.list.d/moosefs.list with an explicit version number and followed all the instructions 2.0.77 -> 2.089 [brought up servers] -> shutdown and backup again -> 3.0.77 Everything went very smoothly. Thanks for the awesome support and such a rock solid product! On Thu, Jun 9, 2016 at 9:49 AM, Piotr Robert Konopelko < pio...@mo...> wrote: > I meant when I upgrade the chunk servers to 3.x is there any chance that > they will not recognize the data format from the 2.x chunk servers? > > > There is no such chance neither theoretically nor practically - of course > if all your disks are OK. > > I mean there might happen a situation, that during start, MooseFS > Chunkserver detects a broken disk and then some undergoal chunks may > appear, but this is normal and actually does not connected with upgrade > from MFS 2.0 to 3.0 at all. > > We ran a lot of tests of MooseFS 3 in past months, then we decided to > deploy it on our production environments, and then, after over a month of > running MooseFS 3 on our production environments and no error reports, we > decided to release it to You - Users, to let you use really, really > well-tested version. > > > Best regards, > > > -- > [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 09 Jun 2016, at 3:39 PM, web user <web...@gm...> wrote: > > Thanks again. You guys are great... > > I meant when I upgrade the chunk servers to 3.x is there any chance that > they will not recognize the data format from the 2.x chunk servers? > > > > On Thu, Jun 9, 2016 at 9:38 AM, Piotr Robert Konopelko < > pio...@mo...> wrote: > >> Hi, >> >> @1. The issue is, that newer (3.0.x) MooseFS Clients are not able to >> "talk" with old (2.0.x) MooseFS Master Server (Client returns error: >> "incompatible Master version"). >> >> Actually there is no problem when you follow our guidelines from "Upgrade >> Guide" - I mean do the upgrade in supported order (1. Master Server, cli, >> cgi, cgiserv, 2. Metaloggers, 3. Chunkservers, 4. *Clients / Mounts* - >> they should be upgraded *at the end*). >> >> Of course 2.0.x Clients can connect to 3.0.x Master Server. >> >> @2. I'm not sure what did you mean - could you be more precise? >> >> Best regards, >> >> -- >> <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 09 Jun 2016, at 3:24 PM, web user <web...@gm...> wrote: >> >> Thanks for the quick server. Couple of quick followup questions: >> >> 1. What was the problem people were referring to with mounts not >> recognized? >> 2. Is the chunk server format still the same? >> >> >> > > |
|
From: Leszek S. <tw...@ms...> - 2016-06-09 16:24:28
|
Hi, are you planning any kind of Configuration GUI, additionally to editing text files? 2016-06-09 15:22 GMT+02:00 Piotr Robert Konopelko < pio...@mo...>: > Hi Web User, > > we are in progress of creating such document, but actually, Chapter 2: > "MooseFS 2.0 (CE and Pro) upgrade to newer version" of the document you > mentioned applies here. > > The only difference is, that now you have to change the repository URL in > /etc/apt/sources.list.d/moosefs.list or equivalent (as I described in > mail named "[MooseFS-Users] MooseFS 3.0.77 - Stable Release"). > Please remember to do a configuration (/etc/mfs) and metadata ( > /var/lib/mfs) backup before starting the upgrade. > > > > Best regards, > > > -- > [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 09 Jun 2016, at 3:04 PM, web user <web...@gm...> wrote: > > Hi, > > I'm currently running 2.0.81 on my production servers and clients. I'd > like to upgrade everything to latest release 3.0.77. Is there any document > that describes that. I checked under moosefs/docs and all I see is > https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf which describes > how to upgrade to 2.0. > > Also is upgrading to the latest 2.088 as simple as running: > > apt-get update > apt-get upgrade > > On each of the hosts. Also before I upgrade do I shut down all the > services master/clients/etc... > > Regards, > > WU > > ------------------------------------------------------------------------------ > 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. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_________________________________________ > 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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > -- -- Leszek A. Szczepanowski tw...@ms... |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-09 13:50:34
|
> Thanks again. You guys are great... And thanks for nice words! :) Best, 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 09 Jun 2016, at 3:39 PM, web user <web...@gm...> wrote: > > Thanks again. You guys are great... > > I meant when I upgrade the chunk servers to 3.x is there any chance that they will not recognize the data format from the 2.x chunk servers? > > > > On Thu, Jun 9, 2016 at 9:38 AM, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote: > Hi, > > @1. The issue is, that newer (3.0.x) MooseFS Clients are not able to "talk" with old (2.0.x) MooseFS Master Server (Client returns error: "incompatible Master version"). > > Actually there is no problem when you follow our guidelines from "Upgrade Guide" - I mean do the upgrade in supported order (1. Master Server, cli, cgi, cgiserv, 2. Metaloggers, 3. Chunkservers, 4. Clients / Mounts - they should be upgraded at the end). > > Of course 2.0.x Clients can connect to 3.0.x Master Server. > > @2. I'm not sure what did you mean - could you be more precise? > > Best regards, > > -- > > <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 09 Jun 2016, at 3:24 PM, web user <web...@gm... <mailto:web...@gm...>> wrote: >> >> Thanks for the quick server. Couple of quick followup questions: >> >> 1. What was the problem people were referring to with mounts not recognized? >> 2. Is the chunk server format still the same? > > |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-09 13:49:38
|
> I meant when I upgrade the chunk servers to 3.x is there any chance that they will not recognize the data format from the 2.x chunk servers? There is no such chance neither theoretically nor practically - of course if all your disks are OK. I mean there might happen a situation, that during start, MooseFS Chunkserver detects a broken disk and then some undergoal chunks may appear, but this is normal and actually does not connected with upgrade from MFS 2.0 to 3.0 at all. We ran a lot of tests of MooseFS 3 in past months, then we decided to deploy it on our production environments, and then, after over a month of running MooseFS 3 on our production environments and no error reports, we decided to release it to You - Users, to let you use really, really well-tested version. 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 09 Jun 2016, at 3:39 PM, web user <web...@gm...> wrote: > > Thanks again. You guys are great... > > I meant when I upgrade the chunk servers to 3.x is there any chance that they will not recognize the data format from the 2.x chunk servers? > > > > On Thu, Jun 9, 2016 at 9:38 AM, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote: > Hi, > > @1. The issue is, that newer (3.0.x) MooseFS Clients are not able to "talk" with old (2.0.x) MooseFS Master Server (Client returns error: "incompatible Master version"). > > Actually there is no problem when you follow our guidelines from "Upgrade Guide" - I mean do the upgrade in supported order (1. Master Server, cli, cgi, cgiserv, 2. Metaloggers, 3. Chunkservers, 4. Clients / Mounts - they should be upgraded at the end). > > Of course 2.0.x Clients can connect to 3.0.x Master Server. > > @2. I'm not sure what did you mean - could you be more precise? > > Best regards, > > -- > > <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 09 Jun 2016, at 3:24 PM, web user <web...@gm... <mailto:web...@gm...>> wrote: >> >> Thanks for the quick server. Couple of quick followup questions: >> >> 1. What was the problem people were referring to with mounts not recognized? >> 2. Is the chunk server format still the same? > > |
|
From: web u. <web...@gm...> - 2016-06-09 13:40:04
|
Thanks again. You guys are great... I meant when I upgrade the chunk servers to 3.x is there any chance that they will not recognize the data format from the 2.x chunk servers? On Thu, Jun 9, 2016 at 9:38 AM, Piotr Robert Konopelko < pio...@mo...> wrote: > Hi, > > @1. The issue is, that newer (3.0.x) MooseFS Clients are not able to > "talk" with old (2.0.x) MooseFS Master Server (Client returns error: > "incompatible Master version"). > > Actually there is no problem when you follow our guidelines from "Upgrade > Guide" - I mean do the upgrade in supported order (1. Master Server, cli, > cgi, cgiserv, 2. Metaloggers, 3. Chunkservers, 4. *Clients / Mounts* - > they should be upgraded *at the end*). > > Of course 2.0.x Clients can connect to 3.0.x Master Server. > > @2. I'm not sure what did you mean - could you be more precise? > > Best regards, > > -- > [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 09 Jun 2016, at 3:24 PM, web user <web...@gm...> wrote: > > Thanks for the quick server. Couple of quick followup questions: > > 1. What was the problem people were referring to with mounts not > recognized? > 2. Is the chunk server format still the same? > > > |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-09 13:38:31
|
Hi, @1. The issue is, that newer (3.0.x) MooseFS Clients are not able to "talk" with old (2.0.x) MooseFS Master Server (Client returns error: "incompatible Master version"). Actually there is no problem when you follow our guidelines from "Upgrade Guide" - I mean do the upgrade in supported order (1. Master Server, cli, cgi, cgiserv, 2. Metaloggers, 3. Chunkservers, 4. Clients / Mounts - they should be upgraded at the end). Of course 2.0.x Clients can connect to 3.0.x Master Server. @2. I'm not sure what did you mean - could you be more precise? 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 09 Jun 2016, at 3:24 PM, web user <web...@gm...> wrote: > > Thanks for the quick server. Couple of quick followup questions: > > 1. What was the problem people were referring to with mounts not recognized? > 2. Is the chunk server format still the same? |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-09 13:22:30
|
Hi Web User, we are in progress of creating such document, but actually, Chapter 2: "MooseFS 2.0 (CE and Pro) upgrade to newer version" of the document you mentioned applies here. The only difference is, that now you have to change the repository URL in /etc/apt/sources.list.d/moosefs.list or equivalent (as I described in mail named "[MooseFS-Users] MooseFS 3.0.77 - Stable Release"). Please remember to do a configuration (/etc/mfs) and metadata (/var/lib/mfs) backup before starting the 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 09 Jun 2016, at 3:04 PM, web user <web...@gm...> wrote: > > Hi, > > I'm currently running 2.0.81 on my production servers and clients. I'd like to upgrade everything to latest release 3.0.77. Is there any document that describes that. I checked under moosefs/docs and all I see is https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf <https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf> which describes how to upgrade to 2.0. > > Also is upgrading to the latest 2.088 as simple as running: > > apt-get update > apt-get upgrade > > On each of the hosts. Also before I upgrade do I shut down all the services master/clients/etc... > > Regards, > > WU > ------------------------------------------------------------------------------ > 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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: web u. <web...@gm...> - 2016-06-09 13:04:12
|
Hi, I'm currently running 2.0.81 on my production servers and clients. I'd like to upgrade everything to latest release 3.0.77. Is there any document that describes that. I checked under moosefs/docs and all I see is https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf which describes how to upgrade to 2.0. Also is upgrading to the latest 2.088 as simple as running: apt-get update apt-get upgrade On each of the hosts. Also before I upgrade do I shut down all the services master/clients/etc... Regards, WU |
|
From: Piotr R. K. <pio...@mo...> - 2016-06-09 12:06:35
|
Hi All, small errata. Instead of: > "It can be done by typing explicite "3.0.75" instead of "stable" in repo URL (as I mentioned in my previous mail in reply to Steven's mail - attaching in quote)." it should be of course: > "It can be done by typing explicite "3.0.77" instead of "stable" in repo URL (as I mentioned in my previous mail in reply to Steven's mail - attaching in quote)." I'm sorry for the mistake. 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 09 Jun 2016, at 1:19 PM, Piotr Robert Konopelko <pio...@mo...> wrote: > > Dear MooseFS Users, > > after some notifications from Users about incompatibility of 3.0.x Mounts with 2.0.x Master Servers, we decided to rollback default "stable" symlink in our repository structure to 2.0.89. > > It doesn't mean, that MooseFS 3.0.77 is not stable! > > We did it only to prevent compatibility issues of 3.0.x Mounts with 2.0.x Masters in Users' MooseFS instances. > > We still recommend and encourage you to upgrade to 3.0.77. > It can be done by typing explicite "3.0.75" instead of "stable" in repo URL (as I mentioned in my previous mail in reply to Steven's mail - attaching in quote). > > Tomorrow we are going to propose a better repository URLs structure. > Please watch the mailing list and our website <https://moosefs.com/download.html> tomorrow. > > 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 08 Jun 2016, at 6:14 PM, Piotr Robert Konopelko <pio...@mo... <mailto:pio...@mo...>> wrote: >> >> Dear Steven, >> >> thank you very much for your remark. I'd like to let you (and the rest of MooseFS-Users) know, that it is possible to "control" the version of MooseFS on moosefs.list repo sources file. It's described on MooseFS Download page <https://moosefs.com/download.html>. Let me quote some essentials: >> >> There is also a possibility to use version number instead of "branch" if you want to decide exactly which version of MooseFS you want to upgrade to (e.g. 3.0.75-1): >> >> http://ppa.moosefs.com/3.0.75/[rest <http://ppa.moosefs.com/3.0.75/[rest> of url] >> If you want to use this option, please remember you need to manually change version number on each server to newer one before doing an upgrade. >> >> >> So it is possible to set up your MooseFS repository in a "controlled way". In such case, just put in /etc/apt/sources.list.d/moosefs.list (or equivalent in other OS) the following entry: >> >> deb http://ppa.moosefs.com/ <http://ppa.moosefs.com/>2.0.89/apt/ubuntu/trusty trusty main >> >> Then, when your upgrade is planned, before starting it, just change it to: >> >> deb http://ppa.moosefs.com/ <http://ppa.moosefs.com/>3.0.77/apt/ubuntu/trusty trusty main >> >> >> This is a very good way to control MooseFS upgrades, since e.g. MooseFS Master Server upgrade usually has to be planned in production environments. The only con of this way is that you have to check manually if there's a newer version of MooseFS available. >> >> >> Best regards, >> >> -- >> >> <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 08 Jun 2016, at 4:24 PM, Wilson, Steven M <st...@pu... <mailto:st...@pu...>> wrote: >>> >>> That's great news... thanks! >>> >>> One warning to other users: Now that v. 3.0.x is the stable version, any package upgrade you perform will automatically pull in this version. I was reminded of this today when I had to take down one of my MooseFS master servers to replace its UPS. Since I was rebooting the master server, I decided to perform a full package upgrade on it (Ubuntu: apt-get dist-upgrade). That, of course, upgraded all MooseFS components to 3.0.77 from 2.0.89. But I have numerous MooseFS master servers still running 2.0.89 and the new mfsmount won't mount these older (2.0.x) MooseFS file systems. I will probably mark as held the moosefs-client package on all my workstations until I have upgraded all MooseFS master servers to 3.0.x. I hope this helps prevent an unexpected surprise to some other user! >>> >>> Best regards, >>> Steve > > ------------------------------------------------------------------------------ > 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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
84 messages has been excluded from this view by a project administrator.
