moosefs-users — Mailing list for MooseFS Users

[Moosefs-users] Disaster Recovery plans

[Brandon F. <bra...@li...>]

Hi all,
I was just curious how you all handle disaster recovery. I know that there
is a metalogger process on a different machine constantly backing the meta
data, and the having multiple copies of files makes it so that if a chunk
server dies mfs will auto replicate to recover the data it was storing.
Is there any kind of option for multi-site data replication? I'd feel a lot
safer if I could have a 2 mfs clusters in constant sync in to different
locations.

-- 
Brandon Foster

Infrastructure Administrator
Liferay, Inc.
Enterprise. Open Source. For life.
(831) 682-5730
skype: brandon.foster-liferay.com
aim: bra...@li...

Re: [Moosefs-users] Got poor performance

[Rashit A. <ras...@ya...>]

I personally prefer tiobench, here some sample results:
root@w32:/moosefs2# tiobench --size 98304 --numruns 3
Run #3: /usr/bin/tiotest -t 8 -f 12288 -r 500 -b 4096 -d . -TT

Unit information
================
File size = megabytes
Blk Size  = bytes
Rate      = megabytes per second
CPU%      = percentage of CPU used during the test
Latency   = milliseconds
Lat%      = percent of requests that took longer than X seconds
CPU Eff   = Rate divided by CPU% - throughput per cpu load

Sequential Reads
                              File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
3.5.0-23-generic             98304  4096    1   52.73 4.532%     0.222    10054.22   0.00007  0.00000  1163
3.5.0-23-generic             98304  4096    2   90.04 15.40%     0.257     8034.65   0.00003  0.00000   585
3.5.0-23-generic             98304  4096    4  114.08 37.06%     0.406     7910.71   0.00002  0.00000   308
3.5.0-23-generic             98304  4096    8  105.17 72.93%     0.881     6378.89   0.00007  0.00000   144

Random Reads
                              File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
3.5.0-23-generic             98304  4096    1    0.37 0.050%    31.956     5102.46   0.02500  0.00000   732
3.5.0-23-generic             98304  4096    2    0.71 0.121%    29.068     6468.06   0.02500  0.00000   586
3.5.0-23-generic             98304  4096    4    1.23 0.345%    30.017     5379.65   0.02500  0.00000   355
3.5.0-23-generic             98304  4096    8    1.49 1.092%    55.224     6271.60   0.22500  0.00000   136

Sequential Writes
                              File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
3.5.0-23-generic             98304  4096    1   70.34 19.92%     0.166     8445.44   0.00002  0.00000   353
3.5.0-23-generic             98304  4096    2   78.56 55.84%     0.298    10029.74   0.00006  0.00000   141
3.5.0-23-generic             98304  4096    4   79.40 139.3%     0.587     7589.39   0.00003  0.00000    57
3.5.0-23-generic             98304  4096    8   68.87 290.3%     1.351     7199.68   0.00004  0.00000    24

Random Writes
                              File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
3.5.0-23-generic             98304  4096    1    0.19 0.428%    53.208     9748.45   0.10000  0.00000    45
3.5.0-23-generic             98304  4096    2    0.28 0.057%    66.149     9146.20   0.17500  0.00000   488
3.5.0-23-generic             98304  4096    4    0.27 0.100%   125.207    11383.82   0.42500  0.00000   266
3.5.0-23-generic             98304  4096    8    0.26 0.126%   215.600     6165.20   0.27500  0.00000   209

20.10.2014, 20:22, "Joseph Love" <jo...@ge...>:
> Out of curiosity, does anyone have any recommended testing utilities?  I’ve been using iozone & dd for testing, before having a chance to throw a normal workload at it.  I did find iozone’s to perform fantastically with larger files & block sizes, but it seemed to be a bit hard to gauge as if it’s affected by local caching.  (transfer rates 5x the throughput of 10gbe is a little hard to believe.)  Performance with dd always seemed to be a bit dismal, no matter what settings I handed it.
>
> I’ve been looking to throw a sample workload at it and just see what the usage and response seems to be like, but I’ve been running into time constraints lately and haven’t had time to experiment.  But my performance always seemed to be more like dd, and less like iozone: a bit lacking.  I sort of blame this on the FreeBSD 10 FUSE client, but haven’t had much chance to try the linux version.  (I’m not much of a linux user.)  The mac client seemed to perform very well, though.
>
> -Joe
>>  On Oct 20, 2014, at 4:00 AM, Aleksander Wieliczko <ale...@co...> wrote:
>>
>>  Hi Yves
>>  We are very glad that You are using MooseFS distributed file system.
>>
>>  First of all we strongly recommended to update your instance to MooseFS
>>  2.0.40-1 version.
>>  We fixed some bugs and add many new algorithms. All this make MooseFS
>>  2.0 faster and provide better stability to cluster.
>>>  From description it appears that your LAN connection is getting only 76%
>>  bandwidth of 1Gb LAN.
>>  Can you check if you have any errors, dropped frames in INC interface?
>>
>>  MooseFS is much more sensitive on LAN problems than nc.
>>  MooseFS need to communicate not only to one computer, but to master,
>>  chunkservers and clients, so this operations generating much more TCP
>>  traffic than one to one connection.
>>
>>  By the way.
>>  We have similar configuration (8GB RAM, SATA 7200 RPM HDD, 1Gb LAN) in
>>  our development environment and we getting results for GOAL2
>>  read: 80MB/s and write: 50MB/s
>>
>>  Can you send some more informations about this tests, and what software
>>  are you using to measure the MooseFS speed.
>>
>>  Best regards
>>  Aleksander Wieliczko
>>  Technical Support Engineer
>>  moosefs.com
>>
>>  On 10/18/2014 12:22 PM, "Yves Réveillon - eurower.fr" wrote:
>>>  Hi everybody,
>>>
>>>  I got poor performance with MooseFS :s
>>>
>>>  This is my test :
>>>
>>>  3 servers with on each :
>>>  - 6 core AMD FX-6300 3,5 Ghz
>>>  - 8 Go RAM
>>>  - sata disk 6Gbps with no raid
>>>  - gigabyte LAN
>>>
>>>  The switch is a HP Gigabyte, with CAT 6
>>>
>>>  1 server is the mfsmaster
>>>  3 servers are chunkservers
>>>
>>>  Tests with a tmpfs randomly data of 1 Go :
>>>
>>>  Bandwidth beetween 2 server with ncat : 780 Mbps
>>>  Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)
>>>
>>>  MooseFS 1.6.27 with 2x replication goal :
>>>  Bandwidth : 85 Mbps (10.6 MB/s).
>>>
>>>  During test, RAM is good, no production on theses servers (no activity)
>>>  and CPU is enought (less than 20%)
>>>
>>>  Network and HDD not seems to be a bottleneck, so do you have any idea of
>>>  why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?
>>>
>>>  Thanks you
>>>
>>>  Yves
>>>
>>>  ------------------------------------------------------------------------------
>>>  Comprehensive Server Monitoring with Site24x7.
>>>  Monitor 10 servers for $9/Month.
>>>  Get alerted through email, SMS, voice calls or mobile push notifications.
>>>  Take corrective actions from your mobile device.
>>>  http://p.sf.net/sfu/Zoho
>>>  _______________________________________________
>>>  moosefs-users mailing list
>>>  moo...@li...
>>>  https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>  ------------------------------------------------------------------------------
>>  Comprehensive Server Monitoring with Site24x7.
>>  Monitor 10 servers for $9/Month.
>>  Get alerted through email, SMS, voice calls or mobile push notifications.
>>  Take corrective actions from your mobile device.
>>  http://p.sf.net/sfu/Zoho
>>  _______________________________________________
>>  moosefs-users mailing list
>>  moo...@li...
>>  https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [Moosefs-users] Got poor performance

