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: Aleksander W. <ale...@mo...> - 2015-12-09 07:31:50
|
Hi. Thank you for this information. First problem that we notice, is that your chunkservers were disconnected at Dec 9 08:01:36. This kind of behaviour may indicate that you mfsmaster process is working really hard. Second information from you syslog was metadata store time. It's about 100 seconds. Combining this informations together we can assume that you may experience SWAPPING problem. Every hour master dumps metadata as a separate subprocess, so it needs more RAM during this operation (about 10-20% more than usual). So can you check this on your mfsmaster server: - Amount of RAM installed in your hardware. - Amount of RAM used by master. Also you can run top at full hour and check if your system uses swap? It is possible that you need to increase amount of RAM in your master server. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 12/09/2015 04:39 AM, fangyao wrote: > hi. > all server MooseFS version 2.0.80-1 and we edited editchunks.c > // > syslog(LOG_WARNING,"chunkserver has nonexistent chunk (%016"PRIX64"_%08"PRIX32"), so create it for future deletion",chunkid,version); > > > syslog > > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: main master server module: (ip:192.168.1.46) write error: EPIPE (Broken pipe) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.82:9422,5), but server is still connected > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: can't accept chunkserver (ip: 192.168.1.82 / port: 9422) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.82 / port: 9422, usedspace: 4585512808448 (4270.59 GiB), totalspace: 12073950502912 (11244.74 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.80 / port: 9422, usedspace: 852051292160 (793.53 GiB), totalspace: 2219235217408 (2066.82 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.83 / port: 9422, usedspace: 4585739321344 (4270.80 GiB), totalspace: 12073407995904 (11244.24 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.79 / port: 9422, usedspace: 863847518208 (804.52 GiB), totalspace: 2249241448448 (2094.77 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.81 / port: 9422, usedspace: 860428738560 (801.34 GiB), totalspace: 2240201351168 (2086.35 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.84 / port: 9422, usedspace: 4586834935808 (4271.82 GiB), totalspace: 12073407995904 (11244.24 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.82 / port: 9422, usedspace: 4585512808448 (4270.59 GiB), totalspace: 12073950502912 (11244.74 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.78 / port: 9422, usedspace: 864117645312 (804.77 GiB), totalspace: 2249241448448 (2094.77 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.84:9422,7) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.84 / port: 9422, usedspace: 4586834935808 (4271.82 GiB), totalspace: 12073407995904 (11244.24 GiB) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.81:9422,4) > Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.81 / port: 9422, usedspace: 860428738560 (801.34 GiB), totalspace: 2240201351168 (2086.35 GiB) > Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.79:9422,2) > Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.79 / port: 9422, usedspace: 863847518208 (804.52 GiB), totalspace: 2249241448448 (2094.77 GiB) > Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.80:9422,3) > Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.80 / port: 9422, usedspace: 852052361216 (793.54 GiB), totalspace: 2219235217408 (2066.82 GiB) > Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.83:9422,6) > Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.83 / port: 9422, usedspace: 4585739321344 (4270.80 GiB), totalspace: 12073407995904 (11244.24 GiB) > Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.78:9422,1) > Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.78 / port: 9422, usedspace: 864117645312 (804.77 GiB), totalspace: 2249241448448 (2094.77 GiB) > Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: child finished > Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.82:9422,5) > Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.82 / port: 9422, usedspace: 4585512808448 (4270.59 GiB), totalspace: 12073950502912 (11244.74 GiB) > Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: store process has finished - store time: 99.380 > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.78 / port: 9422 has been fully removed from data structures > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.82 / port: 9422 has been fully removed from data structures > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.84 / port: 9422 has been fully removed from data structures > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.81 / port: 9422 has been fully removed from data structures > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.79 / port: 9422 has been fully removed from data structures > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.83 / port: 9422 has been fully removed from data structures > Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.80 / port: 9422 has been fully removed from data structures > Dec 9 08:02:20 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.79 / port: 9422 > Dec 9 08:02:32 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.78 / port: 9422 > Dec 9 08:02:32 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.80 / port: 9422 > Dec 9 08:02:32 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.81 / port: 9422 > Dec 9 08:03:17 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.83 / port: 9422 > Dec 9 08:03:19 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.84 / port: 9422 > Dec 9 08:03:20 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.82 / port: 9422 > Dec 9 08:26:01 mfsmaster1 mfsmaster[18477]: structure check loop > > > > 2015-12-09 > ------------------------------------------------------------------------ > *方垚| (8610) 62368638-8906* > ------------------------------------------------------------------------ > *发件人：* Aleksander Wieliczko > *发送时间：* 2015-12-08 18:52:46 > *收件人：* fangyao; moosefs-users > *抄送：* > *主题：* Re: [MooseFS-Users] del and add > Hi. > Would you be so kind and send us some more details from syslog and > tell us what MooseFS version you have? > This is to small amount of information to draw some conclusions. > > > Best regards > Aleksander Wieliczko > Technical Support Engineer > MooseFS.com <moosefs.com> > On 12/08/2015 11:06 AM, fangyao wrote: >> [root@mfsmaster1 data]# grep 63946327 changelog.*mfs >> changelog.11.mfs:18378184425: 1449525706|CHUNKDEL(63946327,1) >> changelog.11.mfs:18378260221: 1449525792|CHUNKADD(63946327,1,1450130592) >> changelog.21.mfs:18377349098: 1449489681|CHUNKDEL(63946327,1) >> changelog.21.mfs:18377425708: 1449489774|CHUNKADD(63946327,1,1450094574) >> changelog.28.mfs:18376418578: 1449464464|CHUNKDEL(63946327,1) >> changelog.28.mfs:18376495479: 1449464550|CHUNKADD(63946327,1,1450069350) >> changelog.35.mfs:18375745795: 1449439281|CHUNKDEL(63946327,1) >> changelog.35.mfs:18375823198: 1449439371|CHUNKADD(63946327,1,1450044171) >> changelog.37.mfs:18375586289: 1449432091|CHUNKDEL(63946327,1) >> changelog.37.mfs:18375662761: 1449432181|CHUNKADD(63946327,1,1450036981) >> changelog.3.mfs:18378924313: 1449554475|CHUNKDEL(63946327,1) >> changelog.3.mfs:18379012240: 1449554572|CHUNKADD(63946327,1,1450159372) >> changelog.45.mfs:18374453427: 1449403276|CHUNKDEL(63946327,1) >> changelog.45.mfs:18374529796: 1449403358|CHUNKADD(63946327,1,1450008158) >> changelog.6.mfs:18378583919: 1449543696|CHUNKDEL(63946327,1) >> changelog.6.mfs:18378669372: 1449543789|CHUNKADD(63946327,1,1450148589) >> >> this log be write when EPIPE (Broken pipe) and monitor locked unused file Ascending never del >> almost EPIPE when dump and iowait not high per second 15 >> we want solve problem EPIPE >> thx >> >> >> ------------------------------------------------------------------------------ >> Go from Idea to Many App Stores Faster with Intel(R) XDK >> Give your users amazing mobile app experiences with Intel(R) XDK. >> Use one codebase in this all-in-one HTML5 development environment. >> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. >> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 >> >> >> _________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users > |
|
From: fangyao <fa...@eb...> - 2015-12-09 03:39:54
|
hi. all server MooseFS version 2.0.80-1 and we edited editchunks.c // syslog(LOG_WARNING,"chunkserver has nonexistent chunk (%016"PRIX64"_%08"PRIX32"), so create it for future deletion",chunkid,version); syslog Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: main master server module: (ip:192.168.1.46) write error: EPIPE (Broken pipe) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.82:9422,5), but server is still connected Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: can't accept chunkserver (ip: 192.168.1.82 / port: 9422) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.82 / port: 9422, usedspace: 4585512808448 (4270.59 GiB), totalspace: 12073950502912 (11244.74 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.80 / port: 9422, usedspace: 852051292160 (793.53 GiB), totalspace: 2219235217408 (2066.82 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.83 / port: 9422, usedspace: 4585739321344 (4270.80 GiB), totalspace: 12073407995904 (11244.24 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.79 / port: 9422, usedspace: 863847518208 (804.52 GiB), totalspace: 2249241448448 (2094.77 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.81 / port: 9422, usedspace: 860428738560 (801.34 GiB), totalspace: 2240201351168 (2086.35 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.84 / port: 9422, usedspace: 4586834935808 (4271.82 GiB), totalspace: 12073407995904 (11244.24 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.82 / port: 9422, usedspace: 4585512808448 (4270.59 GiB), totalspace: 12073950502912 (11244.74 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver disconnected - ip: 192.168.1.78 / port: 9422, usedspace: 864117645312 (804.77 GiB), totalspace: 2249241448448 (2094.77 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.84:9422,7) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.84 / port: 9422, usedspace: 4586834935808 (4271.82 GiB), totalspace: 12073407995904 (11244.24 GiB) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.81:9422,4) Dec 9 08:01:36 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.81 / port: 9422, usedspace: 860428738560 (801.34 GiB), totalspace: 2240201351168 (2086.35 GiB) Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.79:9422,2) Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.79 / port: 9422, usedspace: 863847518208 (804.52 GiB), totalspace: 2249241448448 (2094.77 GiB) Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.80:9422,3) Dec 9 08:01:37 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.80 / port: 9422, usedspace: 852052361216 (793.54 GiB), totalspace: 2219235217408 (2066.82 GiB) Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.83:9422,6) Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.83 / port: 9422, usedspace: 4585739321344 (4270.80 GiB), totalspace: 12073407995904 (11244.24 GiB) Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.78:9422,1) Dec 9 08:01:38 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.78 / port: 9422, usedspace: 864117645312 (804.77 GiB), totalspace: 2249241448448 (2094.77 GiB) Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: child finished Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: csdb: found cs using ip:port and csid (192.168.1.82:9422,5) Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: chunkserver register begin (packet version: 6) - ip: 192.168.1.82 / port: 9422, usedspace: 4585512808448 (4270.59 GiB), totalspace: 12073950502912 (11244.74 GiB) Dec 9 08:01:40 mfsmaster1 mfsmaster[18477]: store process has finished - store time: 99.380 Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.78 / port: 9422 has been fully removed from data structures Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.82 / port: 9422 has been fully removed from data structures Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.84 / port: 9422 has been fully removed from data structures Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.81 / port: 9422 has been fully removed from data structures Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.79 / port: 9422 has been fully removed from data structures Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.83 / port: 9422 has been fully removed from data structures Dec 9 08:02:18 mfsmaster1 mfsmaster[18477]: server ip: 192.168.1.80 / port: 9422 has been fully removed from data structures Dec 9 08:02:20 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.79 / port: 9422 Dec 9 08:02:32 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.78 / port: 9422 Dec 9 08:02:32 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.80 / port: 9422 Dec 9 08:02:32 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.81 / port: 9422 Dec 9 08:03:17 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.83 / port: 9422 Dec 9 08:03:19 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.84 / port: 9422 Dec 9 08:03:20 mfsmaster1 mfsmaster[18477]: chunkserver register end (packet version: 6) - ip: 192.168.1.82 / port: 9422 Dec 9 08:26:01 mfsmaster1 mfsmaster[18477]: structure check loop 2015-12-09 方| (8610) 62368638-8906 发件人： Aleksander Wieliczko 发送时间： 2015-12-08 18:52:46 收件人： fangyao; moosefs-users 抄送： 主题： Re: [MooseFS-Users] del and add Hi. Would you be so kind and send us some more details from syslog and tell us what MooseFS version you have? This is to small amount of information to draw some conclusions. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com On 12/08/2015 11:06 AM, fangyao wrote: [root@mfsmaster1 data]# grep 63946327 changelog.*mfs changelog.11.mfs:18378184425: 1449525706|CHUNKDEL(63946327,1) changelog.11.mfs:18378260221: 1449525792|CHUNKADD(63946327,1,1450130592) changelog.21.mfs:18377349098: 1449489681|CHUNKDEL(63946327,1) changelog.21.mfs:18377425708: 1449489774|CHUNKADD(63946327,1,1450094574) changelog.28.mfs:18376418578: 1449464464|CHUNKDEL(63946327,1) changelog.28.mfs:18376495479: 1449464550|CHUNKADD(63946327,1,1450069350) changelog.35.mfs:18375745795: 1449439281|CHUNKDEL(63946327,1) changelog.35.mfs:18375823198: 1449439371|CHUNKADD(63946327,1,1450044171) changelog.37.mfs:18375586289: 1449432091|CHUNKDEL(63946327,1) changelog.37.mfs:18375662761: 1449432181|CHUNKADD(63946327,1,1450036981) changelog.3.mfs:18378924313: 1449554475|CHUNKDEL(63946327,1) changelog.3.mfs:18379012240: 1449554572|CHUNKADD(63946327,1,1450159372) changelog.45.mfs:18374453427: 1449403276|CHUNKDEL(63946327,1) changelog.45.mfs:18374529796: 1449403358|CHUNKADD(63946327,1,1450008158) changelog.6.mfs:18378583919: 1449543696|CHUNKDEL(63946327,1) changelog.6.mfs:18378669372: 1449543789|CHUNKADD(63946327,1,1450148589) this log be write when EPIPE (Broken pipe) and monitor locked unused file Ascending never del almost EPIPE when dump and iowait not high per second 15 we want solve problem EPIPE thx ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Aleksander W. <ale...@mo...> - 2015-12-08 10:52:52
|
Hi. Would you be so kind and send us some more details from syslog and tell us what MooseFS version you have? This is to small amount of information to draw some conclusions. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 12/08/2015 11:06 AM, fangyao wrote: > [root@mfsmaster1 data]# grep 63946327 changelog.*mfs > changelog.11.mfs:18378184425: 1449525706|CHUNKDEL(63946327,1) > changelog.11.mfs:18378260221: 1449525792|CHUNKADD(63946327,1,1450130592) > changelog.21.mfs:18377349098: 1449489681|CHUNKDEL(63946327,1) > changelog.21.mfs:18377425708: 1449489774|CHUNKADD(63946327,1,1450094574) > changelog.28.mfs:18376418578: 1449464464|CHUNKDEL(63946327,1) > changelog.28.mfs:18376495479: 1449464550|CHUNKADD(63946327,1,1450069350) > changelog.35.mfs:18375745795: 1449439281|CHUNKDEL(63946327,1) > changelog.35.mfs:18375823198: 1449439371|CHUNKADD(63946327,1,1450044171) > changelog.37.mfs:18375586289: 1449432091|CHUNKDEL(63946327,1) > changelog.37.mfs:18375662761: 1449432181|CHUNKADD(63946327,1,1450036981) > changelog.3.mfs:18378924313: 1449554475|CHUNKDEL(63946327,1) > changelog.3.mfs:18379012240: 1449554572|CHUNKADD(63946327,1,1450159372) > changelog.45.mfs:18374453427: 1449403276|CHUNKDEL(63946327,1) > changelog.45.mfs:18374529796: 1449403358|CHUNKADD(63946327,1,1450008158) > changelog.6.mfs:18378583919: 1449543696|CHUNKDEL(63946327,1) > changelog.6.mfs:18378669372: 1449543789|CHUNKADD(63946327,1,1450148589) > > this log be write when EPIPE (Broken pipe) and monitor locked unused file Ascending never del > almost EPIPE when dump and iowait not high per second 15 > we want solve problem EPIPE > thx > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: fangyao <fa...@eb...> - 2015-12-08 10:23:17
|
[root@mfsmaster1 data]# grep 63946327 changelog.*mfs changelog.11.mfs:18378184425: 1449525706|CHUNKDEL(63946327,1) changelog.11.mfs:18378260221: 1449525792|CHUNKADD(63946327,1,1450130592) changelog.21.mfs:18377349098: 1449489681|CHUNKDEL(63946327,1) changelog.21.mfs:18377425708: 1449489774|CHUNKADD(63946327,1,1450094574) changelog.28.mfs:18376418578: 1449464464|CHUNKDEL(63946327,1) changelog.28.mfs:18376495479: 1449464550|CHUNKADD(63946327,1,1450069350) changelog.35.mfs:18375745795: 1449439281|CHUNKDEL(63946327,1) changelog.35.mfs:18375823198: 1449439371|CHUNKADD(63946327,1,1450044171) changelog.37.mfs:18375586289: 1449432091|CHUNKDEL(63946327,1) changelog.37.mfs:18375662761: 1449432181|CHUNKADD(63946327,1,1450036981) changelog.3.mfs:18378924313: 1449554475|CHUNKDEL(63946327,1) changelog.3.mfs:18379012240: 1449554572|CHUNKADD(63946327,1,1450159372) changelog.45.mfs:18374453427: 1449403276|CHUNKDEL(63946327,1) changelog.45.mfs:18374529796: 1449403358|CHUNKADD(63946327,1,1450008158) changelog.6.mfs:18378583919: 1449543696|CHUNKDEL(63946327,1) changelog.6.mfs:18378669372: 1449543789|CHUNKADD(63946327,1,1450148589) this log be write when EPIPE (Broken pipe) and monitor locked unused file Ascending never del almost EPIPE when dump and iowait not high per second 15 we want solve problem EPIPE thx |
|
From: Wolfgang <moo...@wo...> - 2015-12-04 12:42:39
|
Dear List! I'm using 6 bananapie's as chunkservers and a virtual Ubuntu as Master. I'm doing a everyday backup of my data to the moose-fs-cluster with the following script: http://pastebin.com/95QK0ywQ It's using rsync but to remain history the script makes a folder like 2015-11-13__06-45-01 and checks for changes - if a file has not changed since the last execution it is making a hardlink to save disc space. (but you have the complete folder-structure on every run) As this script runs on a daily base there are more and more folders - and more and more hardlinks as 99% of the files don't change. Normally the save duration for the moose-fs metadata from the master - shown in the web-gui - takes from 10-25s. Now what I observe is that after abt. 3 weeks the saving of the master-metadata takes longer and longer - until it takes several minutes and the master is getting blocked, load is very high and not getting finished within hours. Before I added swap-space the master process died with out of memory error. Now I added 8GB HDD-Swap-Space so the master isn't dieing but when the master is swapping its very very slow. Then when I manage to delete some of the daily folders from the backup it starts working again and saving metadata is again down to 10-25s Master Ram: 4GB metadata.mfs.back is currently abt. 925MB Total Space within moose-fs: 8.4TB Available 2.9TB du -sh /data/moos/homedirs/ 2.9TB du -sh /data/moos/homedirs/2015-11-13__06-45-01/ 1.5TB So my wild guess is that there are to much hardlinks to manage - is there anything known in that direction - or does anybody knows what I can test further on this issue? Thank you very much & have a nice weekend! Greetings from Austria Wolfgang |
|
From: Aleksander W. <ale...@mo...> - 2015-12-03 10:14:24
|
Hi, Thank you for your information. We will fix this problem in the nearest MooseFS release. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 12/03/2015 11:02 AM, 18...@gm... wrote: > Hi, > > I only have one master server, so this way works. I'm seeing chunks > replication happens now. > > Thanks for your support. > > On Thu, Dec 3, 2015 at 4:58 PM, Aleksander Wieliczko > <ale...@mo...> wrote: >> Hi, >> >> If you have reinstalled chunkserver you probably removed >> /var/lib/mfs/chunkserverid.mfs file with chunkserver metadata ID. >> Now chunkserver and chunkserver disks are in mismatch condition. >> >> Solution is simple but very dangerous. >> Please understand - this is security solution to prevent connecting >> chunkserver to wrong master!!! >> If you have 100% sure that this disks will be connected to right master and >> there is no possibility that there is some mistake in configuration please >> remove .metaid file from /mnt/sdb and /mnt/sdc folder. >> >> If you connect chunks to wrong master they will be removed. >> >> Best regards >> Aleksander Wieliczko >> Technical Support Engineer >> MooseFS.com >> >> On 12/03/2015 08:41 AM, 18...@gm... wrote: >> >> Hi, I have 1 chunkserver in the cluster need to be reinstalled, and >> after configured it, chunkserver can't start >> >> # /etc/init.d/moosefs- >> chunkserver start >> Starting moosefs-chunkserver: >> open files limit has been set to: 16384 >> working directory: /var/lib/mfs >> lockfile created and locked >> setting glibc malloc arena max to 8 >> setting glibc malloc arena test to 1 >> initializing mfschunkserver modules ... >> hdd space manager: chunkserver without meta id shouldn't use drive >> with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive >> definition to ignore this (dangerous) >> hdd space manager: chunkserver without meta id shouldn't use drive >> with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive >> definition to ignore this (dangerous) >> hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file >> init: hdd space manager failed !!! >> error occured during initialization - exiting >> >> Its working mfs disks were mounted >> >> # mount /dev/sdb1 /mnt/sdb >> # mount /dev/sdc1 /mnt/sdc >> >> All mfs data disks were untouched, only remounted lastly. >> >> How can I solve this error? >> Thanks in advance. >> >> ------------------------------------------------------------------------------ >> Go from Idea to Many App Stores Faster with Intel(R) XDK >> Give your users amazing mobile app experiences with Intel(R) XDK. >> Use one codebase in this all-in-one HTML5 development environment. >> Design, debug & build mobile apps & 2D/3D high-impact games for multiple >> OSs. >> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 >> _________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users >> >> |
|
From: <18...@gm...> - 2015-12-03 10:03:06
|
Hi, I only have one master server, so this way works. I'm seeing chunks replication happens now. Thanks for your support. On Thu, Dec 3, 2015 at 4:58 PM, Aleksander Wieliczko <ale...@mo...> wrote: > Hi, > > If you have reinstalled chunkserver you probably removed > /var/lib/mfs/chunkserverid.mfs file with chunkserver metadata ID. > Now chunkserver and chunkserver disks are in mismatch condition. > > Solution is simple but very dangerous. > Please understand - this is security solution to prevent connecting > chunkserver to wrong master!!! > If you have 100% sure that this disks will be connected to right master and > there is no possibility that there is some mistake in configuration please > remove .metaid file from /mnt/sdb and /mnt/sdc folder. > > If you connect chunks to wrong master they will be removed. > > Best regards > Aleksander Wieliczko > Technical Support Engineer > MooseFS.com > > On 12/03/2015 08:41 AM, 18...@gm... wrote: > > Hi, I have 1 chunkserver in the cluster need to be reinstalled, and > after configured it, chunkserver can't start > > # /etc/init.d/moosefs- > chunkserver start > Starting moosefs-chunkserver: > open files limit has been set to: 16384 > working directory: /var/lib/mfs > lockfile created and locked > setting glibc malloc arena max to 8 > setting glibc malloc arena test to 1 > initializing mfschunkserver modules ... > hdd space manager: chunkserver without meta id shouldn't use drive > with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive > definition to ignore this (dangerous) > hdd space manager: chunkserver without meta id shouldn't use drive > with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive > definition to ignore this (dangerous) > hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file > init: hdd space manager failed !!! > error occured during initialization - exiting > > Its working mfs disks were mounted > > # mount /dev/sdb1 /mnt/sdb > # mount /dev/sdc1 /mnt/sdc > > All mfs data disks were untouched, only remounted lastly. > > How can I solve this error? > Thanks in advance. > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple > OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > |
|
From: Aleksander W. <ale...@mo...> - 2015-12-03 09:58:18
|
Hi, If you have reinstalled chunkserver you probably removed /var/lib/mfs/chunkserverid.mfs file with chunkserver metadata ID. Now chunkserver and chunkserver disks are in mismatch condition. Solution is simple but very dangerous. *Please understand - this is security solution to prevent connecting chunkserver to wrong master!!!* If you have 100% sure that this disks will be connected to right master and there is no possibility that there is some mistake in configuration please remove .metaid file from /mnt/sdb and /mnt/sdc folder. If you connect chunks to wrong master they will be removed. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 12/03/2015 08:41 AM, 18...@gm... wrote: > Hi, I have 1 chunkserver in the cluster need to be reinstalled, and > after configured it, chunkserver can't start > > # /etc/init.d/moosefs-chunkserver start > Starting moosefs-chunkserver: > open files limit has been set to: 16384 > working directory: /var/lib/mfs > lockfile created and locked > setting glibc malloc arena max to 8 > setting glibc malloc arena test to 1 > initializing mfschunkserver modules ... > hdd space manager: chunkserver without meta id shouldn't use drive > with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive > definition to ignore this (dangerous) > hdd space manager: chunkserver without meta id shouldn't use drive > with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive > definition to ignore this (dangerous) > hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file > init: hdd space manager failed !!! > error occured during initialization - exiting > > Its working mfs disks were mounted > > # mount /dev/sdb1 /mnt/sdb > # mount /dev/sdc1 /mnt/sdc > > All mfs data disks were untouched, only remounted lastly. > > How can I solve this error? > Thanks in advance. > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: <18...@gm...> - 2015-12-03 07:41:31
|
Hi, I have 1 chunkserver in the cluster need to be reinstalled, and after configured it, chunkserver can't start # /etc/init.d/moosefs-chunkserver start Starting moosefs-chunkserver: open files limit has been set to: 16384 working directory: /var/lib/mfs lockfile created and locked setting glibc malloc arena max to 8 setting glibc malloc arena test to 1 initializing mfschunkserver modules ... hdd space manager: chunkserver without meta id shouldn't use drive with defined meta id (file: '/mnt/sdb/.metaid') - use '!' in drive definition to ignore this (dangerous) hdd space manager: chunkserver without meta id shouldn't use drive with defined meta id (file: '/mnt/sdc/.metaid') - use '!' in drive definition to ignore this (dangerous) hdd space manager: no hdd space defined in /etc/mfs/mfshdd.cfg file init: hdd space manager failed !!! error occured during initialization - exiting Its working mfs disks were mounted # mount /dev/sdb1 /mnt/sdb # mount /dev/sdc1 /mnt/sdc All mfs data disks were untouched, only remounted lastly. How can I solve this error? Thanks in advance. |
|
From: Aleksander W. <ale...@mo...> - 2015-11-30 12:52:19
|
Hi At this moment we don't have native windows client. We are working on it. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 11/30/2015 09:55 AM, Angus Yang 杨阳 wrote: > Dear All > > Did Moosefs has windows client ? > > I did not find it on www.moosefs.org <http://www.moosefs.org> . > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Angus Y. 杨阳 <ang...@vi...> - 2015-11-30 08:56:09
|
Dear All Did Moosefs has windows client ? I did not find it on www.moosefs.org . |
|
From: web u. <web...@gm...> - 2015-11-23 04:11:31
|
Thanks. Upgrade worked like a charm. On Sun, Nov 22, 2015 at 6:27 PM, Piotr Robert Konopelko < pio...@mo...> wrote: > Hello, > > In the most current documentation I see that the 'ce' has been removed > from them. Should I remove the moosefs-ce packages and install the > following packages: > > Yes. > > What will happen to my config files and data in /var/lib/mfs > > Modified config files and /var/lib/mfs folder should not be removed, but > just in case, we recommend to do a backup. > > > Best regards, > > -- > Piotr Robert Konopelko > *MooseFS Technical Support Engineer* | moosefs.com > > On 22 Nov 2015, at 6:42 PM, web user <web...@gm...> wrote: > > When I see what installed packages I have I get: > > moosefs-ce-cgi install > moosefs-ce-cgiserv install > moosefs-ce-chunkserver install > moosefs-ce-cli install > moosefs-ce-client install > moosefs-ce-common install > moosefs-ce-master install > moosefs-ce-metalogger install > > > These were not upgraded when I did an "apt-get upgrade" > > In the most current documentation I see that the 'ce' has been removed > from them. Should I remove the moosefs-ce packages and install the > following packages: > > moosefs-cgi > moosefs-cgiserv > moosefs-chunkserver > moosefs-cli > moosefs-client > moosefs-common > moosefs-master > moosefs-metalogger > > > What will happen to my config files and data in /var/lib/mfs > > Regards, > > WU > > ------------------------------------------------------------------------------ > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > |
|
From: Piotr R. K. <pio...@mo...> - 2015-11-22 23:53:04
|
Hello, please download the newest key: wget -O - http://ppa.moosefs.com/moosefs.key | apt-key add - Best regards, -- Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com <https://moosefs.com/> > On 22 Nov 2015, at 5:58 PM, web user <web...@gm...> wrote: > > Hi, > > I'm trying to upgrade my mfs to the latest version and when I run: > > apt-get update > > I get the following error: > > W: GPG error: http://ppa.moosefs.com <http://ppa.moosefs.com/> trusty InRelease: The following signatures were invalid: KEYEXPIRED 1433428634 KEYEXPIRED 1433428634 KEYEXPIRED 1433428634 > > Any idea on what I'm doing wrong. I have mfs version 2.50CE. > > I'm on ubuntu 14.04 > > Regards, > > WU > ------------------------------------------------------------------------------ > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Piotr R. K. <pio...@mo...> - 2015-11-22 23:27:08
|
Hello, > In the most current documentation I see that the 'ce' has been removed from them. Should I remove the moosefs-ce packages and install the following packages: Yes. > What will happen to my config files and data in /var/lib/mfs Modified config files and /var/lib/mfs folder should not be removed, but just in case, we recommend to do a backup. Best regards, -- Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com <https://moosefs.com/> > On 22 Nov 2015, at 6:42 PM, web user <web...@gm...> wrote: > > When I see what installed packages I have I get: > > moosefs-ce-cgi install > moosefs-ce-cgiserv install > moosefs-ce-chunkserver install > moosefs-ce-cli install > moosefs-ce-client install > moosefs-ce-common install > moosefs-ce-master install > moosefs-ce-metalogger install > > > These were not upgraded when I did an "apt-get upgrade" > > In the most current documentation I see that the 'ce' has been removed from them. Should I remove the moosefs-ce packages and install the following packages: > > moosefs-cgi > moosefs-cgiserv > moosefs-chunkserver > moosefs-cli > moosefs-client > moosefs-common > moosefs-master > moosefs-metalogger > > > What will happen to my config files and data in /var/lib/mfs > > Regards, > > WU > ------------------------------------------------------------------------------ > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: web u. <web...@gm...> - 2015-11-22 17:42:09
|
When I see what installed packages I have I get: moosefs-ce-cgi install moosefs-ce-cgiserv install moosefs-ce-chunkserver install moosefs-ce-cli install moosefs-ce-client install moosefs-ce-common install moosefs-ce-master install moosefs-ce-metalogger install These were not upgraded when I did an "apt-get upgrade" In the most current documentation I see that the 'ce' has been removed from them. Should I remove the moosefs-ce packages and install the following packages: moosefs-cgi moosefs-cgiserv moosefs-chunkserver moosefs-cli moosefs-client moosefs-common moosefs-master moosefs-metalogger What will happen to my config files and data in /var/lib/mfs Regards, WU |
|
From: web u. <web...@gm...> - 2015-11-22 16:58:44
|
Hi, I'm trying to upgrade my mfs to the latest version and when I run: apt-get update I get the following error: W: GPG error: http://ppa.moosefs.com trusty InRelease: The following signatures were invalid: KEYEXPIRED 1433428634 KEYEXPIRED 1433428634 KEYEXPIRED 1433428634 Any idea on what I'm doing wrong. I have mfs version 2.50CE. I'm on ubuntu 14.04 Regards, WU |
|
From: Andreas H. <ah...@it...> - 2015-11-20 11:08:48
|
Hi! Our upgrade from 1.6.27 to 2.0.81 on Debian Linux 7 and 8 was succesfull. I have documented all steps on <https://itp.tugraz.at/~ahi/admin/MooseFS.html#orgheadline4>. I use self compiled Debian packages using the already included "debian/" directories; therefore my config and metadata have already been at the correct places. Service was available during most of the upgrade; only for less than 10 minutes during master servers update connections blocked on clients. Thanks to the team for all their hard work and their decision to further maintain a GPL licensed variant. Best regards Andreas -- Andreas Hirczy <ah...@it...> https://itp.tugraz.at/~ahi/ Graz University of Technology phone: +43/316/873- 8190 Institute of Theoretical and Computational Physics fax: +43/316/873-10 8190 Petersgasse 16, A-8010 Graz mobile: +43/664/859 23 57 |
|
From: Aleksander W. <ale...@mo...> - 2015-11-18 13:13:10
|
Hi. First of all. Chunkserver do not have any metadata information. If you have chunks disks you don't have a problem. Just install moosefs chunkserver packages and edit /etc/mfs/mfshdd.cfg file and enter path to disks with chunks. Than just start chunkserver. But if you formatted mfsmaster machine and you don't have metadata.mfs file you have big problem. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> <moosefs.com> On 11/18/2015 01:31 PM, hanyuwei70 wrote: > Hi, everyone > One of my mfs cluster machine expericed the system fault. So I > reinstalled the OS but I forgot to save metadata on the chunkserver. > But chunk is saved. > So is it possible to restore files on this chunkserver? |
|
From: Aleksander W. <ale...@mo...> - 2015-11-18 13:04:34
|
Hi. First of all. Chunkserver do not have any metadata information. If you have chunks disks you don't have a problem. Just install moosefs chunkserver packages and edit /etc/mfs/mfshdd.cfg file and enter path to disks with chunks. Than just start chunkserver. But if you formatted mfsmaster machine and you don't have metadata.mfs file you have big problem. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 11/18/2015 01:31 PM, hanyuwei70 wrote: > Hi, everyone > One of my mfs cluster machine expericed the system fault. So I > reinstalled the OS but I forgot to save metadata on the chunkserver. > But chunk is saved. > So is it possible to restore files on this chunkserver? > > > ------------------------------------------------------------------------------ > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: h. <han...@vi...> - 2015-11-18 12:47:50
|
Hi, everyone One of my mfs cluster machine expericed the system fault. So I reinstalled the OS but I forgot to save metadata on the chunkserver. But chunk is saved. So is it possible to restore files on this chunkserver? |
|
From: Aleksander W. <ale...@mo...> - 2015-11-17 08:40:24
|
Hi, Thanks for your reply. If you are using RAID as chunkserver HDD please check if you don't have any problems with RAID controller a specially on 10.172.217.237 chunkserver. MooseFS is not able to detect errors when chunkserver hdd is RAID. So you will see ok status under "DISK" tab in CGI web page. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 11/12/2015 03:55 AM, Angus Yang 杨阳 wrote: > Dear All > > i was using mfs to collect my server's Log. like jboss or nginx's Log. > > when i check yesterday. i found the software log stop writing and lost > servral hours log message. > > i check my server's /var/log/message. it show: > > Nov 11 09:30:11 localhost mfsmount[26420]: file: 662, index: 4, chunk: > 9463, version: 3 - writeworker: connection with (10.172.217.237:9422) > was reset by peer / ZEROREAD (unfinished writes: 2; try counter: 1) > Nov 11 09:30:12 localhost mfsmount[26420]: file: 662, index: 4 - > fs_writechunk returned status: Chunk lost > Nov 11 09:30:12 localhost mfsmount[26420]: error writing file number > 662: ENXIO (No such device or address) > > ENXIO (No such device or address) what meaning? > > > > ------------------------------------------------------------------------------ > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Aleksander W. <ale...@mo...> - 2015-11-17 07:40:07
|
Hello, In MooseFS GPL version there is no possibility to change mfsmaster data_path without restarting process. Data_path during process start is set as current working directory. If you system need to work without long break time, please consider to use MooseFS PRO version. In PRO version saving metadata scenario is little bit different than in single master model(GPL version). Master leader saving metadata every 24 hour and master follower's saving data every hour. So in PRO version you can change data_path on master follower and restart process without any interruptions. If you are interested in MooseFS PRO version tests please write to su...@mo.... Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 11/16/2015 09:14 PM, Wilson, Steven M wrote: > Hi, > > I'm wondering if there is a way to change the DATA_PATH location where > mfsmaster writes its files without restarting mfsmaster. I have one > MooseFS file system that takes over 70 seconds to write its metadata > to disk at the top of each hour. I'd like to try pointing DATA_PATH > to an SSD drive to see how much that would help but I don't want to > stop a very active server just to try out this experiment. > > Thanks! > > Steve > > > ------------------------------------------------------------------------------ > Presto, an open source distributed SQL query engine for big data, initially > developed by Facebook, enables you to easily query your data on Hadoop in a > more interactive manner. Teradata is also now providing full enterprise > support for Presto. Download a free open source copy now. > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Wilson, S. M <st...@pu...> - 2015-11-16 20:14:17
|
Hi, I'm wondering if there is a way to change the DATA_PATH location where mfsmaster writes its files without restarting mfsmaster. I have one MooseFS file system that takes over 70 seconds to write its metadata to disk at the top of each hour. I'd like to try pointing DATA_PATH to an SSD drive to see how much that would help but I don't want to stop a very active server just to try out this experiment. Thanks! Steve |
|
From: Aleksander W. <ale...@mo...> - 2015-11-13 14:30:06
|
Hi Michael, Yes we tested it under load. We migrated whole production environment(more than 600 clients) without any problems. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> |
|
From: Michael T. <mic...@ho...> - 2015-11-12 07:56:34
|
This is an awesome feature. Has it been tested under heavy load? On Wed, Nov 11, 2015 at 10:43 PM -0800, "Aleksander Wieliczko" <ale...@mo...> wrote: Hi Michael, Exactly. You can update old MooseFS master to new 2.0, and start whole cluster with old components like: chunkservers, clients, metaloggers. After this step you can start one by one update for other MooseFS components under running MooseFS cluster. Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 11/12/2015 03:01 AM, Michael Tinsay wrote: > Does this mean that once I have upgrade the master node to 2.x the > 1.6.27-5 metaloggers, chunkservers, and clients can be started up and > used while I upgrade them to 2.x one at a time? > > > -- mike t. > > > Date: Fri, 30 Oct 2015 12:02:13 +0100 > > From: Piotr Robert Konopelko <pio...@mo...> > > Subject: Re: [MooseFS-Users] Access to data while upgradeing from > > 1.6.27 to 2.xxx? > > To: Andreas Hirczy <ah...@it...> > > Cc: MooseFS-Users <moo...@li...> > > Message-ID: <DE0...@mo...> > > Content-Type: text/plain; charset="utf-8" > > > > Hi Andreas, > > > > yes, > > you?ll be able to access your data with your 1.6.27-5 clients. > > > > Please remember to do a backup of metadata, and please remember that > > we recommend to do the upgrade in the following order: > > > > 1. MFS Master (needs to be done first of all) > > 2. MFS Metalogger > > 3. MFS Chunkservers > > 4. MFS Clients (Mounts) > > > > Please also read this document before starting the upgrade: > > https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf > <https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf> > > > > In case of any questions, please don?t hesitate to contact us. > > > > > > > > Best regards, > > > > -- > > Piotr Robert Konopelko > > > > ------------------------------------------------------------------------------ > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
84 messages has been excluded from this view by a project administrator.
