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-01-28 16:05:59
|
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...> 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 -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 >>>> -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 >>>> -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/ <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> >> > > ------------------------------------------------------------------------------ > 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-01-28 15:09:45
|
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 -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 <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 >>> -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 >>> -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 > |
|
From: Steve W. <st...@pu...> - 2015-01-28 14:49:05
|
Somewhat implied from the following at http://moosefs.com/download/centosfedorarhel.html... > > Next you need to add the repository entry: > > * For sysv os family - CentOS 6: > # curl "http://ppa.moosefs.com/MooseFS-stable-rhsysv.repo" > > /etc/yum.repos.d/MooseFS.repo > * For systemd os family - CentOS 7: > # curl "http://ppa.moosefs.com/MooseFS-stable-rhsystemd.repo" > > /etc/yum.repos.d/MooseFS.repo > > On 01/28/2015 09:14 AM, Tobias Honacker wrote: > I cant see any documented support for CentOS7 at the moment. > > -> http://moosefs.com/download/install.html |
|
From: Aleksander W. <ale...@mo...> - 2015-01-28 14:33:03
|
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 <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 >> -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 >> -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 |
|
From: Tobias H. <t.h...@go...> - 2015-01-28 14:14:24
|
I cant see any documented support for CentOS7 at the moment. -> http://moosefs.com/download/install.html |
|
From: Steve W. <st...@pu...> - 2015-01-28 14:09:08
|
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 > -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 > -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 |
|
From: 浅. <xuh...@vi...> - 2015-01-27 03:23:00
|
Dear mfs engineers, I have some problems when using mfs. Details are below. AS I have deployed a monitoring shell to detect if mfs-mount thread is alive.,this moring I recieved an alarm.When I checked out system logs, I got those messages: mfsmount[31059]: master: register error (read header: Connection timed out) mfsmount[31059]: master: tcp recv error: Connection timed out (1) mfsmount[31059]: file: 40847619, index: 0, chunk: 74472590, version: 1 - writeworker: connection with (0AF0390E:9432) was timed out (unfinished writes: 2; try counter: 1) Can you explain to me what these messages mean? And I guess that it may be concerned with the system load of the machine in where mfs master is deployed. And here are some charts. Your Sincerely Huan Xu |
|
From: Joseph L. <jo...@ge...> - 2015-01-26 15:15:41
|
Great, thanks. -Joe > On Jan 26, 2015, at 9:14 AM, Aleksander Wieliczko <ale...@mo...> wrote: > > Hallo! > > No we still building packages for FreeBSD. > I think we have little error in our ppa package creating script - it's not placing FreeBSD packages in the right place. > > Tomorrow we will place all packages for FreeBSD. > Sorry for all this problems. > > Best regards > Aleksander Wieliczko > Technical Support Engineer > MooseFS.com <x-msg://128/moosefs.com> > > On 01/26/2015 03:38 PM, Joseph Love wrote: >> Hi, >> >> It seems like the FreeBSD folder on ppa.moosefs.com <http://ppa.moosefs.com/> is devoid of files. Is a FreeBSD build still being continued? >> >> -Joe >> >> >> >> >> >> ------------------------------------------------------------------------------ >> 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> > > ------------------------------------------------------------------------------ > 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: Aleksander W. <ale...@mo...> - 2015-01-26 15:14:27
|
Hallo! No we still building packages for FreeBSD. I think we have little error in our ppa package creating script - it's not placing FreeBSD packages in the right place. Tomorrow we will place all packages for FreeBSD. Sorry for all this problems. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 01/26/2015 03:38 PM, Joseph Love wrote: > Hi, > > It seems like the FreeBSD folder on ppa.moosefs.com > <http://ppa.moosefs.com> is devoid of files. Is a FreeBSD build still > being continued? > > -Joe > > > > > > ------------------------------------------------------------------------------ > 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: Joseph L. <jo...@ge...> - 2015-01-26 14:57:57
|
Hi, It seems like the FreeBSD folder on ppa.moosefs.com <http://ppa.moosefs.com/> is devoid of files. Is a FreeBSD build still being continued? -Joe |
|
From: Eugene D. <it...@da...> - 2015-01-26 10:17:27
|
Dear Piotr, I have small files, so 1 chunk is equal to 1 file. This means that I also miss a file in this case. Currently using 2.0.43, but will update today. 26.01.2015 12:05, Piotr Robert Konopelko пишет: > > Hello Eugene, > > > 1) What maintenance mode does? What should happen when I switch it > on or off? > > It is described in "MooseFS User's Manual" - chapter 4.3. You can > obtain it at http://moosefs.com/documentation.html. > > > 2) Is there any way to force filesystem checks? > > What do you mean exactly? The "filesystem check" loop is going all the > time. When it ends, info is shown on CGI monitor and it starts over. > > > 3) chunk is unavailable error. sometimes, after fs check I receive a > > > message, that the chunk is unavailable. > > If you have missing chunk(s) in "All chunks state matrix", information > about specific chunks/files missing is shown after filesystem check > loop ends. > > > currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0) > > > > > > I checked in fs structure and the chuck is really missed. > > > How this could happen usually? If the file was written successfully, > why it is missed now? > > Do you have only unavailable chunk, or also file? > > > Using latest stable CE edition. Linux, HDD fs is ext4. > > Which version exactly? On Thursday, 22nd January 2015 we released > MooseFS 2.0.48 as stable, please upgrade to 2.0.48. > > Since 2.0.43 there were some fixes which may be important in you case > (specifically regarding to missing chunks and no unavailable files). > > Can you send us some logs from master and this chunkserver, on which > you have missing chunk from period you were writing files and the > problem occured? > > -- > > Best regards, > > Piotr Robert Konopelko > > MooseFS Technical Support Engineer | moosefs.com <http://moosefs.com> > > On Sunday, January 25, 2015 12:10:11 PM Eugene Diatlov wrote: > > > Hi everyone, > > > > > > 1) What maintenance mode does? What should happen when I switch it > on or > > > off? > > > > > > 2) Is there any way to force filesystem checks? > > > > > > 3) chunk is unavailable error. sometimes, after fs check I receive a > > > message, that the chunk is unavailable. > > > > > > currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0) > > > > > > I checked in fs structure and the chuck is really missed. > > > How this could happen usually? If the file was written successfully, > why it is missed now? > > > > > > Using latest stable CE edition. Linux, HDD fs is ext4. > > > > > > > -- 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-01-26 10:05:32
|
Hello Eugene, > 1) What maintenance mode does? What should happen when I switch it on or off? It is described in "MooseFS User's Manual" - chapter 4.3. You can obtain it at http://moosefs.com/documentation.html[1]. > 2) Is there any way to force filesystem checks? What do you mean exactly? The "filesystem check" loop is going all the time. When it ends, info is shown on CGI monitor and it starts over. > 3) chunk is unavailable error. sometimes, after fs check I receive a > message, that the chunk is unavailable. If you have missing chunk(s) in "All chunks state matrix", information about specific chunks/files missing is shown after filesystem check loop ends. > currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0) > > I checked in fs structure and the chuck is really missed. > How this could happen usually? If the file was written successfully, why it is missed now? Do you have only unavailable chunk, or also *file*? > Using latest stable CE edition. Linux, HDD fs is ext4. Which version exactly? On Thursday, 22nd January 2015 we released MooseFS 2.0.48 as stable, please upgrade to 2.0.48. Since 2.0.43 there were some fixes which may be important in you case (specifically regarding to missing chunks and *no unavailable files*). Can you send us some logs from master and this chunkserver, on which you have missing chunk from period you were writing files and the problem occured? -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[2] On Sunday, January 25, 2015 12:10:11 PM Eugene Diatlov wrote: > Hi everyone, > > 1) What maintenance mode does? What should happen when I switch it on or > off? > > 2) Is there any way to force filesystem checks? > > 3) chunk is unavailable error. sometimes, after fs check I receive a > message, that the chunk is unavailable. > > currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0) > > I checked in fs structure and the chuck is really missed. > How this could happen usually? If the file was written successfully, why it is missed now? > > Using latest stable CE edition. Linux, HDD fs is ext4. > > -------- [1] http://moosefs.com/documentation.html [2] http://moosefs.com |
|
From: Eugene D. <it...@da...> - 2015-01-25 10:26:20
|
Hi everyone, 1) What maintenance mode does? What should happen when I switch it on or off? 2) Is there any way to force filesystem checks? 3) chunk is unavailable error. sometimes, after fs check I receive a message, that the chunk is unavailable. currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0) I checked in fs structure and the chuck is really missed. How this could happen usually? If the file was written successfully, why it is missed now? Using latest stable CE edition. Linux, HDD fs is ext4. -- 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-01-23 15:19:00
|
You are welcome :) I understand. If you will have any other questions, don't hesitate to contact me. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] OK Thank you . I will do that in the future. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上10:38 *收件人:* "张海"<183...@qq...>; *抄送:* "moosefs-users"<moo...@li...>; "contact"<co...@mo...>; "MooseFS Technical Support Depar"<dw...@mo...>; *主题:* Re: 回复： 回复： [MooseFS-users] what is the client number that the moosefs can support? Hello again, all versions from 1.6.x branch are no longer supported. Upgrading MooseFS is a *safe* operation, because your data is not even touched. *The most important thing* during the upgrade is to make it even more safer: Your *metadata* is stored on master server. When you stop the master server, it dumps the metadata from RAM to file named *metadata.mfs* So the most important thing is to *make a backup* of this file. We upgraded a lot of instances, even 1.0 PiB and bigger and *every time* upgrade was successful, so you don't need to be afraid. Please read carefully this document: http://moosefs.com/Content/Downloads/moosefs-upgrade.pdf[2] and if you will have any questions after reading this guide, please ask me :) We *really* recommend upgrading MooseFS. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] Yes I know 1.6.15 is old.But my data is vesy big and very important. I'm afriad to lose my data for upgrading the MooseFs. Now please tell me how to solve my problem without upgrading the MooseFs. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上9:53 *收件人:* "moosefs-users"<moo...@li...>; *抄送:* "张海"<183...@qq...>; "MooseFS Contact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; *主题:* Re: 回复： [MooseFS-users] what is the client number that the moosefs can support? Hello, 1.6.15 is a *very* old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: *Your version* -> *1.6.27-5* ->* 2.0.x CE*, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in *MooseFS Upgrade Guide* (you can download it from the URL below), so please refer to this document. I also very recommend reading *MooseFS 2.0 Step-by-Step Installation Guide*. You can obtain documentation at http://moosefs.com/documentation.html[3]. Also, at http://get.moosefs.com[4] you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo...[5] or mailing list at moo...@li...[6]. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上7:00 *收件人:* "moosefs-users"<moo...@li...>; *抄送:* "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; *主题:* Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| _moosefs.com_ hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! -------- [1] http://moosefs.com [2] http://moosefs.com/Content/Downloads/moosefs-upgrade.pdf [3] http://moosefs.com/documentation.html [4] http://get.moosefs.com [5] mailto:dw...@mo... [6] mailto:moo...@li... |
|
From: 张海 <183...@qq...> - 2015-01-23 14:47:05
|
OK Thank you . I will do that in the future. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上10:38 收件人: "张海"<183...@qq...>; 抄送: "moosefs-users"<moo...@li...>; "contact"<co...@mo...>; "MooseFS Technical Support Depar"<dw...@mo...>; 主题: Re: 回复： 回复： [MooseFS-users] what is the client number that the moosefs can support? Hello again, all versions from 1.6.x branch are no longer supported. Upgrading MooseFS is a safe operation, because your data is not even touched. The most important thing during the upgrade is to make it even more safer: Your metadata is stored on master server. When you stop the master server, it dumps the metadata from RAM to file named metadata.mfs So the most important thing is to make a backup of this file. We upgraded a lot of instances, even 1.0 PiB and bigger and every time upgrade was successful, so you don't need to be afraid. Please read carefully this document: http://moosefs.com/Content/Downloads/moosefs-upgrade.pdf and if you will have any questions after reading this guide, please ask me :) We really recommend upgrading MooseFS. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 10:02:59 PM 张海 wrote: Yes I know 1.6.15 is old.But my data is vesy big and very important. I'm afriad to lose my data for upgrading the MooseFs. Now please tell me how to solve my problem without upgrading the MooseFs. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上9:53 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFS Contact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: 回复： [MooseFS-users] what is the client number that the moosefs can support? Hello, 1.6.15 is a very old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: Your version -> 1.6.27-5 -> 2.0.x CE, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in MooseFS Upgrade Guide (you can download it from the URL below), so please refer to this document. I also very recommend reading MooseFS 2.0 Step-by-Step Installation Guide. You can obtain documentation at http://moosefs.com/documentation.html. Also, at http://get.moosefs.com you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo... or mailing list at moo...@li.... -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 9:38:07 PM 张海 wrote: hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上7:00 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 11:45:02 AM 张海 wrote: hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! |
|
From: Piotr R. K. <pio...@mo...> - 2015-01-23 14:39:11
|
Hello again, all versions from 1.6.x branch are no longer supported. Upgrading MooseFS is a *safe* operation, because your data is not even touched. *The most important thing* during the upgrade is to make it even more safer: Your *metadata* is stored on master server. When you stop the master server, it dumps the metadata from RAM to file named *metadata.mfs* So the most important thing is to *make a backup* of this file. We upgraded a lot of instances, even 1.0 PiB and bigger and *every time* upgrade was successful, so you don't need to be afraid. Please read carefully this document: http://moosefs.com/Content/Downloads/moosefs-upgrade.pdf[1] and if you will have any questions after reading this guide, please ask me :) We *really* recommend upgrading MooseFS. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[2] Yes I know 1.6.15 is old.But my data is vesy big and very important. I'm afriad to lose my data for upgrading the MooseFs. Now please tell me how to solve my problem without upgrading the MooseFs. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上9:53 *收件人:* "moosefs-users"<moo...@li...>; *抄送:* "张海"<183...@qq...>; "MooseFS Contact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; *主题:* Re: 回复： [MooseFS-users] what is the client number that the moosefs can support? Hello, 1.6.15 is a *very* old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: *Your version* -> *1.6.27-5* ->* 2.0.x CE*, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in *MooseFS Upgrade Guide* (you can download it from the URL below), so please refer to this document. I also very recommend reading *MooseFS 2.0 Step-by-Step Installation Guide*. You can obtain documentation at http://moosefs.com/documentation.html[3]. Also, at http://get.moosefs.com[4] you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo...[5] or mailing list at moo...@li...[6]. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[2] hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上7:00 *收件人:* "moosefs-users"<moo...@li...>; *抄送:* "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; *主题:* Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| _moosefs.com_ hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! -------- [1] http://moosefs.com/Content/Downloads/moosefs-upgrade.pdf [2] http://moosefs.com [3] http://moosefs.com/documentation.html [4] http://get.moosefs.com [5] mailto:dw...@mo... [6] mailto:moo...@li... |
|
From: 张海 <183...@qq...> - 2015-01-23 14:09:51
|
ok I know.Thank you. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上10:03 收件人: "moosefs-users"<moo...@li...>; 抄送: "MooseFS Contact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; "张海"<183...@qq...>; 主题: Re: [MooseFS-users] 回复： what is the client number that the moosefs can support? I would like to mention, that in MooseFS 2.0.x problems with "closed by peer" connections of course have been solved. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 2:53:48 PM Piotr Robert Konopelko wrote: Hello, 1.6.15 is a very old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: Your version -> 1.6.27-5 -> 2.0.x CE, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in MooseFS Upgrade Guide (you can download it from the URL below), so please refer to this document. I also very recommend reading MooseFS 2.0 Step-by-Step Installation Guide. You can obtain documentation at http://moosefs.com/documentation.html. Also, at http://get.moosefs.com you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo... or mailing list at moo...@li.... -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 9:38:07 PM 张海 wrote: hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上7:00 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 11:45:02 AM 张海 wrote: hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! |
|
From: 张海 <183...@qq...> - 2015-01-23 14:03:17
|
Yes I know 1.6.15 is old.But my data is vesy big and very important. I'm afriad to lose my data for upgrading the MooseFs. Now please tell me how to solve my problem without upgrading the MooseFs. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上9:53 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFS Contact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: 回复： [MooseFS-users] what is the client number that the moosefs can support? Hello, 1.6.15 is a very old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: Your version -> 1.6.27-5 -> 2.0.x CE, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in MooseFS Upgrade Guide (you can download it from the URL below), so please refer to this document. I also very recommend reading MooseFS 2.0 Step-by-Step Installation Guide. You can obtain documentation at http://moosefs.com/documentation.html. Also, at http://get.moosefs.com you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo... or mailing list at moo...@li.... -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 9:38:07 PM 张海 wrote: hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上7:00 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 11:45:02 AM 张海 wrote: hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! |
|
From: Piotr R. K. <pio...@mo...> - 2015-01-23 14:03:17
|
I would like to mention, that in MooseFS 2.0.x problems with "closed by peer" connections of course have been solved. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] Hello, 1.6.15 is a *very* old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: *Your version* -> *1.6.27-5* ->* 2.0.x CE*, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in *MooseFS Upgrade Guide* (you can download it from the URL below), so please refer to this document. I also very recommend reading *MooseFS 2.0 Step-by-Step Installation Guide*. You can obtain documentation at http://moosefs.com/documentation.html[2]. Also, at http://get.moosefs.com[3] you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo...[4] or mailing list at moo...@li...[5]. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上7:00 *收件人:* "moosefs-users"<moo...@li...>; *抄送:* "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; *主题:* Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| _moosefs.com_ hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! -------- [1] http://moosefs.com [2] http://moosefs.com/documentation.html [3] http://get.moosefs.com [4] mailto:dw...@mo... [5] mailto:moo...@li... |
|
From: Piotr R. K. <pio...@mo...> - 2015-01-23 13:54:03
|
Hello, 1.6.15 is a *very* old and not supported version of MooseFS. I recommend upgrade your whole instance to the MooseFS 2.0.48 CE, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: *Your version* -> *1.6.27-5* ->* 2.0.x CE*, so first of all you need to upgrade to 1.6.27-5 and then to 2.0.48 CE. Please remember to back up your metadata, changelogs and configuration files before starting an upgrade. The whole upgrade process is described in *MooseFS Upgrade Guide* (you can download it from the URL below), so please refer to this document. I also very recommend reading *MooseFS 2.0 Step-by-Step Installation Guide*. You can obtain documentation at http://moosefs.com/documentation.html[1]. Also, at http://get.moosefs.com[2] you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo...[3] or mailing list at moo...@li...[4]. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[5] hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ *发件人:* "Piotr Robert Konopelko";<pio...@mo...>; *发送时间:* 2015年1月23日(星期五) 晚上7:00 *收件人:* "moosefs-users"<moo...@li...>; *抄送:* "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; *主题:* Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| _moosefs.com_ hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! -------- [1] http://moosefs.com/documentation.html [2] http://get.moosefs.com [3] mailto:dw...@mo... [4] mailto:moo...@li... [5] http://moosefs.com |
|
From: 张海 <183...@qq...> - 2015-01-23 13:38:24
|
hello Piotr Robert Konopelko Thanks very much for your reply. Now I’m useing the version 1.6.15. The linux syslog reports that "mfsmaster mfsmaster[13031]: connection with client(ip:192.168.101.79) has been closed by peer" many times one day . Could you tell me why and what I can do to solve this problem? Best regards, thanks. ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上7:00 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 11:45:02 AM 张海 wrote: hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! |
|
From: 张海 <183...@qq...> - 2015-01-23 13:30:36
|
hi Thanks very much for your reply. Now I’m useing the ------------------ 原始邮件 ------------------ 发件人: "Piotr Robert Konopelko";<pio...@mo...>; 发送时间: 2015年1月23日(星期五) 晚上7:00 收件人: "moosefs-users"<moo...@li...>; 抄送: "张海"<183...@qq...>; "MooseFSContact"<co...@mo...>; "MooseFS Technical Support Department"<dw...@mo...>; 主题: Re: [MooseFS-users] what is the client number that the moosefs can support? Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com On Friday, January 23, 2015 11:45:02 AM 张海 wrote: hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! |
|
From: Piotr R. K. <pio...@mo...> - 2015-01-23 11:00:54
|
Hello Stephen, we are very happy that you are using MooseFS :) MooseFS doesn't have hard-coded client number limits. We have installations with about 300 clients (mounts) working and probably handling more than 300 mounts is not a problem at all for MooseFS :) If you have any other questions, please don't hesitate to contact us. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! -------- [1] http://moosefs.com |
|
From: 张海 <183...@qq...> - 2015-01-23 03:45:20
|
hi the moosefs team I am stephen. I am from china. Now I want to know what is the client number that the moosefs can support? please tell me ,tinaks! |
|
From: Piotr R. K. <pio...@mo...> - 2015-01-21 13:38:36
|
Dear Chenr, I would like to mention, that in MooseFS 2.0.x problems with "closed by peer" connections of course have been solved. Please remember to backup your metadata, changelogs and configuration before doing an upgrade. We very recommend upgrading MooseFS to 2.0.48 CE. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] Dear Chenr, We are very happy that you're using MooseFS :) 1.6.25 is a very old and not supported version of MooseFS. You should *immediately* upgrade your whole instance to the *MooseFS 2.0.48 CE*, because in 2.0.x branch a lot of improvements and bug fixes has been made. Please keep in mind, that supported way to upgrade your instance is: Your version -> *1.6.27-5* -> 2.0.x CE, so you firstly need to upgrade to 1.6.27-5 and then to 2.0.48 CE. The whole upgrade process is described in MooseFS Upgrade Guide[2], so please refer to this document. I also very recommend reading MooseFS 2.0 Step-by-Step Installation Guide[3]. Also, at http://get.moosefs.com[4] you can find useful information about installing MooseFS from packages, so now you don't need to compile MooseFS yourself (but you still can if you want, because sources of MooseFS 2.0.x CE are available). In case of any questions, please don't hesitate to contact our Technical Support Department at dw...@mo...[5]. -- Best regards, Piotr Robert Konopelko *MooseFS Technical Support Engineer *| moosefs.com[1] Dear moosefs-Developers : I am a moosefs-user, our moosefs version is 1.6.25 ,stored 71347651 chunks, and have one mfsmaster server,one mfsmetalogger server,thirty-one chunkservers and mfsclients(mfschunkserver and mfsclient installed on the same server). I meet a thorny problem : all servers attached to the same switch , the network connection between the server properly ,the network in stable condition, but all mfschunkservers ,mfsclients and mfsmetalogger servers disconnected the mfsmaster on the same time, the mfsmasterserver's log is as follows figure: I can not find the cause of the problem , so restart the mfsmaster , then everything back to normal .This happens several times, after restart mfsmaster ,all services back to normal. Can solve this problem by upgrade version to 1.6.27-5 ? Is the version 1.6.27-5 stable? Which version should i upgrade? Sincerely request your assistance,please give me help ,thank you very much . Best regards! -------------------- *陈嵘* 网宿科技股份有限公司 厦门分公司 CDN运营中心 mobile:18965810348 E-mail:ch...@ch...[6] http://www.chinanetcenter.com[7] 分公司：北京-上海-广州-深圳 咨询电话：800-820-0001 卓越的互联网业务平台提供商 -------------------- -------- [1] http://moosefs.com [2] http://pro.hit.gemius.pl/hitredir/id=p4M1jTM4nRhU008M3Fe_sOUC3wjpXEbik3RJMrUmhjn.l7/et=1/extra=moosefsManual%3DupgradeGuide/url=http://moosefs.com/Content/Downloads/moosefs-upgrade.pdf [3] http://pro.hit.gemius.pl/hitredir/id=p4M1jTM4nRhU008M3Fe_sOUC3wjpXEbik3RJMrUmhjn.l7/et=1/extra=moosefsManual%3DstepByStep/url=http://moosefs.com/Content/Downloads/moosefs-installation.pdf [4] http://get.moosefs.com [5] mailto:dw...@mo... [6] mailto:ch...@ch... [7] http://www.chinanetcenter.com/ |
84 messages has been excluded from this view by a project administrator.