[Joseph L. <jo...@ge...>]

Out of curiosity, does anyone have any recommended testing utilities?  I’ve been using iozone & dd for testing, before having a chance to throw a normal workload at it.  I did find iozone’s to perform fantastically with larger files & block sizes, but it seemed to be a bit hard to gauge as if it’s affected by local caching.  (transfer rates 5x the throughput of 10gbe is a little hard to believe.)  Performance with dd always seemed to be a bit dismal, no matter what settings I handed it.

I’ve been looking to throw a sample workload at it and just see what the usage and response seems to be like, but I’ve been running into time constraints lately and haven’t had time to experiment.  But my performance always seemed to be more like dd, and less like iozone: a bit lacking.  I sort of blame this on the FreeBSD 10 FUSE client, but haven’t had much chance to try the linux version.  (I’m not much of a linux user.)  The mac client seemed to perform very well, though.

-Joe

> On Oct 20, 2014, at 4:00 AM, Aleksander Wieliczko <ale...@co...> wrote:
> 
> Hi Yves
> We are very glad that You are using MooseFS distributed file system.
> 
> First of all we strongly recommended to update your instance to MooseFS
> 2.0.40-1 version.
> We fixed some bugs and add many new algorithms. All this make MooseFS
> 2.0 faster and provide better stability to cluster.
> 
>> From description it appears that your LAN connection is getting only 76%
> bandwidth of 1Gb LAN.
> Can you check if you have any errors, dropped frames in INC interface?
> 
> MooseFS is much more sensitive on LAN problems than nc.
> MooseFS need to communicate not only to one computer, but to master,
> chunkservers and clients, so this operations generating much more TCP
> traffic than one to one connection.
> 
> By the way.
> We have similar configuration (8GB RAM, SATA 7200 RPM HDD, 1Gb LAN) in
> our development environment and we getting results for GOAL2
> read: 80MB/s and write: 50MB/s
> 
> Can you send some more informations about this tests, and what software
> are you using to measure the MooseFS speed.
> 
> Best regards
> Aleksander Wieliczko
> Technical Support Engineer
> moosefs.com
> 
> On 10/18/2014 12:22 PM, "Yves Réveillon - eurower.fr" wrote:
>> Hi everybody,
>> 
>> I got poor performance with MooseFS :s
>> 
>> This is my test :
>> 
>> 3 servers with on each :
>> - 6 core AMD FX-6300 3,5 Ghz
>> - 8 Go RAM
>> - sata disk 6Gbps with no raid
>> - gigabyte LAN
>> 
>> The switch is a HP Gigabyte, with CAT 6
>> 
>> 1 server is the mfsmaster
>> 3 servers are chunkservers
>> 
>> Tests with a tmpfs randomly data of 1 Go :
>> 
>> Bandwidth beetween 2 server with ncat : 780 Mbps
>> Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)
>> 
>> MooseFS 1.6.27 with 2x replication goal :
>> Bandwidth : 85 Mbps (10.6 MB/s).
>> 
>> During test, RAM is good, no production on theses servers (no activity)
>> and CPU is enought (less than 20%)
>> 
>> Network and HDD not seems to be a bottleneck, so do you have any idea of
>> why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?
>> 
>> Thanks you
>> 
>> Yves
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Comprehensive Server Monitoring with Site24x7.
>> Monitor 10 servers for $9/Month.
>> Get alerted through email, SMS, voice calls or mobile push notifications.
>> Take corrective actions from your mobile device.
>> http://p.sf.net/sfu/Zoho
>> _______________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
> 
> 
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
> 

Re: [Moosefs-users] Got poor performance

[Aleksander W. <ale...@co...>]

Hi Yves
We are very glad that You are using MooseFS distributed file system.

First of all we strongly recommended to update your instance to MooseFS
2.0.40-1 version.
We fixed some bugs and add many new algorithms. All this make MooseFS
2.0 faster and provide better stability to cluster.

>From description it appears that your LAN connection is getting only 76%
bandwidth of 1Gb LAN.
Can you check if you have any errors, dropped frames in INC interface?

MooseFS is much more sensitive on LAN problems than nc.
MooseFS need to communicate not only to one computer, but to master,
chunkservers and clients, so this operations generating much more TCP
traffic than one to one connection.

By the way.
We have similar configuration (8GB RAM, SATA 7200 RPM HDD, 1Gb LAN) in
our development environment and we getting results for GOAL2
read: 80MB/s and write: 50MB/s

Can you send some more informations about this tests, and what software
are you using to measure the MooseFS speed.

Best regards
Aleksander Wieliczko
Technical Support Engineer
moosefs.com

On 10/18/2014 12:22 PM, "Yves Réveillon - eurower.fr" wrote:
> Hi everybody,
>
> I got poor performance with MooseFS :s
>
> This is my test :
>
> 3 servers with on each :
> - 6 core AMD FX-6300 3,5 Ghz
> - 8 Go RAM
> - sata disk 6Gbps with no raid
> - gigabyte LAN
>
> The switch is a HP Gigabyte, with CAT 6
>
> 1 server is the mfsmaster
> 3 servers are chunkservers
>
> Tests with a tmpfs randomly data of 1 Go :
>
> Bandwidth beetween 2 server with ncat : 780 Mbps
> Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)
>
> MooseFS 1.6.27 with 2x replication goal :
> Bandwidth : 85 Mbps (10.6 MB/s).
>
> During test, RAM is good, no production on theses servers (no activity)
> and CPU is enought (less than 20%)
>
> Network and HDD not seems to be a bottleneck, so do you have any idea of
> why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?
>
> Thanks you
>
> Yves
>
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

Re: [MooseFS-users] [Moosefs-users] Got poor performance

[Przemysław H. <prz...@gm...>]

Make sure jumbo frames are enabled, as you'll avoid extra overhead due to unnecessary fragmentation. 

Because MooseFS operates on 64MB chunks as a basic unit for a filesystem 'transaction' (excuse my brevity), the fragmentation overhead can grow up enormously, especially (but not only) when replicating missing chunks after a chunkserver goes down.

Running MooseFS on dedicated network has also one great benefit - you can easily monitor, how the system performs :)

Pozdrawiam,

Przemysław Hejman
e-mail: prz...@gm...
GSM: (+48) 883-680-038

