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: Krzysztof K. <krz...@mo...> - 2015-03-31 05:03:07
|
Dear Vineet, One option for using MooseFS on Windows is to setup a gateway through Samba servers possibly running on few chunkservers to spread the load from the clients. If you need any assistance with such setup we would be happy to help you. LizardFS native Windows client seems to be only “youtube-ware”. > On 30 Mar 2015, at 19:55, web user <web...@gm...> wrote: > > Hi Guys, > > I got the client working on Mac and Linux. Both work great. Any chance to get a client working on Windows? I see that LizardFS has a native windows client, but about 15 minutes of googling did not get me anything. > > Any pointers would be much appreciated. > > Regards, > > Vineet > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/_______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users Best Regards, Krzysztof Kielak Director of Operations and Customer Support Mobile: +48 601 476 440 |
|
From: web u. <web...@gm...> - 2015-03-30 17:55:54
|
Hi Guys, I got the client working on Mac and Linux. Both work great. Any chance to get a client working on Windows? I see that LizardFS has a native windows client, but about 15 minutes of googling did not get me anything. Any pointers would be much appreciated. Regards, Vineet |
|
From: Aleksander W. <ale...@mo...> - 2015-03-23 08:30:56
|
Hi Yes of course. We are working on it. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 03/23/2015 08:59 AM, Akhobadze Alexander wrote: > Hi All! > Unfortunately in the FreeBSD ports collection there is a 1.6.27-5 version of the moosefs port :--( > Is it planned to update it ? > > Wbr Alexander > > ====================================================== > > Hi, > > The update from 2.0.x CE version to 2.0.60 is similar to upgrade from 1.6.x. You need to remove old packages and install 2.0.60 that should start with all config and metadata files from previous version. > > We recommend starting from the master server. > > Before any deinstallation/installationplease make sure that you have valid backup of your config files and metadata files. > > ------ > Pozdrawiam, > Krzysztof Kielak > > -----Original Message----- > From: "Neddy, NH. Nam" <na...@nd...> > Date: Sat, 21 Mar 2015 08:18:16 > Cc: moo...@li...<moo...@li...> > Subject: Re: [MooseFS-Users] MooseFS 2.0.60-1 released and back on GPL > > Hi, > > I'm using MooseFS CE and was trying to update to 2.0.60 but can't, > because the package names were changed (from moosefs-ce-xxx to > moosefs-xxx). Do I have to rebuild the whole FS? > > On Sat, Mar 21, 2015 at 2:12 AM, WK <wk...@bn...> wrote: >> Excellent, Excellent. >> >> We are still on 1.6.27. >> >> Can we directly upgrade to 2.0.60 or is there a recommended intermediate >> step. >> >> -wk >> >> On 3/20/2015 11:40 AM, Davies Liu wrote: >>> This is great news! >>> >>> I had created a git mirror for recent releases to track the changes: >>> https://github.com/davies/moosefs/commits/master >>> >>> On Fri, Mar 20, 2015 at 7:48 AM, Aleksander Wieliczko >>> <ale...@mo...> wrote: >>>> Hi. >>>> Yes change log is available on moosefs.org site >>>> >>>> http://www.moosefs.org/changelog.html >>>> >>>> Best regards >>>> Aleksander Wieliczko >>>> Technical Support Engineer >>>> MooseFS.com >>>> >>>> On 03/20/2015 03:42 PM, Steve Wilson wrote: >>>> >>>> Hi, >>>> >>>> Is there some form of release notes indicating the features and bug fixes >>>> included in this release? >>>> >>>> Thanks! >>>> >>>> Steve >>>> >>>> On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: >>>> >>>> Dear MooseFS Community, >>>> >>>> We are very excited to announce that MooseFS is back on GPL license. >>>> >>>> From now on the MooseFS naming convention and licensing changes, so MooseFS >>>> CE (Community Edition) will now be referred to as MooseFS. >>>> >>>> MooseFS 2.0.60 (previously named CE) released today and all upcoming >>>> releases will be licensed under GPLv2. The change is our response to the >>>> feedback that we have got from the community after moving to proprietary >>>> license while introducing version 2.x. >>>> >>>> MooseFS PRO name and licensing will stay unchanged. >>>> >>>> Version 2.0.60 is the most stable and reliable release of 2.x branch and >>>> becomes a natural bridge to version 3.x planned to be released later this >>>> month. >>>> >>>> For more informations on installation or update procedures please visit >>>> https://moosefs.com/download.html >>>> >>>> Best Regards, >>>> MooseFS Team > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Akhobadze A. <akh...@ri...> - 2015-03-23 08:16:59
|
Hi All! Unfortunately in the FreeBSD ports collection there is a 1.6.27-5 version of the moosefs port :--( Is it planned to update it ? Wbr Alexander ====================================================== Hi, The update from 2.0.x CE version to 2.0.60 is similar to upgrade from 1.6.x. You need to remove old packages and install 2.0.60 that should start with all config and metadata files from previous version. We recommend starting from the master server. Before any deinstallation/installationplease make sure that you have valid backup of your config files and metadata files. ------ Pozdrawiam, Krzysztof Kielak -----Original Message----- From: "Neddy, NH. Nam" <na...@nd...> Date: Sat, 21 Mar 2015 08:18:16 Cc: moo...@li...<moo...@li...> Subject: Re: [MooseFS-Users] MooseFS 2.0.60-1 released and back on GPL Hi, I'm using MooseFS CE and was trying to update to 2.0.60 but can't, because the package names were changed (from moosefs-ce-xxx to moosefs-xxx). Do I have to rebuild the whole FS? On Sat, Mar 21, 2015 at 2:12 AM, WK <wk...@bn...> wrote: > Excellent, Excellent. > > We are still on 1.6.27. > > Can we directly upgrade to 2.0.60 or is there a recommended intermediate > step. > > -wk > > On 3/20/2015 11:40 AM, Davies Liu wrote: >> This is great news! >> >> I had created a git mirror for recent releases to track the changes: >> https://github.com/davies/moosefs/commits/master >> >> On Fri, Mar 20, 2015 at 7:48 AM, Aleksander Wieliczko >> <ale...@mo...> wrote: >>> Hi. >>> Yes change log is available on moosefs.org site >>> >>> http://www.moosefs.org/changelog.html >>> >>> Best regards >>> Aleksander Wieliczko >>> Technical Support Engineer >>> MooseFS.com >>> >>> On 03/20/2015 03:42 PM, Steve Wilson wrote: >>> >>> Hi, >>> >>> Is there some form of release notes indicating the features and bug fixes >>> included in this release? >>> >>> Thanks! >>> >>> Steve >>> >>> On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: >>> >>> Dear MooseFS Community, >>> >>> We are very excited to announce that MooseFS is back on GPL license. >>> >>> From now on the MooseFS naming convention and licensing changes, so MooseFS >>> CE (Community Edition) will now be referred to as MooseFS. >>> >>> MooseFS 2.0.60 (previously named CE) released today and all upcoming >>> releases will be licensed under GPLv2. The change is our response to the >>> feedback that we have got from the community after moving to proprietary >>> license while introducing version 2.x. >>> >>> MooseFS PRO name and licensing will stay unchanged. >>> >>> Version 2.0.60 is the most stable and reliable release of 2.x branch and >>> becomes a natural bridge to version 3.x planned to be released later this >>> month. >>> >>> For more informations on installation or update procedures please visit >>> https://moosefs.com/download.html >>> >>> Best Regards, >>> MooseFS Team |
|
From: Krzysztof K. <krz...@mo...> - 2015-03-21 08:47:29
|
Hi, The update from 2.0.x CE version to 2.0.60 is similar to upgrade from 1.6.x. You need to remove old packages and install 2.0.60 that should start with all config and metadata files from previous version. We recommend starting from the master server. Before any deinstallation/installationplease make sure that you have valid backup of your config files and metadata files. ------ Pozdrawiam, Krzysztof Kielak -----Original Message----- From: "Neddy, NH. Nam" <na...@nd...> Date: Sat, 21 Mar 2015 08:18:16 Cc: moo...@li...<moo...@li...> Subject: Re: [MooseFS-Users] MooseFS 2.0.60-1 released and back on GPL Hi, I'm using MooseFS CE and was trying to update to 2.0.60 but can't, because the package names were changed (from moosefs-ce-xxx to moosefs-xxx). Do I have to rebuild the whole FS? On Sat, Mar 21, 2015 at 2:12 AM, WK <wk...@bn...> wrote: > Excellent, Excellent. > > We are still on 1.6.27. > > Can we directly upgrade to 2.0.60 or is there a recommended intermediate > step. > > -wk > > On 3/20/2015 11:40 AM, Davies Liu wrote: >> This is great news! >> >> I had created a git mirror for recent releases to track the changes: >> https://github.com/davies/moosefs/commits/master >> >> On Fri, Mar 20, 2015 at 7:48 AM, Aleksander Wieliczko >> <ale...@mo...> wrote: >>> Hi. >>> Yes change log is available on moosefs.org site >>> >>> http://www.moosefs.org/changelog.html >>> >>> Best regards >>> Aleksander Wieliczko >>> Technical Support Engineer >>> MooseFS.com >>> >>> On 03/20/2015 03:42 PM, Steve Wilson wrote: >>> >>> Hi, >>> >>> Is there some form of release notes indicating the features and bug fixes >>> included in this release? >>> >>> Thanks! >>> >>> Steve >>> >>> On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: >>> >>> Dear MooseFS Community, >>> >>> We are very excited to announce that MooseFS is back on GPL license. >>> >>> From now on the MooseFS naming convention and licensing changes, so MooseFS >>> CE (Community Edition) will now be referred to as MooseFS. >>> >>> MooseFS 2.0.60 (previously named CE) released today and all upcoming >>> releases will be licensed under GPLv2. The change is our response to the >>> feedback that we have got from the community after moving to proprietary >>> license while introducing version 2.x. >>> >>> MooseFS PRO name and licensing will stay unchanged. >>> >>> Version 2.0.60 is the most stable and reliable release of 2.x branch and >>> becomes a natural bridge to version 3.x planned to be released later this >>> month. >>> >>> For more informations on installation or update procedures please visit >>> https://moosefs.com/download.html >>> >>> Best Regards, >>> MooseFS Team >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming The Go Parallel Website, >>> sponsored >>> by Intel and developed in partnership with Slashdot Media, is your hub for >>> all >>> things parallel software development, from weekly thought leadership blogs >>> to >>> news, videos, case studies, tutorials and more. Take a look and join the >>> conversation now. http://goparallel.sourceforge.net/ >>> >>> >>> >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming The Go Parallel Website, >>> sponsored >>> by Intel and developed in partnership with Slashdot Media, is your hub for >>> all >>> things parallel software development, from weekly thought leadership blogs >>> to >>> news, videos, case studies, tutorials and more. Take a look and join the >>> conversation now. http://goparallel.sourceforge.net/ >>> >>> >>> >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming The Go Parallel Website, >>> sponsored >>> by Intel and developed in partnership with Slashdot Media, is your hub for >>> all >>> things parallel software development, from weekly thought leadership blogs >>> to >>> news, videos, case studies, tutorials and more. Take a look and join the >>> conversation now. http://goparallel.sourceforge.net/ >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >> >> > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Neddy, N. N. <na...@nd...> - 2015-03-21 01:43:02
|
Hi, I'm using MooseFS CE and was trying to update to 2.0.60 but can't, because the package names were changed (from moosefs-ce-xxx to moosefs-xxx). Do I have to rebuild the whole FS? On Sat, Mar 21, 2015 at 2:12 AM, WK <wk...@bn...> wrote: > Excellent, Excellent. > > We are still on 1.6.27. > > Can we directly upgrade to 2.0.60 or is there a recommended intermediate > step. > > -wk > > On 3/20/2015 11:40 AM, Davies Liu wrote: >> This is great news! >> >> I had created a git mirror for recent releases to track the changes: >> https://github.com/davies/moosefs/commits/master >> >> On Fri, Mar 20, 2015 at 7:48 AM, Aleksander Wieliczko >> <ale...@mo...> wrote: >>> Hi. >>> Yes change log is available on moosefs.org site >>> >>> http://www.moosefs.org/changelog.html >>> >>> Best regards >>> Aleksander Wieliczko >>> Technical Support Engineer >>> MooseFS.com >>> >>> On 03/20/2015 03:42 PM, Steve Wilson wrote: >>> >>> Hi, >>> >>> Is there some form of release notes indicating the features and bug fixes >>> included in this release? >>> >>> Thanks! >>> >>> Steve >>> >>> On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: >>> >>> Dear MooseFS Community, >>> >>> We are very excited to announce that MooseFS is back on GPL license. >>> >>> From now on the MooseFS naming convention and licensing changes, so MooseFS >>> CE (Community Edition) will now be referred to as MooseFS. >>> >>> MooseFS 2.0.60 (previously named CE) released today and all upcoming >>> releases will be licensed under GPLv2. The change is our response to the >>> feedback that we have got from the community after moving to proprietary >>> license while introducing version 2.x. >>> >>> MooseFS PRO name and licensing will stay unchanged. >>> >>> Version 2.0.60 is the most stable and reliable release of 2.x branch and >>> becomes a natural bridge to version 3.x planned to be released later this >>> month. >>> >>> For more informations on installation or update procedures please visit >>> https://moosefs.com/download.html >>> >>> Best Regards, >>> MooseFS Team >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming The Go Parallel Website, >>> sponsored >>> by Intel and developed in partnership with Slashdot Media, is your hub for >>> all >>> things parallel software development, from weekly thought leadership blogs >>> to >>> news, videos, case studies, tutorials and more. Take a look and join the >>> conversation now. http://goparallel.sourceforge.net/ >>> >>> >>> >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming The Go Parallel Website, >>> sponsored >>> by Intel and developed in partnership with Slashdot Media, is your hub for >>> all >>> things parallel software development, from weekly thought leadership blogs >>> to >>> news, videos, case studies, tutorials and more. Take a look and join the >>> conversation now. http://goparallel.sourceforge.net/ >>> >>> >>> >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming The Go Parallel Website, >>> sponsored >>> by Intel and developed in partnership with Slashdot Media, is your hub for >>> all >>> things parallel software development, from weekly thought leadership blogs >>> to >>> news, videos, case studies, tutorials and more. Take a look and join the >>> conversation now. http://goparallel.sourceforge.net/ >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >> >> > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: WK <wk...@bn...> - 2015-03-20 19:38:59
|
Excellent, Excellent. We are still on 1.6.27. Can we directly upgrade to 2.0.60 or is there a recommended intermediate step. -wk On 3/20/2015 11:40 AM, Davies Liu wrote: > This is great news! > > I had created a git mirror for recent releases to track the changes: > https://github.com/davies/moosefs/commits/master > > On Fri, Mar 20, 2015 at 7:48 AM, Aleksander Wieliczko > <ale...@mo...> wrote: >> Hi. >> Yes change log is available on moosefs.org site >> >> http://www.moosefs.org/changelog.html >> >> Best regards >> Aleksander Wieliczko >> Technical Support Engineer >> MooseFS.com >> >> On 03/20/2015 03:42 PM, Steve Wilson wrote: >> >> Hi, >> >> Is there some form of release notes indicating the features and bug fixes >> included in this release? >> >> Thanks! >> >> Steve >> >> On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: >> >> Dear MooseFS Community, >> >> We are very excited to announce that MooseFS is back on GPL license. >> >> From now on the MooseFS naming convention and licensing changes, so MooseFS >> CE (Community Edition) will now be referred to as MooseFS. >> >> MooseFS 2.0.60 (previously named CE) released today and all upcoming >> releases will be licensed under GPLv2. The change is our response to the >> feedback that we have got from the community after moving to proprietary >> license while introducing version 2.x. >> >> MooseFS PRO name and licensing will stay unchanged. >> >> Version 2.0.60 is the most stable and reliable release of 2.x branch and >> becomes a natural bridge to version 3.x planned to be released later this >> month. >> >> For more informations on installation or update procedures please visit >> https://moosefs.com/download.html >> >> Best Regards, >> MooseFS Team >> >> >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for >> all >> things parallel software development, from weekly thought leadership blogs >> to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> >> >> >> _______________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users >> >> >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for >> all >> things parallel software development, from weekly thought leadership blogs >> to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> >> >> >> _______________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users >> >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for >> all >> things parallel software development, from weekly thought leadership blogs >> to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users >> > > |
|
From: Davies L. <dav...@gm...> - 2015-03-20 18:40:47
|
This is great news! I had created a git mirror for recent releases to track the changes: https://github.com/davies/moosefs/commits/master On Fri, Mar 20, 2015 at 7:48 AM, Aleksander Wieliczko <ale...@mo...> wrote: > Hi. > Yes change log is available on moosefs.org site > > http://www.moosefs.org/changelog.html > > Best regards > Aleksander Wieliczko > Technical Support Engineer > MooseFS.com > > On 03/20/2015 03:42 PM, Steve Wilson wrote: > > Hi, > > Is there some form of release notes indicating the features and bug fixes > included in this release? > > Thanks! > > Steve > > On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: > > Dear MooseFS Community, > > We are very excited to announce that MooseFS is back on GPL license. > > From now on the MooseFS naming convention and licensing changes, so MooseFS > CE (Community Edition) will now be referred to as MooseFS. > > MooseFS 2.0.60 (previously named CE) released today and all upcoming > releases will be licensed under GPLv2. The change is our response to the > feedback that we have got from the community after moving to proprietary > license while introducing version 2.x. > > MooseFS PRO name and licensing will stay unchanged. > > Version 2.0.60 is the most stable and reliable release of 2.x branch and > becomes a natural bridge to version 3.x planned to be released later this > month. > > For more informations on installation or update procedures please visit > https://moosefs.com/download.html > > Best Regards, > MooseFS Team > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > -- - Davies |
|
From: Aleksander W. <ale...@mo...> - 2015-03-20 14:48:24
|
Hi. Yes change log is available on moosefs.org site http://www.moosefs.org/changelog.html Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 03/20/2015 03:42 PM, Steve Wilson wrote: > Hi, > > Is there some form of release notes indicating the features and bug > fixes included in this release? > > Thanks! > > Steve > > On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: >> Dear MooseFS Community, >> >> We are very excited to announce that MooseFS is back on GPL license. >> >> From now on the MooseFS naming convention and licensing changes, so >> MooseFS CE (Community Edition) will now be referred to as MooseFS. >> >> MooseFS 2.0.60 (previously named CE) released today and all upcoming >> releases will be licensed under GPLv2. The change is our response to >> the feedback that we have got from the community after moving to >> proprietary license while introducing version 2.x. >> >> MooseFS PRO name and licensing will stay unchanged. >> >> Version 2.0.60 is the most stable and reliable release of 2.x branch >> and becomes a natural bridge to version 3.x planned to be released >> later this month. >> >> For more informations on installation or update procedures please >> visit https://moosefs.com/download.html >> >> Best Regards, >> MooseFS Team >> >> >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for all >> things parallel software development, from weekly thought leadership blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> >> >> _______________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Steve W. <st...@pu...> - 2015-03-20 14:42:45
|
Hi, Is there some form of release notes indicating the features and bug fixes included in this release? Thanks! Steve On 03/20/2015 10:25 AM, Krzysztof Kielak wrote: > Dear MooseFS Community, > > We are very excited to announce that MooseFS is back on GPL license. > > From now on the MooseFS naming convention and licensing changes, so > MooseFS CE (Community Edition) will now be referred to as MooseFS. > > MooseFS 2.0.60 (previously named CE) released today and all upcoming > releases will be licensed under GPLv2. The change is our response to > the feedback that we have got from the community after moving to > proprietary license while introducing version 2.x. > > MooseFS PRO name and licensing will stay unchanged. > > Version 2.0.60 is the most stable and reliable release of 2.x branch > and becomes a natural bridge to version 3.x planned to be released > later this month. > > For more informations on installation or update procedures please > visit https://moosefs.com/download.html > > Best Regards, > MooseFS Team > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Krzysztof K. <krz...@mo...> - 2015-03-20 14:25:35
|
Dear MooseFS Community, We are very excited to announce that MooseFS is back on GPL license. From now on the MooseFS naming convention and licensing changes, so MooseFS CE (Community Edition) will now be referred to as MooseFS. MooseFS 2.0.60 (previously named CE) released today and all upcoming releases will be licensed under GPLv2. The change is our response to the feedback that we have got from the community after moving to proprietary license while introducing version 2.x. MooseFS PRO name and licensing will stay unchanged. Version 2.0.60 is the most stable and reliable release of 2.x branch and becomes a natural bridge to version 3.x planned to be released later this month. For more informations on installation or update procedures please visit https://moosefs.com/download.html <https://moosefs.com/download.html> Best Regards, MooseFS Team |
|
From: Aleksander W. <ale...@mo...> - 2015-02-25 12:06:01
|
Hi Michael. I think the best solution for your problem is to use MooseFS tool colled mfsfilerepair like this: mfsfilerepair file.name mfsfilerepair repair given file. Use it with caution. It forces file to be readable, so it could erase (fill with zeros) file when chunkservers are not currently connected. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 02/24/2015 02:50 AM, Michael Tinsay wrote: > Hi. > > In the MooseFS (v1.6.26) Info page, under "Important messages", it > contains the following lines (among others): > + currently unavailable reserved file 17020496: KVM/images/SAPHesk.raw.damaged > + currently unavailable reserved file 5394774: KVM/images/BOBJQAS-hda.raw.damaged > + currently unavailable reserved file 4114282: KVM/images/Syslog-vda.raw.damaged > + currently unavailable reserved file 4114283: KVM/images/Tickets.raw.damaged > These files do not exist anymore, except in MFSMETA's reserved folder. > > Is it safe to delete these? I'm fairly certain that no other client > has any of these files opened. > > Upgrading to MooseFS 2.0 is in the pipeline, but not anytime soon. > > > Regards. > > > --- mike t. > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: MooseFS S. <su...@mo...> - 2015-02-24 11:09:16
|
Dobry pomysl ------ Pozdrawiam, Krzysztof Kielak -----Original Message----- From: my...@mo... Date: Tue, 24 Feb 2015 12:01:57 Subject: [Support requests - Support request #146] Fwd: [MooseFS-users] MooseFS reports missing chunks for files which do not exist. Issue #146 has been updated by Piotr Robert Konopelko. Zrobione. A może by tak zasubskrybować e-mail su...@mo... do listy - wtedy maile automatycznie by tu trafiały :) Można też wtedy od razu stąd odpowiadać. I nie trzeba będzie robić żadnych forwardów. ---------------------------------------- Support request #146: Fwd: [MooseFS-users] MooseFS reports missing chunks for files which do not exist. https://my.moosefs.com/issues/146#change-330 * Author: Anonymous * Status: New * Priority: Normalny * Assignee: Piotr Robert Konopelko * Category: * Target version: * Firma: ---------------------------------------- > Begin forwarded message: > > From: Michael Tinsay <mic...@ho...> > To: "moo...@li..." <moo...@li...> > Date: 24 Feb 2015 02:50:55 CET > Subject: [MooseFS-users] MooseFS reports missing chunks for files which do not exist. > > Hi. > > In the MooseFS (v1.6.26) Info page, under "Important messages", it contains the following lines (among others): > + currently unavailable reserved file 17020496: KVM/images/SAPHesk.raw.damaged > + currently unavailable reserved file 5394774: KVM/images/BOBJQAS-hda.raw.damaged > + currently unavailable reserved file 4114282: KVM/images/Syslog-vda.raw.damaged > + currently unavailable reserved file 4114283: KVM/images/Tickets.raw.damaged > These files do not exist anymore, except in MFSMETA's reserved folder. > > Is it safe to delete these? I'm fairly certain that no other client has any of these files opened. > > Upgrading to MooseFS 2.0 is in the pipeline, but not anytime soon. > > > Regards. > > > --- mike t. > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/_______________________________________________ <http://goparallel.sourceforge.net/_______________________________________________> > 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> Best Regards, Krzysztof Kielak Director of Operations and Customer Support Mobile: +48 601 476 440 -- my.moosefs.com |
|
From: Michael T. <mic...@ho...> - 2015-02-24 01:51:01
|
Hi. In the MooseFS (v1.6.26) Info page, under "Important messages", it contains the following lines (among others): + currently unavailable reserved file 17020496: KVM/images/SAPHesk.raw.damaged + currently unavailable reserved file 5394774: KVM/images/BOBJQAS-hda.raw.damaged + currently unavailable reserved file 4114282: KVM/images/Syslog-vda.raw.damaged + currently unavailable reserved file 4114283: KVM/images/Tickets.raw.damagedThese files do not exist anymore, except in MFSMETA's reserved folder. Is it safe to delete these? I'm fairly certain that no other client has any of these files opened. Upgrading to MooseFS 2.0 is in the pipeline, but not anytime soon. Regards. --- mike t. |
|
From: Grzegorz P. <gp...@gm...> - 2015-02-17 08:47:12
|
Yes you understood me correctly. Path after -S parameter is correct. After mounting without specifying share name, mfs_root is being mounted and I can cd into /media/test/mfs/test folder. But still I cant mount shares that are already exported and visible in mfs cgi panel. Any advice on that? Thanks, Grzegorz On Mon, Feb 16, 2015 at 2:35 PM, Aleksander Wieliczko < ale...@mo...> wrote: > Hello Grzegorz > > Nice to hear that you are using MooseFS. > First of all we advice you to update MooseFS to 2.0.50 version. > A lot of improvements have been made till 1.6.x version. > > Please check your path after -S parameter. > If I have understood, you have made entry in export for /mfs/test folder > and you have (mfs_root)/mfs/test folder available on MooseFS and sent HUP > signal. > So if you mounts moosefs without -S parameter (mfsmount -H mfsmaster > /media/test/) you can "cd" to /media/test/mfs/test folder, yes? > > Best regards > Aleksander Wieliczko > Technical Support Engineer > MooseFS.com <http://moosefs.com> > > On 02/16/2015 11:27 AM, Grzegorz Palak wrote: > > hello everyone, > > While using MFS 1.6.27 I've came accross strange situation. > After adding new export and sending HUP to mfsmaster I cannot mount new > exports. > Other already existing exports can be mounted without any problems. > I'm having ~45 exports right now. Last 10 of them were created with the > same procedure[mfmaster HUP > mount] and everything went smoothly. Host > where I'm doing mounting is allowed in mfsexport.cfg and these problematic > exports are visible in master cgi panel. > > root@zerg:/media/# mfsmount /media/test/ -H mfsmaster -S /mfs/test > mfsmaster register error: No such file or directory > > It's the same message when you want to mount share that is not defined > in mfsexports.cfg. > Have anyone came across similar problem? Any advice? > > Thanks. > Grzegorz > > -- > Human knowledge, belongs to the world. > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREEhttp://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk > > > > _______________________________________________ > moosefs-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > -- Human knowledge, belongs to the world. Debian, fanatic user. |
|
From: Aleksander W. <ale...@mo...> - 2015-02-16 13:35:59
|
Hello Grzegorz Nice to hear that you are using MooseFS. First of all we advice you to update MooseFS to 2.0.50 version. A lot of improvements have been made till 1.6.x version. Please check your path after -S parameter. If I have understood, you have made entry in export for /mfs/test folder and you have (mfs_root)/mfs/test folder available on MooseFS and sent HUP signal. So if you mounts moosefs without -S parameter (mfsmount -H mfsmaster /media/test/) you can "cd" to /media/test/mfs/test folder, yes? Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 02/16/2015 11:27 AM, Grzegorz Palak wrote: > hello everyone, > > While using MFS 1.6.27 I've came accross strange situation. > After adding new export and sending HUP to mfsmaster I cannot mount > new exports. > Other already existing exports can be mounted without any problems. > I'm having ~45 exports right now. Last 10 of them were created with > the same procedure[mfmaster HUP > mount] and everything went smoothly. > Host where I'm doing mounting is allowed in mfsexport.cfg and these > problematic exports are visible in master cgi panel. > > root@zerg:/media/# mfsmount /media/test/ -H mfsmaster -S /mfs/test > mfsmaster register error: No such file or directory > > It's the same message when you want to mount share that is not defined > in mfsexports.cfg. > Have anyone came across similar problem? Any advice? > > Thanks. > Grzegorz > > -- > Human knowledge, belongs to the world. > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Grzegorz P. <gp...@gm...> - 2015-02-16 10:27:30
|
hello everyone, While using MFS 1.6.27 I've came accross strange situation. After adding new export and sending HUP to mfsmaster I cannot mount new exports. Other already existing exports can be mounted without any problems. I'm having ~45 exports right now. Last 10 of them were created with the same procedure[mfmaster HUP > mount] and everything went smoothly. Host where I'm doing mounting is allowed in mfsexport.cfg and these problematic exports are visible in master cgi panel. root@zerg:/media/# mfsmount /media/test/ -H mfsmaster -S /mfs/test mfsmaster register error: No such file or directory It's the same message when you want to mount share that is not defined in mfsexports.cfg. Have anyone came across similar problem? Any advice? Thanks. Grzegorz -- Human knowledge, belongs to the world. |
|
From: Aleksander W. <ale...@mo...> - 2015-02-06 14:18:12
|
Hi. About main loop you can find some informations on our MooseFS web site in MooseFS User's Manual at this address: http://moosefs.com/documentation.html Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 02/06/2015 01:12 PM, Eugene Diatlov wrote: > Hi, > > No, it is not a trashtime. bcs I have trashtime = 0. > And it is not replications, bcs after some time I see that replication > graph become to 0. > I think it is moosefs loop checks. Where I can read details about how it > works? > > > 06.02.2015 13:50, moo...@li... пишет: >> Hi >> It's look like you have some files in trash. >> Default trash time value is 7 days, after this period files will start >> deleting automatically from trash. >> All deletions in trash changing free space in MooseFS and this causing >> other algorithms to run. >> Mainly replication algorithms working in background to care about equal >> alignment of chunks on all chunkserver. >> >> Please check on MooseFS cgi webpage "Trash space" on "Info" tab |
|
From: Eugene D. <it...@da...> - 2015-02-06 12:12:19
|
Hi, No, it is not a trashtime. bcs I have trashtime = 0. And it is not replications, bcs after some time I see that replication graph become to 0. I think it is moosefs loop checks. Where I can read details about how it works? 06.02.2015 13:50, moo...@li... пишет: > Hi > It's look like you have some files in trash. > Default trash time value is 7 days, after this period files will start > deleting automatically from trash. > All deletions in trash changing free space in MooseFS and this causing > other algorithms to run. > Mainly replication algorithms working in background to care about equal > alignment of chunks on all chunkserver. > > Please check on MooseFS cgi webpage "Trash space" on "Info" tab -- Best regards, Head of R&D department Eugene Diatlov DataLink LLC email: it...@da... web: http://datalink.ua |
|
From: Piotr R. K. <pio...@mo...> - 2015-02-06 11:50:17
|
Hello, I checked and there is two things you need to know: when you write data to MooseFS, the data is divided to chunks (64MiB each) - I think you probably know this already. When you write data, MooseFS Master Server does not know if the chunk it want to create will contain 64 MiB of data or it will contain less. So MooseFS Master Server assume, that it will be 64 MiB chunk and at this moment your example *hard* quota (~9.5MiB) is already exceeded. To write even less than 64 MiB, your *hard* quota must be at least 65MiB (because the chunk uses really 64 MiB of data + 5KiB header). Of course when you write 1MiB file, your real used space is 1MiB + 5KiB header. So e.g. if you have 66 MiB hard quota, you will be able to write 1MiB file and then 64 MiB file. Please try to set bigger quota values, so your test will be more accurate. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] Hi, we are happy that you are using MooseFS! Can you provide us output of the following commands?: * mfsdirinfo /data/mfsdata/test * mfsgetgoal -r /data/mfsdata/test So we can analyze your issue? -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| _moosefs.com_ hi,i install moosefs-ce-master-2.0.48 in centos7,and it work better.But i have a issue about mfssetquota in mfs client,i use this tools like this， 13:24:30 # mfsgetquota /data/mfsdata/test /data/mfsdata/test: (current values | soft quota | hard quota) inodes | 6 | 10000000 | 10000000 | length | 0 | 10000000 | 10000000 | size | 0 | 10000000 | 10000000 | realsize | 0 | 10000000 | 10000000 | then i add a 2M file 13:23:16 # dd if=/dev/zero of=test.img bs=1M count=2 dd: writing `test.img': Disk quota exceeded dd: closing output file `test.img': Disk quota exceeded it have a issue,pls help me,tks! -------- [1] http://moosefs.com |
|
From: Aleksander W. <ale...@mo...> - 2015-02-06 11:37:01
|
Hi It's look like you have some files in trash. Default trash time value is 7 days, after this period files will start deleting automatically from trash. All deletions in trash changing free space in MooseFS and this causing other algorithms to run. Mainly replication algorithms working in background to care about equal alignment of chunks on all chunkserver. Please check on MooseFS cgi webpage "Trash space" on "Info" tab Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 02/06/2015 07:29 AM, Eugene Diatlov wrote: > Hi everyone, > > Have some strange things on moosefs 2.0.48, CE. > I have 1369414 chunks, goal is 1. At the same time I have around 50-80 > chunks with goal 1 in state pending deletions. > Pending deletion chunks counter are changing every seconds. It is > strange, bcs nobody do not makeing any changes to moose filesystem. > > For the last night no new files, no deletions (as well as no > modifications), but free space is changed for a few percents, metadata > version changed, etc. > And pending deletions counter is still around 60. Could you give more > information about foreground processes in moosefs? > |
|
From: Piotr R. K. <pio...@mo...> - 2015-02-06 10:45:23
|
Hi,
we are happy that you are using MooseFS!
Can you provide us output of the following commands?:
* mfsdirinfo /data/mfsdata/test
* mfsgetgoal -r /data/mfsdata/test
So we can analyze your issue?
--
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer *| moosefs.com[1]
hi,i install moosefs-ce-master-2.0.48 in centos7,and it work better.But i have a issue
about mfssetquota in mfs client,i use this tools like this，
13:24:30 # mfsgetquota /data/mfsdata/test
/data/mfsdata/test: (current values | soft quota | hard quota)
inodes | 6 | 10000000 | 10000000 |
length | 0 | 10000000 | 10000000 |
size | 0 | 10000000 | 10000000 |
realsize | 0 | 10000000 | 10000000 |
then i add a 2M file
13:23:16 # dd if=/dev/zero of=test.img bs=1M count=2
dd: writing `test.img': Disk quota exceeded
dd: closing output file `test.img': Disk quota exceeded
it have a issue,pls help me,tks!
--------
[1] http://moosefs.com
|
|
From: Eugene D. <it...@da...> - 2015-02-06 06:29:51
|
Hi everyone, Have some strange things on moosefs 2.0.48, CE. I have 1369414 chunks, goal is 1. At the same time I have around 50-80 chunks with goal 1 in state pending deletions. Pending deletion chunks counter are changing every seconds. It is strange, bcs nobody do not makeing any changes to moose filesystem. For the last night no new files, no deletions (as well as no modifications), but free space is changed for a few percents, metadata version changed, etc. And pending deletions counter is still around 60. Could you give more information about foreground processes in moosefs? -- Best regards, Head of R&D department Eugene Diatlov DataLink LLC email: it...@da... web: http://datalink.ua |
|
From: 邓磊 <dl5...@gm...> - 2015-02-06 05:53:37
|
hi,i install moosefs-ce-master-2.0.48 in centos7,and it work better.But i have a issue about mfssetquota in mfs client,i use this tools like this， 13:24:30 # mfsgetquota /data/mfsdata/test /data/mfsdata/test: (current values | soft quota | hard quota) inodes | 6 | 10000000 | 10000000 | length | 0 | 10000000 | 10000000 | size | 0 | 10000000 | 10000000 | realsize | 0 | 10000000 | 10000000 | then i add a 2M file 13:23:16 # dd if=/dev/zero of=test.img bs=1M count=2 dd: writing `test.img': Disk quota exceeded dd: closing output file `test.img': Disk quota exceeded it have a issue,pls help me,tks! |
|
From: Steve W. <st...@pu...> - 2015-01-28 17:00:15
|
Hi, Oops... it turns out that this is a false alarm! I found a typo in my hosts file which was the source of this problem. After correcting the typo, I'm able to successfully mount using the -B (mfsbind) option as before. Thanks for your replies and sorry for the false alarm. Kind regards, Steve On 01/28/2015 11:05 AM, Krzysztof Kielak wrote: > Steve, > > We’ll look into your case in more details first thing in the morning > (CET time) tomorrow and we’ll fix it, if it’s broken on our side. > > When it comes to binding on a client side, I can quote Richard Stevens > from book “UNIX Network Programming: The Sockets Networking API” that > says: > > /“Normally, a TCP client does not bind an IP address to its socket. > The kernel chooses the source IP address when the socket is connected, > based on the outgoing interface that is used, which in turn is based > on the route required to reach the server”/ > > From the above you should be fine without binding, but of course - as > I mentioned earlier - we’ll check CentOS 7 here and we’ll keep you posted. > > Best Regards, > Krzysztof Kielak > *Director of Operations and Customer Support* > Mobile: +48 601 476 440 > > > >> On 28 Jan 2015, at 16:09, Steve Wilson <st...@pu... >> <mailto:st...@pu...>> wrote: >> >> I have a generic script that is used for mounting MooseFS filesystems >> on my workstations. Some of the workstations have multiple IP >> addresses, including those workstations that also double as a MooseFS >> master server. These will have a master server IP address along with >> their normal IP address that can easily be moved to another >> workstation (i.e., the metalogger server) when I want that >> workstation to become the master server. >> >> So the script I use supplies the default hostname (as given by >> /bin/hostname) to the -B option of mfsmount. And, like I mentioned >> earlier, this has been working quite successfully for several years >> up until this installation of CentOS 7. >> >> I did find that using the IP address instead of the hostname does >> work correctly so I'll probably change my scripts to use an IP address: >>> [root@sbmonitor mnt]# mfsmount /mnt/mfs -B10.145.7.33 >>> -Hsb-data.bio.purdue.edu <http://Hsb-data.bio.purdue.edu> -S/cosit >>> mfsmaster accepted connection with parameters: >>> read-write,restricted_ip ; root mapped to root:root >> >> Thanks, >> Steve >> >> On 01/28/2015 09:32 AM, Aleksander Wieliczko wrote: >>> Hi >>> What is the reason that you want to use different IP address for >>> client binding, than your default NIC ip? >>> >>> -B IP option is the same as -o mfsbind=IP ---define source ip >>> address for connections (default: NOT DEFINED - chosen automatically >>> by OS) >>> >>> Best regards >>> Aleksander Wieliczko >>> Technical Support Engineer >>> MooseFS.com <x-msg://26/moosefs.com> >>> >>> On 01/28/2015 03:08 PM, Steve Wilson wrote: >>>> Hi, >>>> >>>> When using the -B option to mfsmount after upgrading to CentOS 7, I get >>>> the following error: >>>>> [root@sbmonitor mnt]# mfsmount /mnt/mfs -Bsbmonitor.bio.purdue.edu <http://Bsbmonitor.bio.purdue.edu> >>>>> -Hsb-data.bio.purdue.edu <http://Hsb-data.bio.purdue.edu> -S/cosit >>>>> can't bind socket to given ip ("10.147.7.33") >>>> This same command works on CentOS 6, RHEL 6, Ubuntu 12.04, and Ubuntu >>>> 14.04 but doesn't work on CentOS 7. This is my first CentOS 7 >>>> installation so I'm still learning its subtle and not-so-subtle >>>> differences. I'm not sure if this is a problem with my CentOS 7 >>>> configuration or a MooseFS problem. >>>> >>>> If I attempt to perform the mount without the -B option, it works fine: >>>>> [root@sbmonitor mnt]# mfsmount /mnt/mfs -Bsbmonitor.bio.purdue.edu <http://Bsbmonitor.bio.purdue.edu> >>>>> -Hsb-data.bio.purdue.edu <http://Hsb-data.bio.purdue.edu> -S/cosit >>>>> can't bind socket to given ip ("10.147.7.33") >>>> Any ideas what the problem could be? Can anyone reproduce this on >>>> another CentOS 7 or RHEL 7 installation? >>>> >>>> Thanks! >>>> >>>> Steve >>>> >>>> ------------------------------------------------------------------------------ >>>> Dive into the World of Parallel Programming. The Go Parallel Website, >>>> sponsored by Intel and developed in partnership with Slashdot Media, is your >>>> hub for all things parallel software development, from weekly thought >>>> leadership blogs to news, videos, case studies, tutorials and more. Take a >>>> look and join the conversation now.http://goparallel.sourceforge.net/ >>>> _______________________________________________ >>>> moosefs-users mailing list >>>> moo...@li... >>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming. The Go Parallel Website, >> sponsored by Intel and developed in partnership with Slashdot Media, >> is your >> hub for all things parallel software development, from weekly thought >> leadership blogs to news, videos, case studies, tutorials and more. >> Take a >> look and join the conversation now. >> http://goparallel.sourceforge.net/_______________________________________________ >> moosefs-users mailing list >> moo...@li... >> <mailto:moo...@li...> >> https://lists.sourceforge.net/lists/listinfo/moosefs-users > |
84 messages has been excluded from this view by a project administrator.
