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: Travis H. <tra...@tr...> - 2011-12-01 21:01:18
|
On 11-11-30 8:50 PM, thirsd cheng wrote: > i am now confused the owner of the file in MFS: > client user: user1,user2 > how to config mfsexports.cfg > 1.is <http://1.is> the user for maproot on master ,or not ( on client) ? > 2.the password is for mfsmount authority,or must meet the users's > System Login Password > 3. i config /test ,maproot=root > when i use user1 to mount the /test, I touch a new file(a.txt) > ,the file's owner is root?,or user1? > when i use user2 to mount the /test,can I use a.txt? > i will be very glad to recieve your reply > 1. the user for maproot is resolved from the point of view of the machine that is running the mfsmaster process. 2. the password if supplied into the mfsexports, as far as I know, is just a password (or MD5 password), and exists within the mfsexports file, it is not the system's /etc/passwd user's system login password. 3. the file touched by user1 should be owned by root in the file system. I have been unable to figure out how to mount as a user1, user2 in my system so far. |
|
From: Travis H. <tra...@tr...> - 2011-12-01 20:38:21
|
On 11-12-01 2:31 PM, matakura wrote: > Does mooseFS implement something that makes its security? > There is the mfsexports, used by the mfsmaster process to define access control. It kind of works a bit like NFS exports. By default, the sample config file that comes with the distribution exports everything without requiring authentication. See also: man mfsexports.cfg |
|
From: matakura <mat...@gm...> - 2011-12-01 19:31:40
|
Does mooseFS implement something that makes its security? -- Driver |
|
From: liangzhenfang <lia...@ba...> - 2011-12-01 03:40:49
|
Dear, mfser I have installed the MFS. But it can not cache the lookup operations . Here is the mfsmount way and the cat .stats result mfsmount -o mfsattrcacheto=60000 -o mfsentrycacheto=60000 -o mfsentrycacheto=60000 -o mfswritecachesize=1024 /home/rrddata/ -H HOST fuse_ops.statfs: 24 fuse_ops.access: 0 fuse_ops.lookup-cached: 75 fuse_ops.lookup: 12348564 fuse_ops.getattr-cached: 170 fuse_ops.getattr: 1578048 fuse_ops.setattr: 35 fuse_ops.mknod: 0 fuse_ops.unlink: 1096 fuse_ops.mkdir: 1 fuse_ops.rmdir: 0 fuse_ops.symlink: 0 fuse_ops.readlink: 0 fuse_ops.rename: 8 fuse_ops.link: 0 fuse_ops.opendir: 342 fuse_ops.readdir: 1759 fuse_ops.releasedir: 342 fuse_ops.create: 1107 fuse_ops.open: 4438617 fuse_ops.release: 4439721 fuse_ops.read: 3068682 fuse_ops.write: 35827564 fuse_ops.flush: 4439692 fuse_ops.fsync: 13 master.reconnects: 0 master.bytes_sent: 929559594 master.bytes_received: 1395627491 master.packets_sent: 35603705 master.packets_received: 35600113 And How Can I improve the cache Hit. Thank you very much in advance Zhenfang,liang |
|
From: thirsd c. <th...@gm...> - 2011-12-01 01:50:25
|
i am now confused the owner of the file in MFS:
client user: user1,user2
how to config mfsexports.cfg
1.is the user for maproot on master ,or not ( on client) ?
2.the password is for mfsmount authority,or must meet the users's System
Login Password
3. i config /test ,maproot=root
when i use user1 to mount the /test, I touch a new file(a.txt) ,the
file's owner is root?,or user1?
when i use user2 to mount the /test,can I use a.txt?
i will be very glad to recieve your reply
|
|
From: <fl...@co...> - 2011-11-30 17:16:48
|
You need to find the file and use mfsfilerepair :) On Wed, 30 Nov 2011 15:30:42 +0100, Sébastien MERTES wrote: > Before this accident, I was errors with my mfsmaster. > This errors are again reproduced. > > this errors are : > > chunk 000000000032061B has only invalid copies (2) - please repair it > manually > chunk 000000000032061B_00000008 - invalid copy on (192.168.2.3 - > ver:00000007) > chunk 000000000032061B_00000008 - invalid copy on (192.168.2.2 - > ver:00000007) > > how it repair manually ? > > On 30/11/2011 14:12, Sébastien MERTES wrote: > >> Thank you Michal for your help. I try this command but it doesn't work. The command termined by "killed : 9". But, why to use only chanlog.1.mfs and changlog.1.mfs ? I have try the command with success on the advice of Davies ;): # mv metadata.mfs.back.tmp metadata.mfs.back # mfsmetarestore -a -d /[directory metadata] On 30/11/2011 13:39, Michał Borychowski wrote: >> >>> Yes, that's right you should use .tmp file. You can use this command: mfsmetarestore -m metadata.mfs.back.tmp -o metadata.mfs changelog.1.mfs changelog.0.mfs Kind regards Michał Borychowski MooseFS Support Manager _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gemius S.A. ul. Wołoska 7, 02-672 Warszawa Budynek MARS, klatka D Tel.: +4822 874-41-00 Fax : +4822 874-41-01 -----Original Message----- From: Sébastien MERTES [mailto:seb...@u-... [10]] Sent: Wednesday, November 30, 2011 11:42 AM To: moo...@li... [11]Subject: Re: [Moosefs-users] problem metadata Thank you very much Davies, it works !!!!! thank you thank you and thank you !!! Sébastien On 30/11/2011 09:48, Davies Liu wrote: >>> >>>> Have you any other metalogger ? If they have some recently change logs, it may help. On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu wrote: >>>> >>>>> If you found changelog.2.mfs, you should: mv metadata.mfs.back.tmp metadata.mfs.back mfsmetarestore -a -d /xxx On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu wrote: >>>>> >>>>>> I have not found changelog.2.mfs, so can not recover the full data with change logs. changelog.3.mfs are too older, no needed. metadata.mfs.back.tmp is the last snapshot, you can rename it to metadata.mfs and start mfsmaster. Some recently modification may been lost. On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu >>> wrote: >>> >>>>>>> I will try. On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES wrote: >>>>>>> >>>>>>>> The metadata and changelog files are located in the ftp server ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 [8]The login is anonymous. Can you help me ? On 29/11/2011 15:27, Davies Liu wrote: >>>>>>>> >>>>>>>>> Could you share the metadata and changelog out ? Then we could help recover it. On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES wrote: >>>>>>>>> >>>>>>>>>> Hello, I have a serious problem with mfsmaster. The server crashed roughly and the mfsmetaloggers are not operate. With the command mfsmetarestore -a -d /[directory-metadata], i have the following messages : loading names ... loading edge: read error: ENOENT (No such file or directory) error can't read metadata from file: metadata.mfs.back Can you help me please ??? It's very very urgent. Thank you. Sébastien ---------------------------------------------------------------- -------------- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d [4] _______________________________________________ moosefs-users mailing list moo...@li... [5] https://lists.sourceforge.net/lists/listinfo/moosefs-users [6] >>>>>>> -- - Davies >>>>>> -- - Davies >>>>> -- - Davies >>> ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d [12] _______________________________________________ moosefs-users mailing list moo...@li... [13] https://lists.sourceforge.net/lists/listinfo/moosefs-users [14] >> ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d [15] _______________________________________________ moosefs-users mailing list moo...@li... [16] https://lists.sourceforge.net/lists/listinfo/moosefs-users [17] > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d [18] > _______________________________________________ > moosefs-users mailing list > moo...@li... [19] > https://lists.sourceforge.net/lists/listinfo/moosefs-users [20] Links: ------ [1] mailto:dav...@gm... [2] mailto:dav...@gm... [3] mailto:dav...@gm... [4] http://p.sf.net/sfu/splunk-novd2d [5] mailto:moo...@li... [6] https://lists.sourceforge.net/lists/listinfo/moosefs-users [7] mailto:seb...@u-... [8] http://webmail.coppint.com/ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 [9] mailto:seb...@u-... [10] mailto:seb...@u-... [11] mailto:moo...@li... [12] http://p.sf.net/sfu/splunk-novd2d [13] mailto:moo...@li... [14] https://lists.sourceforge.net/lists/listinfo/moosefs-users [15] http://p.sf.net/sfu/splunk-novd2d [16] mailto:moo...@li... [17] https://lists.sourceforge.net/lists/listinfo/moosefs-users [18] http://p.sf.net/sfu/splunk-novd2d [19] mailto:moo...@li... [20] https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Davies L. <dav...@gm...> - 2011-11-30 14:54:12
|
You are welcome :) On Wed, Nov 30, 2011 at 6:41 PM, Sébastien MERTES <seb...@u-...> wrote: > Thank you very much Davies, it works !!!!! > > > thank you thank you and thank you !!! > > Sébastien > > > > On 30/11/2011 09:48, Davies Liu wrote: >> >> Have you any other metalogger ? >> >> If they have some recently change logs, it may help. >> >> On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu<dav...@gm...> wrote: >>> >>> If you found changelog.2.mfs, you should: >>> >>> mv metadata.mfs.back.tmp metadata.mfs.back >>> >>> mfsmetarestore -a -d /xxx >>> >>> On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu<dav...@gm...> wrote: >>>> >>>> I have not found changelog.2.mfs, so can not recover the full data >>>> with change logs. >>>> changelog.3.mfs are too older, no needed. >>>> >>>> metadata.mfs.back.tmp is the last snapshot, you can rename it to >>>> metadata.mfs >>>> and start mfsmaster. >>>> >>>> Some recently modification may been lost. >>>> >>>> On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu<dav...@gm...> >>>> wrote: >>>>> >>>>> I will try. >>>>> >>>>> On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES >>>>> <seb...@u-...> wrote: >>>>>> >>>>>> The metadata and changelog files are located in the ftp server >>>>>> ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 >>>>>> >>>>>> The login is anonymous. >>>>>> >>>>>> >>>>>> Can you help me ? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 29/11/2011 15:27, Davies Liu wrote: >>>>>>> >>>>>>> Could you share the metadata and changelog out ? Then we could help >>>>>>> recover it. >>>>>>> >>>>>>> On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES >>>>>>> <seb...@u-...> wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I have a serious problem with mfsmaster. The server crashed >>>>>>>> roughly and >>>>>>>> the mfsmetaloggers are not operate. >>>>>>>> >>>>>>>> With the command mfsmetarestore -a -d /[directory-metadata], i have >>>>>>>> the >>>>>>>> following messages : >>>>>>>> >>>>>>>> loading names ... loading edge: read error: ENOENT (No such file or >>>>>>>> directory) >>>>>>>> error >>>>>>>> >>>>>>>> can't read metadata from file: metadata.mfs.back >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Can you help me please ??? >>>>>>>> It's very very urgent. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> Sébastien >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> All the data continuously generated in your IT infrastructure >>>>>>>> contains a definitive record of customers, application performance, >>>>>>>> security threats, fraudulent activity, and more. Splunk takes this >>>>>>>> data and makes sense of it. IT sense. And common sense. >>>>>>>> http://p.sf.net/sfu/splunk-novd2d >>>>>>>> _______________________________________________ >>>>>>>> moosefs-users mailing list >>>>>>>> moo...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>>>>>>> >>>>>>> >>>>> >>>>> >>>>> -- >>>>> - Davies >>>> >>>> >>>> >>>> -- >>>> - Davies >>> >>> >>> >>> -- >>> - Davies >> >> >> > -- - Davies |
|
From: Sébastien M. <seb...@u-...> - 2011-11-30 14:30:54
|
Before this accident, I was errors with my mfsmaster. This errors are again reproduced. this errors are : chunk 000000000032061B has only invalid copies (2) - please repair it manually chunk 000000000032061B_00000008 - invalid copy on (192.168.2.3 - ver:00000007) chunk 000000000032061B_00000008 - invalid copy on (192.168.2.2 - ver:00000007) how it repair manually ? On 30/11/2011 14:12, Sébastien MERTES wrote: > Thank you Michal for your help. > > I try this command but it doesn't work. The command termined by "killed > : 9". > > But, why to use only chanlog.1.mfs and changlog.1.mfs ? > > I have try the command with success on the advice of Davies ;): > > # mv metadata.mfs.back.tmp metadata.mfs.back > # mfsmetarestore -a -d /[directory metadata] > > > > On 30/11/2011 13:39, Michał Borychowski wrote: >> Yes, that's right you should use .tmp file. You can use this command: >> >> mfsmetarestore -m metadata.mfs.back.tmp -o metadata.mfs changelog.1.mfs >> changelog.0.mfs >> >> >> >> Kind regards >> Michał Borychowski >> MooseFS Support Manager >> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ >> Gemius S.A. >> ul. Wołoska 7, 02-672 Warszawa >> Budynek MARS, klatka D >> Tel.: +4822 874-41-00 >> Fax : +4822 874-41-01 >> >> >> -----Original Message----- >> From: Sébastien MERTES [mailto:seb...@u-...] >> Sent: Wednesday, November 30, 2011 11:42 AM >> To: moo...@li... >> Subject: Re: [Moosefs-users] problem metadata >> >> Thank you very much Davies, it works !!!!! >> >> >> thank you thank you and thank you !!! >> >> Sébastien >> >> >> On 30/11/2011 09:48, Davies Liu wrote: >>> Have you any other metalogger ? >>> >>> If they have some recently change logs, it may help. >>> >>> On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu<dav...@gm...> wrote: >>>> If you found changelog.2.mfs, you should: >>>> >>>> mv metadata.mfs.back.tmp metadata.mfs.back >>>> >>>> mfsmetarestore -a -d /xxx >>>> >>>> On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu<dav...@gm...> wrote: >>>>> I have not found changelog.2.mfs, so can not recover the full data >>>>> with change logs. >>>>> changelog.3.mfs are too older, no needed. >>>>> >>>>> metadata.mfs.back.tmp is the last snapshot, you can rename it to >>>>> metadata.mfs and start mfsmaster. >>>>> >>>>> Some recently modification may been lost. >>>>> >>>>> On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu<dav...@gm...> >> wrote: >>>>>> I will try. >>>>>> >>>>>> On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES >>>>>> <seb...@u-...> wrote: >>>>>>> The metadata and changelog files are located in the ftp server >>>>>>> ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 >>>>>>> >>>>>>> The login is anonymous. >>>>>>> >>>>>>> >>>>>>> Can you help me ? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 29/11/2011 15:27, Davies Liu wrote: >>>>>>>> Could you share the metadata and changelog out ? Then we could >>>>>>>> help recover it. >>>>>>>> >>>>>>>> On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES >>>>>>>> <seb...@u-...> wrote: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> I have a serious problem with mfsmaster. The server crashed >>>>>>>>> roughly and the mfsmetaloggers are not operate. >>>>>>>>> >>>>>>>>> With the command mfsmetarestore -a -d /[directory-metadata], i >>>>>>>>> have the following messages : >>>>>>>>> >>>>>>>>> loading names ... loading edge: read error: ENOENT (No such file >>>>>>>>> or >>>>>>>>> directory) >>>>>>>>> error >>>>>>>>> >>>>>>>>> can't read metadata from file: metadata.mfs.back >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Can you help me please ??? >>>>>>>>> It's very very urgent. >>>>>>>>> >>>>>>>>> Thank you. >>>>>>>>> >>>>>>>>> Sébastien >>>>>>>>> >>>>>>>>> >>>>>>>>> ---------------------------------------------------------------- >>>>>>>>> -------------- All the data continuously generated in your IT >>>>>>>>> infrastructure contains a definitive record of customers, >>>>>>>>> application performance, security threats, fraudulent activity, >>>>>>>>> and more. Splunk takes this data and makes sense of it. IT >>>>>>>>> sense. And common sense. >>>>>>>>> http://p.sf.net/sfu/splunk-novd2d >>>>>>>>> _______________________________________________ >>>>>>>>> moosefs-users mailing list >>>>>>>>> moo...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>>>>>>>> >>>>>> -- >>>>>> - Davies >>>>> -- >>>>> - Davies >>>> -- >>>> - Davies >> ---------------------------------------------------------------------------- >> -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security threats, >> fraudulent activity, and more. Splunk takes this data and makes sense of it. >> IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users >> >> >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > |
|
From: Sébastien M. <seb...@u-...> - 2011-11-30 13:12:58
|
Thank you Michal for your help. I try this command but it doesn't work. The command termined by "killed : 9". But, why to use only chanlog.1.mfs and changlog.1.mfs ? I have try the command with success on the advice of Davies ;): # mv metadata.mfs.back.tmp metadata.mfs.back # mfsmetarestore -a -d /[directory metadata] On 30/11/2011 13:39, Michał Borychowski wrote: > Yes, that's right you should use .tmp file. You can use this command: > > mfsmetarestore -m metadata.mfs.back.tmp -o metadata.mfs changelog.1.mfs > changelog.0.mfs > > > > Kind regards > Michał Borychowski > MooseFS Support Manager > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > Gemius S.A. > ul. Wołoska 7, 02-672 Warszawa > Budynek MARS, klatka D > Tel.: +4822 874-41-00 > Fax : +4822 874-41-01 > > > -----Original Message----- > From: Sébastien MERTES [mailto:seb...@u-...] > Sent: Wednesday, November 30, 2011 11:42 AM > To: moo...@li... > Subject: Re: [Moosefs-users] problem metadata > > Thank you very much Davies, it works !!!!! > > > thank you thank you and thank you !!! > > Sébastien > > > On 30/11/2011 09:48, Davies Liu wrote: >> Have you any other metalogger ? >> >> If they have some recently change logs, it may help. >> >> On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu<dav...@gm...> wrote: >>> If you found changelog.2.mfs, you should: >>> >>> mv metadata.mfs.back.tmp metadata.mfs.back >>> >>> mfsmetarestore -a -d /xxx >>> >>> On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu<dav...@gm...> wrote: >>>> I have not found changelog.2.mfs, so can not recover the full data >>>> with change logs. >>>> changelog.3.mfs are too older, no needed. >>>> >>>> metadata.mfs.back.tmp is the last snapshot, you can rename it to >>>> metadata.mfs and start mfsmaster. >>>> >>>> Some recently modification may been lost. >>>> >>>> On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu<dav...@gm...> > wrote: >>>>> I will try. >>>>> >>>>> On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES >>>>> <seb...@u-...> wrote: >>>>>> The metadata and changelog files are located in the ftp server >>>>>> ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 >>>>>> >>>>>> The login is anonymous. >>>>>> >>>>>> >>>>>> Can you help me ? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 29/11/2011 15:27, Davies Liu wrote: >>>>>>> Could you share the metadata and changelog out ? Then we could >>>>>>> help recover it. >>>>>>> >>>>>>> On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES >>>>>>> <seb...@u-...> wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> I have a serious problem with mfsmaster. The server crashed >>>>>>>> roughly and the mfsmetaloggers are not operate. >>>>>>>> >>>>>>>> With the command mfsmetarestore -a -d /[directory-metadata], i >>>>>>>> have the following messages : >>>>>>>> >>>>>>>> loading names ... loading edge: read error: ENOENT (No such file >>>>>>>> or >>>>>>>> directory) >>>>>>>> error >>>>>>>> >>>>>>>> can't read metadata from file: metadata.mfs.back >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Can you help me please ??? >>>>>>>> It's very very urgent. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> Sébastien >>>>>>>> >>>>>>>> >>>>>>>> ---------------------------------------------------------------- >>>>>>>> -------------- All the data continuously generated in your IT >>>>>>>> infrastructure contains a definitive record of customers, >>>>>>>> application performance, security threats, fraudulent activity, >>>>>>>> and more. Splunk takes this data and makes sense of it. IT >>>>>>>> sense. And common sense. >>>>>>>> http://p.sf.net/sfu/splunk-novd2d >>>>>>>> _______________________________________________ >>>>>>>> moosefs-users mailing list >>>>>>>> moo...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>>>>>>> >>>>> >>>>> -- >>>>> - Davies >>>> >>>> -- >>>> - Davies >>> >>> -- >>> - Davies >> > > ---------------------------------------------------------------------------- > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security threats, > fraudulent activity, and more. Splunk takes this data and makes sense of it. > IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > |
|
From: Michał B. <mic...@ge...> - 2011-11-30 12:39:30
|
Yes, that's right you should use .tmp file. You can use this command: mfsmetarestore -m metadata.mfs.back.tmp -o metadata.mfs changelog.1.mfs changelog.0.mfs Kind regards Michał Borychowski MooseFS Support Manager _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gemius S.A. ul. Wołoska 7, 02-672 Warszawa Budynek MARS, klatka D Tel.: +4822 874-41-00 Fax : +4822 874-41-01 -----Original Message----- From: Sébastien MERTES [mailto:seb...@u-...] Sent: Wednesday, November 30, 2011 11:42 AM To: moo...@li... Subject: Re: [Moosefs-users] problem metadata Thank you very much Davies, it works !!!!! thank you thank you and thank you !!! Sébastien On 30/11/2011 09:48, Davies Liu wrote: > Have you any other metalogger ? > > If they have some recently change logs, it may help. > > On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu<dav...@gm...> wrote: >> If you found changelog.2.mfs, you should: >> >> mv metadata.mfs.back.tmp metadata.mfs.back >> >> mfsmetarestore -a -d /xxx >> >> On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu<dav...@gm...> wrote: >>> I have not found changelog.2.mfs, so can not recover the full data >>> with change logs. >>> changelog.3.mfs are too older, no needed. >>> >>> metadata.mfs.back.tmp is the last snapshot, you can rename it to >>> metadata.mfs and start mfsmaster. >>> >>> Some recently modification may been lost. >>> >>> On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu<dav...@gm...> wrote: >>>> I will try. >>>> >>>> On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES >>>> <seb...@u-...> wrote: >>>>> The metadata and changelog files are located in the ftp server >>>>> ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 >>>>> >>>>> The login is anonymous. >>>>> >>>>> >>>>> Can you help me ? >>>>> >>>>> >>>>> >>>>> >>>>> On 29/11/2011 15:27, Davies Liu wrote: >>>>>> Could you share the metadata and changelog out ? Then we could >>>>>> help recover it. >>>>>> >>>>>> On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES >>>>>> <seb...@u-...> wrote: >>>>>>> Hello, >>>>>>> >>>>>>> I have a serious problem with mfsmaster. The server crashed >>>>>>> roughly and the mfsmetaloggers are not operate. >>>>>>> >>>>>>> With the command mfsmetarestore -a -d /[directory-metadata], i >>>>>>> have the following messages : >>>>>>> >>>>>>> loading names ... loading edge: read error: ENOENT (No such file >>>>>>> or >>>>>>> directory) >>>>>>> error >>>>>>> >>>>>>> can't read metadata from file: metadata.mfs.back >>>>>>> >>>>>>> >>>>>>> >>>>>>> Can you help me please ??? >>>>>>> It's very very urgent. >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> Sébastien >>>>>>> >>>>>>> >>>>>>> ---------------------------------------------------------------- >>>>>>> -------------- All the data continuously generated in your IT >>>>>>> infrastructure contains a definitive record of customers, >>>>>>> application performance, security threats, fraudulent activity, >>>>>>> and more. Splunk takes this data and makes sense of it. IT >>>>>>> sense. And common sense. >>>>>>> http://p.sf.net/sfu/splunk-novd2d >>>>>>> _______________________________________________ >>>>>>> moosefs-users mailing list >>>>>>> moo...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>>>>>> >>>>>> >>>> >>>> >>>> -- >>>> - Davies >>> >>> >>> -- >>> - Davies >> >> >> -- >> - Davies > > ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: <fl...@co...> - 2011-11-30 11:28:16
|
Salut Sébastien, Can you detail to us how did you repair it please ? It could help... Merci :) On Wed, 30 Nov 2011 11:41:55 +0100, Sébastien MERTES wrote: > Thank you very much Davies, it works !!!!! > > thank you thank you and thank you !!! > > Sébastien > > On 30/11/2011 09:48, Davies Liu wrote: > >> Have you any other metalogger ? If they have some recently change logs, it may help. On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu wrote: >> >>> If you found changelog.2.mfs, you should: mv metadata.mfs.back.tmp metadata.mfs.back mfsmetarestore -a -d /xxx On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu wrote: >>> >>>> I have not found changelog.2.mfs, so can not recover the full data with change logs. changelog.3.mfs are too older, no needed. metadata.mfs.back.tmp is the last snapshot, you can rename it to metadata.mfs and start mfsmaster. Some recently modification may been lost. On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu wrote: >>>> >>>>> I will try. On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES wrote: >>>>> >>>>>> The metadata and changelog files are located in the ftp server ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 [5]The login is anonymous. Can you help me ? On 29/11/2011 15:27, Davies Liu wrote: >>>>>> >>>>>>> Could you share the metadata and changelog out ? Then we could help recover it. On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES wrote: >>>>>>> >>>>>>>> Hello, I have a serious problem with mfsmaster. The server crashed roughly and the mfsmetaloggers are not operate. With the command mfsmetarestore -a -d /[directory-metadata], i have the following messages : loading names ... loading edge: read error: ENOENT (No such file or directory) error can't read metadata from file: metadata.mfs.back Can you help me please ??? It's very very urgent. Thank you. Sébastien ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d [1] _______________________________________________ moosefs-users mailing list moo...@li... [2] https://lists.sourceforge.net/lists/listinfo/moosefs-users [3] >>>>> -- - Davies >>>> -- - Davies >>> -- - Davies > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d [10] > _______________________________________________ > moosefs-users mailing list > moo...@li... [11] > https://lists.sourceforge.net/lists/listinfo/moosefs-users [12] Links: ------ [1] http://p.sf.net/sfu/splunk-novd2d [2] mailto:moo...@li... [3] https://lists.sourceforge.net/lists/listinfo/moosefs-users [4] mailto:seb...@u-... [5] http://webmail.coppint.com/ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 [6] mailto:seb...@u-... [7] mailto:dav...@gm... [8] mailto:dav...@gm... [9] mailto:dav...@gm... [10] http://p.sf.net/sfu/splunk-novd2d [11] mailto:moo...@li... [12] https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Sébastien M. <seb...@u-...> - 2011-11-30 10:42:06
|
Thank you very much Davies, it works !!!!! thank you thank you and thank you !!! Sébastien On 30/11/2011 09:48, Davies Liu wrote: > Have you any other metalogger ? > > If they have some recently change logs, it may help. > > On Wed, Nov 30, 2011 at 4:44 PM, Davies Liu<dav...@gm...> wrote: >> If you found changelog.2.mfs, you should: >> >> mv metadata.mfs.back.tmp metadata.mfs.back >> >> mfsmetarestore -a -d /xxx >> >> On Wed, Nov 30, 2011 at 4:43 PM, Davies Liu<dav...@gm...> wrote: >>> I have not found changelog.2.mfs, so can not recover the full data >>> with change logs. >>> changelog.3.mfs are too older, no needed. >>> >>> metadata.mfs.back.tmp is the last snapshot, you can rename it to metadata.mfs >>> and start mfsmaster. >>> >>> Some recently modification may been lost. >>> >>> On Wed, Nov 30, 2011 at 9:50 AM, Davies Liu<dav...@gm...> wrote: >>>> I will try. >>>> >>>> On Tue, Nov 29, 2011 at 11:39 PM, Sébastien MERTES >>>> <seb...@u-...> wrote: >>>>> The metadata and changelog files are located in the ftp server >>>>> ftp://jupiter.u-bourgogne.fr/pub/mfsmaster.tar.bz2 >>>>> >>>>> The login is anonymous. >>>>> >>>>> >>>>> Can you help me ? >>>>> >>>>> >>>>> >>>>> >>>>> On 29/11/2011 15:27, Davies Liu wrote: >>>>>> Could you share the metadata and changelog out ? Then we could help >>>>>> recover it. >>>>>> >>>>>> On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES >>>>>> <seb...@u-...> wrote: >>>>>>> Hello, >>>>>>> >>>>>>> I have a serious problem with mfsmaster. The server crashed roughly and >>>>>>> the mfsmetaloggers are not operate. >>>>>>> >>>>>>> With the command mfsmetarestore -a -d /[directory-metadata], i have the >>>>>>> following messages : >>>>>>> >>>>>>> loading names ... loading edge: read error: ENOENT (No such file or >>>>>>> directory) >>>>>>> error >>>>>>> >>>>>>> can't read metadata from file: metadata.mfs.back >>>>>>> >>>>>>> >>>>>>> >>>>>>> Can you help me please ??? >>>>>>> It's very very urgent. >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> Sébastien >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> All the data continuously generated in your IT infrastructure >>>>>>> contains a definitive record of customers, application performance, >>>>>>> security threats, fraudulent activity, and more. Splunk takes this >>>>>>> data and makes sense of it. IT sense. And common sense. >>>>>>> http://p.sf.net/sfu/splunk-novd2d >>>>>>> _______________________________________________ >>>>>>> moosefs-users mailing list >>>>>>> moo...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>>>>>> >>>>>> >>>> >>>> >>>> -- >>>> - Davies >>> >>> >>> -- >>> - Davies >> >> >> -- >> - Davies > > |
|
From: Michał B. <mic...@ge...> - 2011-11-29 17:40:48
|
Hi! Please send to my email address metadata.mfs.back and changelogs (in tar.gz). And what about metaloggers? They were not running? Kind regards Michał Borychowski MooseFS Support Manager _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gemius S.A. ul. Wołoska 7, 02-672 Warszawa Budynek MARS, klatka D Tel.: +4822 874-41-00 Fax : +4822 874-41-01 From: Sébastien MERTES [mailto:seb...@u-...] Sent: Tuesday, November 29, 2011 3:22 PM To: moo...@li... Subject: Re: [Moosefs-users] problem metadata The moosefs version is 1.6.20. The msfmaster's operating system is FreeBSD and chunkserver also. The files system is ZFS. The client is Linux. On 29/11/2011 15:09, Sébastien MERTES wrote: Hello, I have a serious problem with mfsmaster. The server crashed roughly and the mfsmetaloggers are not operate. With the command mfsmetarestore -a -d /[directory-metadata], i have the following messages : loading names ... loading edge: read error: ENOENT (No such file or directory) error can't read metadata from file: metadata.mfs.back Can you help me please ??? It's very very urgent. Thank you. Sébastien ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Fabien G. <fab...@gm...> - 2011-11-29 15:53:06
|
Bonjour Sébastien, On Tue, Nov 29, 2011 at 3:09 PM, Sébastien MERTES < seb...@u-...> wrote: > Hello, > > I have a serious problem with mfsmaster. The server crashed roughly and > the mfsmetaloggers are not operate. > > With the command mfsmetarestore -a -d /[directory-metadata], i have the > following messages : > * > loading names ... loading edge: read error: ENOENT (No such file or > directory) > error > > can't read metadata from file: metadata.mfs.back* > Can you share (a simple "ls -l") the content of the metadata directory, and the exact mfsmetarestore command you launched ? Fabien |
|
From: Davies L. <dav...@gm...> - 2011-11-29 14:32:53
|
Could you share the metadata and changelog out ? Then we could help recover it. On Tue, Nov 29, 2011 at 10:09 PM, Sébastien MERTES <seb...@u-...> wrote: > Hello, > > I have a serious problem with mfsmaster. The server crashed roughly and > the mfsmetaloggers are not operate. > > With the command mfsmetarestore -a -d /[directory-metadata], i have the > following messages : > > loading names ... loading edge: read error: ENOENT (No such file or > directory) > error > > can't read metadata from file: metadata.mfs.back > > > > Can you help me please ??? > It's very very urgent. > > Thank you. > > Sébastien > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > -- - Davies |
|
From: Sébastien M. <seb...@u-...> - 2011-11-29 14:21:51
|
The moosefs version is 1.6.20. The msfmaster's operating system is FreeBSD and chunkserver also. The files system is ZFS. The client is Linux. On 29/11/2011 15:09, Sébastien MERTES wrote: > Hello, > > I have a serious problem with mfsmaster. The server crashed roughly > and the mfsmetaloggers are not operate. > > With the command mfsmetarestore -a -d /[directory-metadata], i have > the following messages : > * > loading names ... loading edge: read error: ENOENT (No such file or > directory) > error > > can't read metadata from file: metadata.mfs.back* > > > > Can you help me please ??? > It's very very urgent. > > Thank you. > > Sébastien > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > > > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Sébastien M. <seb...@u-...> - 2011-11-29 14:09:39
|
Hello, I have a serious problem with mfsmaster. The server crashed roughly and the mfsmetaloggers are not operate. With the command mfsmetarestore -a -d /[directory-metadata], i have the following messages : * loading names ... loading edge: read error: ENOENT (No such file or directory) error can't read metadata from file: metadata.mfs.back* Can you help me please ??? It's very very urgent. Thank you. Sébastien |
|
From: Jie H. <hao...@gm...> - 2011-11-29 07:29:42
|
Hi, I want to study the source code in detail. Is there any detailed document for the source code of the MooseFS ? Thanks! Jack |
|
From: Sébastien M. <seb...@gm...> - 2011-11-22 13:53:06
|
Hi, I have a problem with permission in my moosefs. I'm mounting the system this way: mfsmount /mnt/storage fuse mfsmaster=mfsmaster,_netdev 0 0 Then here is the problem : $ cd /mnt/storage/files $ ls -l total 1 drwxrws--- 11 informatique informatique 42 Nov 22 07:53 informatique $ cd informatique $ ls ls: cannot open directory .: Permission denied $ groups sebastien cdrom floppy audio users informatique What is the problem? I'm in the correct group but I can't access to data. Thanks by advance, Sébastien |
|
From: Ricardo J. B. <ric...@da...> - 2011-11-18 15:45:49
|
El Jue 17 Noviembre 2011, hussein ismail escribió: > Hi, > > I would like to know, is it possible to set up global moosefs system, in > which chunkservers are spread globally (for example spread in europe and > china or other places)? and related question, when a client requests data, > will he receive from the closest chuckserver (for example if the client is > in china and there is a chunkserver in china, will receive the data from > that server)? > > Thank you very much > > Br, > Hussein Travis gave an excellent explanation and recommended Coda. I'd also like to point you to XtreemFS (http://www.xtreemfs.org/) which migth be of interest to you. Note that I haven't tested XtreemFS because MFS serves my purposes well. Regards, -- Ricardo J. Barberis Senior SysAdmin / ITI Dattatec.com :: Soluciones de Web Hosting Tu Hosting hecho Simple! ------------------------------------------ |
|
From: Robert S. <rsa...@ne...> - 2011-11-18 14:03:19
|
I have written quite a few emails on this list about this specific subject. Fuse only seems to be a limitation if you use asynchronous I/O like sendfile(). Both Samba and Apache defaults to using sendfile(). At this stage my best guess is that this limit is due to the single socket between the mfsmount and mfsmaster instances that are re-used by everything. In my production environment I have worked around the problem by having multiple mounts per server of the same volume and then load-balancing between the mounts. The next limit seems to be that mfschunkserver will only process about 10 requests at a time from all the different mfsmount instances. If you don't have a large number of mfschunkserver instances or you have mfschunkserver instances that control a large number of spindles then it can also become a bottleneck. Robert On 11/16/11 2:56 PM, Yezhou Fang wrote: > I found out if I mount about twenty mount point in a server each has > about 50 concurrent connections of read will get much better > performance than only mount one which has about 500 connections . Does > it because fuse is single process. It can not handle too many > concurrent connections? > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Travis H. <tra...@tr...> - 2011-11-18 13:39:40
|
Although that sounds like a neat idea, in practice, this would probably
be a very slow user experience.
The first technical challenge is the connected TCP socket nature of the
protocol. We would require up to (4) TCP port numbers to be open to the
Internet, and possibly firewalled so that only the set of master server,
chunk server and metadata servers could access these:
* TCP port 9429 (MATOML) : Master server to meta logger servers. This
port needs to be opened on the mfsmaster machine if we wish to have
the metalogger machines connect.
* TCP port 9420 (MATOCS) : Master server to chunk servers. This port
needs to be opened on the mfsmaster machine for the chunk servers to
connect.
* TCP port 9421 (MATOCU) : Master server to clients. This port needs
to be opened on the mfsmaster machine for the mfsmount clients to
connect.
* TCP port 9422 (CSSERV)
: Chunk servers to clients. This port needs to be opened on the
chunkserver machines for the mfsmount clients to connect.
Additionally, the protocol kind of expects the chunk servers maintain a
connection to the master server. The nature of the internet in general
is not reliable enough to ensure this (e.g. not just always possible to
keep it plugged in all the time everywhere like a local switch in a LAN
environment
Additionally, the MFS protocol does not have the concept of location or
geographic awareness yet. so it would not be possible for it to know
which was the closest chunkserver.
So technical problems aside, I had found very slow and unuseable
performance when trying to mount mfsmount over my local city internet
even, between my office and my house. What I have found works better is
to mfsmount client on a machine in the same network where the master and
chunk servers are and then from remotely SSHFS connect to this.
I would say if you want to use moosefs, then to have individual
installations in each regional area, and then have some other front end
file share or access mechanism, such as Samba, HTTP, FTP, SSHFS facing
the internet. Where you would either need to have a mechanism to
replicate and synchronize contents between data centers, or just adopt a
convention that some content is only available from some mirror sites
If you are really interested in having file system level multi site
spread over large areas, perhaps have a look at the coda file system. it
aims to be more of a distributed file system rather than a cluster file
system, where by it Coda supports disconnected pieces and remote sites
like you were looking for better. I am sure you could likely even run
Coda on top of a moosefs installation.
On 11-11-17 2:02 PM, hussein ismail wrote:
> Hi,
>
> I would like to know, is it possible to set up global moosefs system, in
> which chunkservers are spread globally (for example spread in europe and
> china or other places)? and related question, when a client requests data,
> will he receive from the closest chuckserver (for example if the client is
> in china and there is a chunkserver in china, will receive the data from
> that server)?
>
> Thank you very much
>
> Br,
> Hussein
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
>
>
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
|
|
From: Alexander A. <akh...@ri...> - 2011-11-18 09:26:02
|
Hi All ! I found by enumeration of possibilities method that sending SINHUP to mfsmetalogger forces it to reread whole metadata file from master and sending SIGTERM to terminate mfsmetalogger. Is there somewhere documented all signals to all MooseFS daemons? Preferably it should be present in man pages. Thanks! wbr Alexander |
|
From: Michał B. <mic...@ge...> - 2011-11-18 08:15:45
|
Hi! Please see http://www.moosefs.org/moosefs-faq.html#writeworker Kind regards Michał Borychowski MooseFS Support Manager _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gemius S.A. ul. Wołoska 7, 02-672 Warszawa Budynek MARS, klatka D Tel.: +4822 874-41-00 Fax : +4822 874-41-01 -----Original Message----- From: Alexander Akhobadze [mailto:akh...@ri...] Sent: Friday, November 18, 2011 6:46 AM To: moo...@li... Subject: [Moosefs-users] mfsmount unfinished writes Hi All ! I see in my syslog a lot of this like records: Nov 18 09:37:18 myhostname mfsmount[1072]: file: 14465, index: 0, chunk: 26804776, version: 3 - writeworker: connection with (C0A8CE06:9422) was timed out (unfinished writes: 2; try counter: 1) What does it mean ? Is it indicates something critical? wbr Alexander ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
|
From: Alexander A. <akh...@ri...> - 2011-11-18 06:03:35
|
Hi All ! I see in my syslog a lot of this like records: Nov 18 09:37:18 myhostname mfsmount[1072]: file: 14465, index: 0, chunk: 26804776, version: 3 - writeworker: connection with (C0A8CE06:9422) was timed out (unfinished writes: 2; try counter: 1) What does it mean ? Is it indicates something critical? wbr Alexander |
84 messages has been excluded from this view by a project administrator.