> Wiadomość napisana przez Yves Réveillon - eurower.fr <yve...@eu...> w dniu 18 paź 2014, o godz. 15:18:
> 
> Hi,
> 
> in fact I have not yet set the jumbo frame because the network speed is
> 780 Mbps.
> 
> I think (maybe I'm wrong) that if the network without jumbo is 780 Mbps
> (97 MB/s) so the bandwith for moosefs can reach this value (so be > 10.6
> MB/s) without the need of jumbo.
> 
> MFS is on a DHCP network, but it's week-end so no users traffic.
> 
> Thanks
> 
> Yves
> 
> 
> Przemysław Hejman a écrit :
>> Hi,
>> 
>> just in order to make a networking side clear:
>> 
>> Have you enabled jumbo frames on ethernet layer?
>> Are you running MFS on separate network (without DHCP, users traffic,
>> etc)?
>> 
>> Pozdrawiam,
>> 
>> Przemysław Hejman
>> e-mail: prz...@gm... <mailto:prz...@gm...> <mailto:prz...@gm... <mailto:prz...@gm...>>
>> GSM: (+48) 883-680-038
>> 
>>> Wiadomość napisana przez Yves Réveillon - eurower.fr <http://eurower.fr/>
>>> <http://eurower.fr <http://eurower.fr/>> <yve...@eu... <mailto:yve...@eu...>
>>> <mailto:yve...@eu... <mailto:yve...@eu...>>> w dniu 18 paź 2014, o godz. 12:22:
>>> 
>>> Hi everybody,
>>> 
>>> I got poor performance with MooseFS :s
>>> 
>>> This is my test :
>>> 
>>> 3 servers with on each :
>>> - 6 core AMD FX-6300 3,5 Ghz
>>> - 8 Go RAM
>>> - sata disk 6Gbps with no raid
>>> - gigabyte LAN
>>> 
>>> The switch is a HP Gigabyte, with CAT 6
>>> 
>>> 1 server is the mfsmaster
>>> 3 servers are chunkservers
>>> 
>>> Tests with a tmpfs randomly data of 1 Go :
>>> 
>>> Bandwidth beetween 2 server with ncat : 780 Mbps
>>> Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)
>>> 
>>> MooseFS 1.6.27 with 2x replication goal :
>>> Bandwidth : 85 Mbps (10.6 MB/s).
>>> 
>>> During test, RAM is good, no production on theses servers (no activity)
>>> and CPU is enought (less than 20%)
>>> 
>>> Network and HDD not seems to be a bottleneck, so do you have any idea of
>>> why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?
>>> 
>>> Thanks you
>>> 
>>> Yves
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Comprehensive Server Monitoring with Site24x7.
>>> Monitor 10 servers for $9/Month.
>>> Get alerted through email, SMS, voice calls or mobile push notifications.
>>> Take corrective actions from your mobile device.
>>> http://p.sf.net/sfu/Zoho
>>> _______________________________________________
>>> moosefs-users mailing list
>>> moo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>> 
>> 
> 
> -- 
> 
> Cordialement,
> 
> .........................................................
> *Yves Réveillon*
> Gérant
> Tél. : +33 (0)4 86 68 9001
> Fax. : +33 (0)4 86 68 9002
> 
> *eurower.fr <http://eurower.fr/>*
> http://www.eurower.fr <http://www.eurower.fr/>
> yve...@eu... <mailto:yve...@eu...>
> 
> *****
> Pour tout incident ou support ne faisant pas l'objet d'un contrat
> _mensuel_ avec assistance téléphonique incluse :
> *0892 430 830*
> 
> 
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho <http://p.sf.net/sfu/Zoho>
> _______________________________________________
> moosefs-users mailing list
> moo...@li... <mailto:moo...@li...>
> https://lists.sourceforge.net/lists/listinfo/moosefs-users <https://lists.sourceforge.net/lists/listinfo/moosefs-users>

Re: [Moosefs-users] Got poor performance

[Yves R. - eurower.f. <yve...@eu...>]

Hi,

in fact I have not yet set the jumbo frame because the network speed is
780 Mbps.

I think (maybe I'm wrong) that if the network without jumbo is 780 Mbps
(97 MB/s) so the bandwith for moosefs can reach this value (so be > 10.6
MB/s) without the need of jumbo.

MFS is on a DHCP network, but it's week-end so no users traffic.

Thanks

Yves


Przemysław Hejman a écrit :
> Hi,
>
> just in order to make a networking side clear:
>
> Have you enabled jumbo frames on ethernet layer?
> Are you running MFS on separate network (without DHCP, users traffic,
> etc)?
>
> Pozdrawiam,
>
> Przemysław Hejman
> e-mail: prz...@gm... <mailto:prz...@gm...>
> GSM: (+48) 883-680-038
>
>> Wiadomość napisana przez Yves Réveillon - eurower.fr
>> <http://eurower.fr> <yve...@eu...
>> <mailto:yve...@eu...>> w dniu 18 paź 2014, o godz. 12:22:
>>
>> Hi everybody,
>>
>> I got poor performance with MooseFS :s
>>
>> This is my test :
>>
>> 3 servers with on each :
>> - 6 core AMD FX-6300 3,5 Ghz
>> - 8 Go RAM
>> - sata disk 6Gbps with no raid
>> - gigabyte LAN
>>
>> The switch is a HP Gigabyte, with CAT 6
>>
>> 1 server is the mfsmaster
>> 3 servers are chunkservers
>>
>> Tests with a tmpfs randomly data of 1 Go :
>>
>> Bandwidth beetween 2 server with ncat : 780 Mbps
>> Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)
>>
>> MooseFS 1.6.27 with 2x replication goal :
>> Bandwidth : 85 Mbps (10.6 MB/s).
>>
>> During test, RAM is good, no production on theses servers (no activity)
>> and CPU is enought (less than 20%)
>>
>> Network and HDD not seems to be a bottleneck, so do you have any idea of
>> why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?
>>
>> Thanks you
>>
>> Yves
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Comprehensive Server Monitoring with Site24x7.
>> Monitor 10 servers for $9/Month.
>> Get alerted through email, SMS, voice calls or mobile push notifications.
>> Take corrective actions from your mobile device.
>> http://p.sf.net/sfu/Zoho
>> _______________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>

-- 

Cordialement,

.........................................................
*Yves Réveillon*
Gérant
Tél. : +33 (0)4 86 68 9001
Fax. : +33 (0)4 86 68 9002
 
*eurower.fr*
http://www.eurower.fr
yve...@eu...

*****
Pour tout incident ou support ne faisant pas l'objet d'un contrat
_mensuel_ avec assistance téléphonique incluse :
*0892 430 830*

Re: [MooseFS-users] [Moosefs-users] Got poor performance

[Przemysław H. <prz...@gm...>]

Hi,

just in order to make a networking side clear:

Have you enabled jumbo frames on ethernet layer?
Are you running MFS on separate network (without DHCP, users traffic, etc)?

Pozdrawiam,

Przemysław Hejman
e-mail: prz...@gm...
GSM: (+48) 883-680-038

> Wiadomość napisana przez Yves Réveillon - eurower.fr <yve...@eu...> w dniu 18 paź 2014, o godz. 12:22:
> 
> Hi everybody,
> 
> I got poor performance with MooseFS :s
> 
> This is my test :
> 
> 3 servers with on each :
> - 6 core AMD FX-6300 3,5 Ghz
> - 8 Go RAM
> - sata disk 6Gbps with no raid
> - gigabyte LAN
> 
> The switch is a HP Gigabyte, with CAT 6
> 
> 1 server is the mfsmaster
> 3 servers are chunkservers
> 
> Tests with a tmpfs randomly data of 1 Go :
> 
> Bandwidth beetween 2 server with ncat : 780 Mbps
> Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)
> 
> MooseFS 1.6.27 with 2x replication goal :
> Bandwidth : 85 Mbps (10.6 MB/s).
> 
> During test, RAM is good, no production on theses servers (no activity)
> and CPU is enought (less than 20%)
> 
> Network and HDD not seems to be a bottleneck, so do you have any idea of
> why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?
> 
> Thanks you
> 
> Yves
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
> 

[Moosefs-users] Got poor performance

[Yves R. - eurower.f. <yve...@eu...>]

Hi everybody,

I got poor performance with MooseFS :s

This is my test :

3 servers with on each :
- 6 core AMD FX-6300 3,5 Ghz
- 8 Go RAM
- sata disk 6Gbps with no raid
- gigabyte LAN

The switch is a HP Gigabyte, with CAT 6

1 server is the mfsmaster
3 servers are chunkservers

Tests with a tmpfs randomly data of 1 Go :

Bandwidth beetween 2 server with ncat : 780 Mbps
Bandwitdh to write to a single sata (RAID-less) : 2593 Mbps (324 MB/s)

MooseFS 1.6.27 with 2x replication goal :
Bandwidth : 85 Mbps (10.6 MB/s).

During test, RAM is good, no production on theses servers (no activity)
and CPU is enought (less than 20%)

Network and HDD not seems to be a bottleneck, so do you have any idea of
why I have 10.6 MB/s and not 20 or 30 MB/s as announced ?

Thanks you

Yves

[MooseFS-users] slow speed rw

[Eugene D. <it...@da...>]

Hi,

I have an issue with moose-fs. Using latest CE version. I have two 
server's, powerfull enough.
When I copy big files (~100MB) to MFS I have speed around 5 MiB. When I 
am reading from MFS I have around 4 MiB.

But.. it is strange. When I run at the same time 4-5 processes, each of 
them can copy with speed 5 MiB/sec.
Why I can't copy files with maximum speed around 20-30 MiB?

I test speed connection between cliend and chunk server, it is around 
900 Mbit.


-- 
Best regards,
Eugene Diatlov

Re: [Moosefs-users] how to set quota in CE2.0.39 version

[Piotr R. K. <pio...@mo...>]

Hello,
first of all you need to enable setting quota by user: in MooseFS 2.0.x "admin" flag has been introduced instead of "canchangequota" in mfsexports.cfg.

So e.g. if you want to allow using whole filesystem in read-write mode and setting quota for all users from 192.168.1.0/24 subnet, you need to add to mfsexports.cfg:

192.168.1.0/24         /       rw,admin

In case of any further questions, don't hesitate to contact me.

-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer*
pio...@mo...[1] | moosefs.com[2] 


> hi all,
> 
>     I have just upgrade MFS from 1.6.27-5 to 2.0.39, need to set quota to a directory but failed. like this:
> 
> # /usr/bin/mfssetquota -s 3500 db
> db: Operation not permitted
> # /usr/bin/mfssetgoal 3 db
> db: 3
> 
> have I missed anything? I couldn't found any else setting in menu. 
> 
> Thinks a lot for any suggestions!!
> 
> 
>  Burke.Xie
> 2014.10.14
> 
> 
> 
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users


--------
[1] mailto:pio...@mo...
[2] http://moosefs.com

[Moosefs-users] how to set quota in CE2.0.39 version

[谢. <xz...@yo...>]

hi all,

    I have just upgrade MFS from 1.6.27-5 to 2.0.39, need to set quota to a directory but failed. like this:

# /usr/bin/mfssetquota -s 3500 db
db: Operation not permitted
# /usr/bin/mfssetgoal 3 db
db: 3

have I missed anything? I couldn't found any else setting in menu. 

Thinks a lot for any suggestions!!


 Burke.Xie
2014.10.14

[MooseFS-users] IPv6

[Юрий М. <l2...@ya...>]

Hello!

I wanna wonder, does MooseFS supports IPv6?

Best regards, Yuri.

[Moosefs-users] MooseFS 2.0.39-1 released.

[Krzysztof K. <krz...@mo...>]

Dear MooseFS Users,


We are proud to announce the release of the new MooseFS version 2.0.39-1. The list of changes introduced by this version compared to previous public release (2.0.34-1) includes:


* MooseFS 2.0.39-1 (2014-10-06)
   - (mfsmount) added ability to mount from /etc/fstab on FreeBSD


* MooseFS 2.0.38-1 (2014-10-02)
  - (mfsmount) fixed memory leak in workaround on FreeBSD early-release bug (FreeBSD only)


* MooseFS 2.0.37-1 (2014-09-23)
  - (mfschunkserver) added internal open files limit
  - (mfsmaster) changed chunkserver choosing algorithm


* MooseFS 2.0.36-1 (2014-09-18)
  - (mfscgi) fixed sorting masters by IP
  - (mfsmaster) fixed ACL POSIX compatibility
  - (mfschunkserver) fixed compatibility issues with master 1.6


* MooseFS 2.0.35-1 (2014-09-12)
  - (freebsd) fixed cgiserv and cli port
  - (mfsmount) fixed setting cal


We have also introduced a new structure to our official PPA for MooseFS, so it's now possible to point the OS Package Managers to URL for specific MooseFS version, or to a special branch called stable or current. For a detailed instructions on how to configure your favorite Package Manager please refer to the documentation on our website at http://get.moosefs.com


Best Regards,
Krzysztof Kielak
Director of Operations and Customer Support
Mobile: +48 601 476 440

Re: [Moosefs-users] FreeBSD fstab entry

[Joseph L. <jo...@ge...>]

That works.

Thank you, Piotr.

-Joe

On Oct 6, 2014, at 7:20 AM, Piotr Robert Konopelko <pio...@mo...> wrote:

> Hello,
> firstly you need to update to MooseFS 2.0.39-1.
> Packages repository is available at http://get.moosefs.com (please select "FreeBSD" in left menu).
>  
> The entry in /etc/fstab/ should look as presented below:
>  
> mfsmount_magic	/mnt/mfs	moosefs	rw,mfsmaster=MASTER_HOST,mountprog=/usr/local/bin/mfsmount,late	0	0
>  
> where MASTER_HOST = your Master Server name, e.g. mfsmaster.mfs.lan.
>  
> It has been tested both on FreeBSD 10.0 and 9.3.
>  
> In case of any further questions don't hesitate to contact me.
>  
> -- 
> Best regards,
> Piotr Robert Konopelko
> MooseFS Technical Support Engineer
> pio...@mo... | moosefs.com 

Re: [Moosefs-users] FreeBSD fstab entry

[Piotr R. K. <pio...@mo...>]

Hello,
firstly you need to update to MooseFS 2.0.39-1.
Packages repository is available at http://get.moosefs.com[1] (please select "FreeBSD" in left menu).

The entry in /etc/fstab/ should look as presented below:

mfsmount_magic	/mnt/mfs	moosefs	rw,mfsmaster=MASTER_HOST,mountprog=/usr/local/bin/mfsmount,late	0	0

where MASTER_HOST = your Master Server name, e.g. mfsmaster.mfs.lan.

It has been tested both on FreeBSD 10.0 and 9.3.

In case of any further questions don't hesitate to contact me.

-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer*
pio...@mo...[2] | moosefs.com[3] 


> Hi,
> 
> Would anyone happen to know what an entry into the freebsd /etc/fstab file for mounting an mfs filesystem might look like?  I don’t think it’s likely to do look similar to the linux one (just hazarding a guess).
> 
> Thanks,
> -Joe
> 
> 
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users


--------
[1] http://get.moosefs.com
[2] mailto:pio...@mo...
[3] http://moosefs.com

[Moosefs-users] FreeBSD fstab entry

[Joseph L. <jo...@ge...>]

Hi,

Would anyone happen to know what an entry into the freebsd /etc/fstab file for mounting an mfs filesystem might look like?  I don’t think it’s likely to do look similar to the linux one (just hazarding a guess).

Thanks,
-Joe

Re: [Moosefs-users] mfsmount failed on FreeBSD 10.0

[Neddy, N. N. <na...@nd...>]

Or add this line to /boot/loader.conf and reboot:
fuse_load=YES

Excuse my silly mistake, I've put this line in /etc/rc.conf

Modified /boot/loader.conf and mfsmount works well.
Thanks guys.


On Sat, Sep 27, 2014 at 11:34 AM, Joe Love <jo...@ge...> wrote:
> Out of curiosity (and because I don’t remember), do you have the fuse modules actually loaded?  I don’t think FreeBSD 10 loads the included fuse module by default.
>
>> kldload fuse
>
> Or add this line to /boot/loader.conf and reboot:
> fuse_load=YES
>
> See if it still does it after that.
>
> -Joe
>
>> On Sep 26, 2014, at 10:20 PM, Neddy, NH. Nam <na...@nd...> wrote:
>>
>> <cont.>
>>
>> # mfsmount /mnt/mfs -H 10.2.192.130
>> mfsmaster accepted connection with parameters:
>> read-write,restricted_ip ; root mapped to root:wheel
>> fuse: failed to open fuse device: No such file or directory
>> error in fuse_mount
>>
>>
>>
>> On Sat, Sep 27, 2014 at 10:18 AM, Neddy, NH. Nam <na...@nd...> wrote:
>>> Hi, I also followed steps on Moosefs.com guide, but still failed when
>>> trying to mount
>>>
>>> # cat /usr/local/etc/pkg/repos/moosefs.conf
>>> moosefs: { url: "http://ppa.moosefs.com/freebsd/10:x86:64", enabled:
>>> YES, mirror_type: NONE }
>>>
>>> # pkg install moosefs-ce-client
>>> Updating FreeBSD repository catalogue...
>>> FreeBSD repository is up-to-date.
>>> Updating moosefs repository catalogue...
>>> moosefs repository is up-to-date.
>>> All repositories are up-to-date.
>>> Updating database digests format: 100%
>>> The following 3 packages will be affected (of 0 checked):
>>>
>>> New packages to be INSTALLED:
>>>        moosefs-ce-client: 2.0.34_1 [moosefs]
>>>        moosefs-common: 2.0.34_1 [moosefs]
>>>        fusefs-libs: 2.9.3_3 [FreeBSD]
>>>
>>> The process will require 1 MB more space.
>>> 245 KB to be downloaded.
>>>
>>> Proceed with this action? [y/N]: y
>>> Fetching moosefs-ce-client-2.0.34_1.txz: 100%  111 KB  56.7k/s    00:02
>>> Fetching moosefs-common-2.0.34_1.txz: 100%    9 KB   9.5k/s    00:01
>>> Fetching fusefs-libs-2.9.3_3.txz: 100%  125 KB 127.8k/s    00:01
>>> Checking integrity... done (0 conflicting)
>>> ===> Creating users and/or groups.
>>> Creating group 'mfs' with gid '925'.
>>> Creating user 'mfs' with uid '925'.
>>> [1/3] Installing moosefs-common-2.0.34_1: 100%
>>> [2/3] Installing fusefs-libs-2.9.3_3: 100%
>>> ===> Creating users and/or groups.
>>> Using existing group 'mfs'.
>>> Using existing user 'mfs'.
>>> [3/3] Installing moosefs-ce-client-2.0.34_1: 100%
>>>
>>> # mfsmount -V
>>> MFS version 2.0.34-1-ce
>>> FUSE library version: 2.9.3
>>> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>>>
>>> # mfsmount /mnt/mfs -H 10.2.192.130
>>> mfsmaster accepted connection with parameters:
>>> read-write,restricted_ip ; root mapped to root:wheel
>>> fuse: failed to open fuse device: No such file or directory
>>> error in fuse_mount
>>>
>>> On Fri, Sep 26, 2014 at 5:43 PM, Piotr Robert Konopelko
>>> <pio...@mo...> wrote:
>>>> Hello,
>>>>
>>>> we are very glad that you are using MooseFS distributed file system.
>>>>
>>>> The 1.6.x version you are using is not being developed any more.
>>>>
>>>>
>>>>
>>>> The latest version of MooseFS is 2.0(.34) which is introducing a lot of
>>>> changes. Also a lot of bugfixes have been included into version 2.0.x
>>>>
>>>> We've also found a bug in libfuse recently (in new FreeBSD 10.0 FUSE
>>>> implementation). For now, a workaround is included in MooseFS 2.0.34.
>>>>
>>>>
>>>>
>>>> We provide packages for FreeBSD 9 and 10. Please visit
>>>> http://get.moosefs.com and select "FreeBSD" from left menu to get new
>>>> MooseFS 2.0.
>>>>
>>>>
>>>>
>>>> Reading following documents is also highly recommended:
>>>>
>>>> MooseFS 2.0 Step by Step Installation Tutorial
>>>> MooseFS 2.0 User's Manual
>>>>
>>>>
>>>>
>>>> Please let us know if your problem is solved.
>>>>
>>>> In case of any questions don't hesitate to contact us: dw...@mo....
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best regards,
>>>>
>>>> Piotr Robert Konopelko
>>>>
>>>> MooseFS Technical Support Engineer
>>>>
>>>> pio...@mo... | moosefs.com
>>>>
>>>>
>>>> On Friday, September 26, 2014 2:08:55 PM Neddy, NH. Nam wrote:
>>>>
>>>>> Hi, I've installed a fresh FreeBSD 10.0 box and would like to create a
>>>>
>>>>> mount point with moosefs but it failed:
>>>>
>>>>>
>>>>
>>>>> # mfsmount /mnt/mfs/ -H 10.2.192.130
>>>>
>>>>> mfsmaster accepted connection with parameters:
>>>>
>>>>> read-write,restricted_ip ; root mapped to root:wheel
>>>>
>>>>> fuse: failed to open fuse device: No such file or directory
>>>>
>>>>> error in fuse_mount
>>>>
>>>>>
>>>>
>>>>> I was installed moosefs-client from ports, and tried moosefs-ce-client
>>>>
>>>>> package but have the same error.
>>>>
>>>>>
>>>>
>>>>> # mfsmount -V
>>>>
>>>>> MFS version 1.6.27
>>>>
>>>>> FUSE library version: 2.9.3
>>>>
>>>>> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>>>>
>>>>>
>>>>
>>>>> # uname -a
>>>>
>>>>> FreeBSD owncloud 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep
>>>>
>>>>> 15 14:35:52 UTC 2014
>>>>
>>>>> ro...@am...:/usr/obj/usr/src/sys/GENERIC amd64
>>>>
>>>>>
>>>>
>>>>>
>>>>
>>>>> Does anybody get the same error? Is there any workaround this issue?
>>>>
>>>>> Thanks in advance.
>>>>
>>>>> ~Neddy
>>>>
>>>>>
>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>
>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>>
>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>>>
>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>>
>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>>
>>>>>
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>>
>>>>> _______________________________________________
>>>>
>>>>> moosefs-users mailing list
>>>>
>>>>> moo...@li...
>>>>
>>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>>>
>>>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>

Re: [Moosefs-users] mfsmount failed on FreeBSD 10.0

[Joe L. <jo...@ge...>]

Out of curiosity (and because I don’t remember), do you have the fuse modules actually loaded?  I don’t think FreeBSD 10 loads the included fuse module by default.

> kldload fuse

Or add this line to /boot/loader.conf and reboot:
fuse_load=YES

See if it still does it after that.

-Joe

> On Sep 26, 2014, at 10:20 PM, Neddy, NH. Nam <na...@nd...> wrote:
> 
> <cont.>
> 
> # mfsmount /mnt/mfs -H 10.2.192.130
> mfsmaster accepted connection with parameters:
> read-write,restricted_ip ; root mapped to root:wheel
> fuse: failed to open fuse device: No such file or directory
> error in fuse_mount
> 
> 
> 
> On Sat, Sep 27, 2014 at 10:18 AM, Neddy, NH. Nam <na...@nd...> wrote:
>> Hi, I also followed steps on Moosefs.com guide, but still failed when
>> trying to mount
>> 
>> # cat /usr/local/etc/pkg/repos/moosefs.conf
>> moosefs: { url: "http://ppa.moosefs.com/freebsd/10:x86:64", enabled:
>> YES, mirror_type: NONE }
>> 
>> # pkg install moosefs-ce-client
>> Updating FreeBSD repository catalogue...
>> FreeBSD repository is up-to-date.
>> Updating moosefs repository catalogue...
>> moosefs repository is up-to-date.
>> All repositories are up-to-date.
>> Updating database digests format: 100%
>> The following 3 packages will be affected (of 0 checked):
>> 
>> New packages to be INSTALLED:
>>        moosefs-ce-client: 2.0.34_1 [moosefs]
>>        moosefs-common: 2.0.34_1 [moosefs]
>>        fusefs-libs: 2.9.3_3 [FreeBSD]
>> 
>> The process will require 1 MB more space.
>> 245 KB to be downloaded.
>> 
>> Proceed with this action? [y/N]: y
>> Fetching moosefs-ce-client-2.0.34_1.txz: 100%  111 KB  56.7k/s    00:02
>> Fetching moosefs-common-2.0.34_1.txz: 100%    9 KB   9.5k/s    00:01
>> Fetching fusefs-libs-2.9.3_3.txz: 100%  125 KB 127.8k/s    00:01
>> Checking integrity... done (0 conflicting)
>> ===> Creating users and/or groups.
>> Creating group 'mfs' with gid '925'.
>> Creating user 'mfs' with uid '925'.
>> [1/3] Installing moosefs-common-2.0.34_1: 100%
>> [2/3] Installing fusefs-libs-2.9.3_3: 100%
>> ===> Creating users and/or groups.
>> Using existing group 'mfs'.
>> Using existing user 'mfs'.
>> [3/3] Installing moosefs-ce-client-2.0.34_1: 100%
>> 
>> # mfsmount -V
>> MFS version 2.0.34-1-ce
>> FUSE library version: 2.9.3
>> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>> 
>> # mfsmount /mnt/mfs -H 10.2.192.130
>> mfsmaster accepted connection with parameters:
>> read-write,restricted_ip ; root mapped to root:wheel
>> fuse: failed to open fuse device: No such file or directory
>> error in fuse_mount
>> 
>> On Fri, Sep 26, 2014 at 5:43 PM, Piotr Robert Konopelko
>> <pio...@mo...> wrote:
>>> Hello,
>>> 
>>> we are very glad that you are using MooseFS distributed file system.
>>> 
>>> The 1.6.x version you are using is not being developed any more.
>>> 
>>> 
>>> 
>>> The latest version of MooseFS is 2.0(.34) which is introducing a lot of
>>> changes. Also a lot of bugfixes have been included into version 2.0.x
>>> 
>>> We've also found a bug in libfuse recently (in new FreeBSD 10.0 FUSE
>>> implementation). For now, a workaround is included in MooseFS 2.0.34.
>>> 
>>> 
>>> 
>>> We provide packages for FreeBSD 9 and 10. Please visit
>>> http://get.moosefs.com and select "FreeBSD" from left menu to get new
>>> MooseFS 2.0.
>>> 
>>> 
>>> 
>>> Reading following documents is also highly recommended:
>>> 
>>> MooseFS 2.0 Step by Step Installation Tutorial
>>> MooseFS 2.0 User's Manual
>>> 
>>> 
>>> 
>>> Please let us know if your problem is solved.
>>> 
>>> In case of any questions don't hesitate to contact us: dw...@mo....
>>> 
>>> 
>>> 
>>> --
>>> 
>>> Best regards,
>>> 
>>> Piotr Robert Konopelko
>>> 
>>> MooseFS Technical Support Engineer
>>> 
>>> pio...@mo... | moosefs.com
>>> 
>>> 
>>> On Friday, September 26, 2014 2:08:55 PM Neddy, NH. Nam wrote:
>>> 
>>>> Hi, I've installed a fresh FreeBSD 10.0 box and would like to create a
>>> 
>>>> mount point with moosefs but it failed:
>>> 
>>>> 
>>> 
>>>> # mfsmount /mnt/mfs/ -H 10.2.192.130
>>> 
>>>> mfsmaster accepted connection with parameters:
>>> 
>>>> read-write,restricted_ip ; root mapped to root:wheel
>>> 
>>>> fuse: failed to open fuse device: No such file or directory
>>> 
>>>> error in fuse_mount
>>> 
>>>> 
>>> 
>>>> I was installed moosefs-client from ports, and tried moosefs-ce-client
>>> 
>>>> package but have the same error.
>>> 
>>>> 
>>> 
>>>> # mfsmount -V
>>> 
>>>> MFS version 1.6.27
>>> 
>>>> FUSE library version: 2.9.3
>>> 
>>>> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>>> 
>>>> 
>>> 
>>>> # uname -a
>>> 
>>>> FreeBSD owncloud 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep
>>> 
>>>> 15 14:35:52 UTC 2014
>>> 
>>>> ro...@am...:/usr/obj/usr/src/sys/GENERIC amd64
>>> 
>>>> 
>>> 
>>>> 
>>> 
>>>> Does anybody get the same error? Is there any workaround this issue?
>>> 
>>>> Thanks in advance.
>>> 
>>>> ~Neddy
>>> 
>>>> 
>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>> 
>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>> 
>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>> 
>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>> 
>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>> 
>>>> 
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>> 
>>>> _______________________________________________
>>> 
>>>> moosefs-users mailing list
>>> 
>>>> moo...@li...
>>> 
>>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>> 
>>> 
> 
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
> 

Re: [Moosefs-users] mfsmount failed on FreeBSD 10.0

[Neddy, N. N. <na...@nd...>]

<cont.>

# mfsmount /mnt/mfs -H 10.2.192.130
mfsmaster accepted connection with parameters:
read-write,restricted_ip ; root mapped to root:wheel
fuse: failed to open fuse device: No such file or directory
error in fuse_mount



On Sat, Sep 27, 2014 at 10:18 AM, Neddy, NH. Nam <na...@nd...> wrote:
> Hi, I also followed steps on Moosefs.com guide, but still failed when
> trying to mount
>
> # cat /usr/local/etc/pkg/repos/moosefs.conf
> moosefs: { url: "http://ppa.moosefs.com/freebsd/10:x86:64", enabled:
> YES, mirror_type: NONE }
>
> # pkg install moosefs-ce-client
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> Updating moosefs repository catalogue...
> moosefs repository is up-to-date.
> All repositories are up-to-date.
> Updating database digests format: 100%
> The following 3 packages will be affected (of 0 checked):
>
> New packages to be INSTALLED:
>         moosefs-ce-client: 2.0.34_1 [moosefs]
>         moosefs-common: 2.0.34_1 [moosefs]
>         fusefs-libs: 2.9.3_3 [FreeBSD]
>
> The process will require 1 MB more space.
> 245 KB to be downloaded.
>
> Proceed with this action? [y/N]: y
> Fetching moosefs-ce-client-2.0.34_1.txz: 100%  111 KB  56.7k/s    00:02
> Fetching moosefs-common-2.0.34_1.txz: 100%    9 KB   9.5k/s    00:01
> Fetching fusefs-libs-2.9.3_3.txz: 100%  125 KB 127.8k/s    00:01
> Checking integrity... done (0 conflicting)
> ===> Creating users and/or groups.
> Creating group 'mfs' with gid '925'.
> Creating user 'mfs' with uid '925'.
> [1/3] Installing moosefs-common-2.0.34_1: 100%
> [2/3] Installing fusefs-libs-2.9.3_3: 100%
> ===> Creating users and/or groups.
> Using existing group 'mfs'.
> Using existing user 'mfs'.
> [3/3] Installing moosefs-ce-client-2.0.34_1: 100%
>
> # mfsmount -V
> MFS version 2.0.34-1-ce
> FUSE library version: 2.9.3
> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>
> # mfsmount /mnt/mfs -H 10.2.192.130
> mfsmaster accepted connection with parameters:
> read-write,restricted_ip ; root mapped to root:wheel
> fuse: failed to open fuse device: No such file or directory
> error in fuse_mount
>
> On Fri, Sep 26, 2014 at 5:43 PM, Piotr Robert Konopelko
> <pio...@mo...> wrote:
>> Hello,
>>
>> we are very glad that you are using MooseFS distributed file system.
>>
>> The 1.6.x version you are using is not being developed any more.
>>
>>
>>
>> The latest version of MooseFS is 2.0(.34) which is introducing a lot of
>> changes. Also a lot of bugfixes have been included into version 2.0.x
>>
>> We've also found a bug in libfuse recently (in new FreeBSD 10.0 FUSE
>> implementation). For now, a workaround is included in MooseFS 2.0.34.
>>
>>
>>
>> We provide packages for FreeBSD 9 and 10. Please visit
>> http://get.moosefs.com and select "FreeBSD" from left menu to get new
>> MooseFS 2.0.
>>
>>
>>
>> Reading following documents is also highly recommended:
>>
>> MooseFS 2.0 Step by Step Installation Tutorial
>> MooseFS 2.0 User's Manual
>>
>>
>>
>> Please let us know if your problem is solved.
>>
>> In case of any questions don't hesitate to contact us: dw...@mo....
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> Piotr Robert Konopelko
>>
>> MooseFS Technical Support Engineer
>>
>> pio...@mo... | moosefs.com
>>
>>
>> On Friday, September 26, 2014 2:08:55 PM Neddy, NH. Nam wrote:
>>
>>> Hi, I've installed a fresh FreeBSD 10.0 box and would like to create a
>>
>>> mount point with moosefs but it failed:
>>
>>>
>>
>>> # mfsmount /mnt/mfs/ -H 10.2.192.130
>>
>>> mfsmaster accepted connection with parameters:
>>
>>> read-write,restricted_ip ; root mapped to root:wheel
>>
>>> fuse: failed to open fuse device: No such file or directory
>>
>>> error in fuse_mount
>>
>>>
>>
>>> I was installed moosefs-client from ports, and tried moosefs-ce-client
>>
>>> package but have the same error.
>>
>>>
>>
>>> # mfsmount -V
>>
>>> MFS version 1.6.27
>>
>>> FUSE library version: 2.9.3
>>
>>> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>>
>>>
>>
>>> # uname -a
>>
>>> FreeBSD owncloud 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep
>>
>>> 15 14:35:52 UTC 2014
>>
>>> ro...@am...:/usr/obj/usr/src/sys/GENERIC amd64
>>
>>>
>>
>>>
>>
>>> Does anybody get the same error? Is there any workaround this issue?
>>
>>> Thanks in advance.
>>
>>> ~Neddy
>>
>>>
>>
>>>
>>> ------------------------------------------------------------------------------
>>
>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>
>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>
>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>
>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>
>>> _______________________________________________
>>
>>> moosefs-users mailing list
>>
>>> moo...@li...
>>
>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>>
>>

Re: [Moosefs-users] mfsmount failed on FreeBSD 10.0

[Neddy, N. N. <na...@nd...>]

Hi, I also followed steps on Moosefs.com guide, but still failed when
trying to mount

# cat /usr/local/etc/pkg/repos/moosefs.conf
moosefs: { url: "http://ppa.moosefs.com/freebsd/10:x86:64", enabled:
YES, mirror_type: NONE }

# pkg install moosefs-ce-client
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
Updating moosefs repository catalogue...
moosefs repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
The following 3 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        moosefs-ce-client: 2.0.34_1 [moosefs]
        moosefs-common: 2.0.34_1 [moosefs]
        fusefs-libs: 2.9.3_3 [FreeBSD]

The process will require 1 MB more space.
245 KB to be downloaded.

Proceed with this action? [y/N]: y
Fetching moosefs-ce-client-2.0.34_1.txz: 100%  111 KB  56.7k/s    00:02
Fetching moosefs-common-2.0.34_1.txz: 100%    9 KB   9.5k/s    00:01
Fetching fusefs-libs-2.9.3_3.txz: 100%  125 KB 127.8k/s    00:01
Checking integrity... done (0 conflicting)
===> Creating users and/or groups.
Creating group 'mfs' with gid '925'.
Creating user 'mfs' with uid '925'.
[1/3] Installing moosefs-common-2.0.34_1: 100%
[2/3] Installing fusefs-libs-2.9.3_3: 100%
===> Creating users and/or groups.
Using existing group 'mfs'.
Using existing user 'mfs'.
[3/3] Installing moosefs-ce-client-2.0.34_1: 100%

# mfsmount -V
MFS version 2.0.34-1-ce
FUSE library version: 2.9.3
mount_fusefs [fuse4bsd] version: 0.3.9-pre1

# mfsmount /mnt/mfs -H 10.2.192.130
mfsmaster accepted connection with parameters:
read-write,restricted_ip ; root mapped to root:wheel
fuse: failed to open fuse device: No such file or directory
error in fuse_mount

On Fri, Sep 26, 2014 at 5:43 PM, Piotr Robert Konopelko
<pio...@mo...> wrote:
> Hello,
>
> we are very glad that you are using MooseFS distributed file system.
>
> The 1.6.x version you are using is not being developed any more.
>
>
>
> The latest version of MooseFS is 2.0(.34) which is introducing a lot of
> changes. Also a lot of bugfixes have been included into version 2.0.x
>
> We've also found a bug in libfuse recently (in new FreeBSD 10.0 FUSE
> implementation). For now, a workaround is included in MooseFS 2.0.34.
>
>
>
> We provide packages for FreeBSD 9 and 10. Please visit
> http://get.moosefs.com and select "FreeBSD" from left menu to get new
> MooseFS 2.0.
>
>
>
> Reading following documents is also highly recommended:
>
> MooseFS 2.0 Step by Step Installation Tutorial
> MooseFS 2.0 User's Manual
>
>
>
> Please let us know if your problem is solved.
>
> In case of any questions don't hesitate to contact us: dw...@mo....
>
>
>
> --
>
> Best regards,
>
> Piotr Robert Konopelko
>
> MooseFS Technical Support Engineer
>
> pio...@mo... | moosefs.com
>
>
> On Friday, September 26, 2014 2:08:55 PM Neddy, NH. Nam wrote:
>
>> Hi, I've installed a fresh FreeBSD 10.0 box and would like to create a
>
>> mount point with moosefs but it failed:
>
>>
>
>> # mfsmount /mnt/mfs/ -H 10.2.192.130
>
>> mfsmaster accepted connection with parameters:
>
>> read-write,restricted_ip ; root mapped to root:wheel
>
>> fuse: failed to open fuse device: No such file or directory
>
>> error in fuse_mount
>
>>
>
>> I was installed moosefs-client from ports, and tried moosefs-ce-client
>
>> package but have the same error.
>
>>
>
>> # mfsmount -V
>
>> MFS version 1.6.27
>
>> FUSE library version: 2.9.3
>
>> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
>
>>
>
>> # uname -a
>
>> FreeBSD owncloud 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep
>
>> 15 14:35:52 UTC 2014
>
>> ro...@am...:/usr/obj/usr/src/sys/GENERIC amd64
>
>>
>
>>
>
>> Does anybody get the same error? Is there any workaround this issue?
>
>> Thanks in advance.
>
>> ~Neddy
>
>>
>
>>
>> ------------------------------------------------------------------------------
>
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
>> _______________________________________________
>
>> moosefs-users mailing list
>
>> moo...@li...
>
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
>

Re: [Moosefs-users] mfsmount failed on FreeBSD 10.0

[Piotr R. K. <pio...@mo...>]

Hello,
we are very glad that you are using MooseFS distributed file system.
The 1.6.x version you are using is not being developed any more.

The latest version of MooseFS is 2.0(.34) which is introducing a lot of changes. Also a lot of bugfixes have been included into version 2.0.x
We've also found a bug in libfuse recently (in new FreeBSD 10.0 FUSE implementation). For now, a workaround is included in MooseFS 2.0.34.

We provide packages for FreeBSD 9 and 10. Please visit http://get.moosefs.com[1] and select "FreeBSD" from left menu to get new MooseFS 2.0.

Reading following documents is also highly recommended:
     *  MooseFS 2.0 Step by Step Installation Tutorial[2] 
     *  MooseFS 2.0 User's Manual[3] 

Please let us know if your problem is solved.
In case of any questions don't hesitate to contact us: dw...@mo...[4].

-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer*
pio...@mo...[5] | moosefs.com[6] 


> Hi, I've installed a fresh FreeBSD 10.0 box and would like to create a
> mount point with moosefs but it failed:
> 
> # mfsmount /mnt/mfs/ -H 10.2.192.130
> mfsmaster accepted connection with parameters:
> read-write,restricted_ip ; root mapped to root:wheel
> fuse: failed to open fuse device: No such file or directory
> error in fuse_mount
> 
> I was installed moosefs-client from ports, and tried moosefs-ce-client
> package but have the same error.
> 
> # mfsmount -V
> MFS version 1.6.27
> FUSE library version: 2.9.3
> mount_fusefs [fuse4bsd] version: 0.3.9-pre1
> 
> # uname -a
> FreeBSD owncloud 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep
> 15 14:35:52 UTC 2014
> ro...@am...:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> 
> Does anybody get the same error? Is there any workaround this issue?
> Thanks in advance.
> ~Neddy
> 
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users


--------
[1] http://get.moosefs.com
[2] 
http://robo.moosefs.com/support/moosefs-installation.pdf
[3] 
http://robo.moosefs.com/support/moosefs-users-manual.pdf
[4] mailto:dw...@mo...
[5] mailto:pio...@mo...
[6] http://moosefs.com

[Moosefs-users] mfsmount failed on FreeBSD 10.0

[Neddy, N. N. <na...@nd...>]

Hi, I've installed a fresh FreeBSD 10.0 box and would like to create a
mount point with moosefs but it failed:

# mfsmount /mnt/mfs/ -H 10.2.192.130
mfsmaster accepted connection with parameters:
read-write,restricted_ip ; root mapped to root:wheel
fuse: failed to open fuse device: No such file or directory
error in fuse_mount

I was installed moosefs-client from ports, and tried moosefs-ce-client
package but have the same error.

# mfsmount -V
MFS version 1.6.27
FUSE library version: 2.9.3
mount_fusefs [fuse4bsd] version: 0.3.9-pre1

# uname -a
FreeBSD owncloud 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep
15 14:35:52 UTC 2014
ro...@am...:/usr/obj/usr/src/sys/GENERIC  amd64


Does anybody get the same error? Is there any workaround this issue?
Thanks in advance.
~Neddy

Re: [Moosefs-users] Problems with cp -al after upgrading to 2.0.34

[Aleksander W. <ale...@co...>]

Hi.

First of all.
MooseFS 2.0.34 had ACL bug, so if you had set some ACL permission on a
folder, this can cause some errors.

Secondly you can try to use MooseFS built-in snapshot mechanism. Just
use this command:
mfsmakesnapshot [-o] SOURCE... DESTINATION

/mfsmakesnapshot  makes  a  "real"  snapshot (lazy copy, like in case of
mfsappendchunks) of some object(s) or subtree (similarly to cp -r
command). It's atomic with respect to each SOURCE argument separately. 
If DESTINATION points to already existing file, error will be reported
unless -o (overwrite) option is given. Note: if SOURCE is a directory,
it's copied as a whole; but if it's followed by trailing slash, only
directory content is copied./


New MooseFS 2.0.35-1 version is available at our repositories.
MooseFS 2.0.35-1 at http://ppa.moosefs.com/current is tested only in our
development environment and it's not officially stable version jet.

For Ubuntu 14.04 - trusty
deb http://ppa.moosefs.com/current/apt/ubuntu/trusty trusty main

For Ubuntu 12.04 - precise
deb http://ppa.moosefs.com/current/apt/ubuntu/precise precise main

For Ubuntu 10.10 - maverick
deb http://ppa.moosefs.com/current/apt/ubuntu/maverick maverick main

For Debian 7.0 Wheezy
deb http://ppa.moosefs.com/current/apt/debian/wheezy wheezy main

For Debian 6.0 Squeeze
deb http://ppa.moosefs.com/current/apt/debian/squeeze squeeze main

For Debian 5.0 Lenny
deb http://ppa.moosefs.com/current/apt/debian/lenny lenny main

For REDHAT 6/ fedora/ centos/SuSE :
curl "http://ppa.moosefs.com/current/yum/MooseFS.repo" >
/etc/yum.repos.d/MooseFS.repo

For OSX:
http://ppa.moosefs.com/current/osx/moosefs-ce-current.pkg

For FreeBSD:
http://ppa.moosefs.com/current/freebsd

If your problem will still occur after update please give us more
details about it.

Best regards
Aleksander Wieliczko
Technical Support Engineer
moosefs.com

On 09/14/2014 04:20 AM, ka...@gm... wrote:
> Hello,
>
> I have recently upgraded from 1.6.27 to 2.0.34 and noticed that my
> rsnapshot scripts stopped working. The problem can be reproduced the
> following way:
> mkdir -p a/b
> date > a/b/c
> cp -al a x
> I am quite sure that it used to work and it also works on my local
> filesystem. Can this be fixed with some mfsmount parameters? (I can
> work around the problem in rsnapshot, but it is rather inefficient)
>
> Thanks,
> k.
>
> mfsmount -V
> MFS version 2.0.34-1-ce
> FUSE library version: 2.9.0
> fusermount version: 2.9.0
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users

[Moosefs-users] Problems with cp -al after upgrading to 2.0.34

[<ka...@gm...>]

Hello,

I have recently upgraded from 1.6.27 to 2.0.34 and noticed that my
rsnapshot scripts stopped working. The problem can be reproduced the
following way:
mkdir -p a/b
date > a/b/c
cp -al a x
I am quite sure that it used to work and it also works on my local
filesystem. Can this be fixed with some mfsmount parameters? (I can work
around the problem in rsnapshot, but it is rather inefficient)

Thanks,
k.

mfsmount -V
MFS version 2.0.34-1-ce
FUSE library version: 2.9.0
fusermount version: 2.9.0

[Moosefs-users] MFS on Mac 10.6 with OSXFUSE

[Mihaly F. <mih...@gm...>]

Dear All,

I am trying to get access to our departmental MFS (run on Linux) with my Mac. I installed Fuse for OS X, and configured and installed mfs binaries (same version as run on the Linux) in Terminal. All seemed to work, but when I try "mfsmount" I get "Illegal instruction" without any specific detail on the error, and cannot proceed.

versions I use:
Mac OS X 10.6.8 Snow Leopard
MFS version run on Linux: 1.6.27-1
Fuse for OS X: 2.7.0

Please let me know how I can solve the problem.
Thank you for your help in advance.

Mihaly