From: Michal B. <mic...@ge...> - 2011-05-31 08:51:42
|
Hi! Hmmm... How many chunks do you have on this test machine? Maybe there are so many many chunks that their processing causes timeouts - but this is rather unprobable. Maybe you just have too little RAM and your swap is overused which causes timeouts? More or less you should have about 12GB of RAM. Regarding sizes of hardlinks - "fixing" it would be too demanding for the CPU of the master. Similarly mfsmakesnapshot causes multiple counting of the same data. Best regards -Michał -----Original Message----- From: Papp Tamas [mailto:to...@ma...] Sent: Monday, May 30, 2011 11:24 AM To: Michal Borychowski; moo...@li... Subject: Re: [Moosefs-users] timeout On 05/30/2011 11:13 AM, Michal Borychowski wrote: > Hi! > > Just start your chunkservers one by one in such a situation. But this > happens very rarely. In this case this is not the same situation. I have only one chunkserver which the same as the master server. It starts this behaviour after a day or two days uptime. > I don't see much differences in the sizes - what do you mean exactly? > /data/backup: > inodes: 33Mi > directories: 4.2Mi > files: 29Mi > chunks: 29Mi > length: 72TiB > size: 73TiB > realsize: 73TiB > > > /dev/sda6 10T 7.3T 2.8T 73% /mnt/mfschunk1 > mfsmaster:9421 10T 7.3T 2.8T 73% /data/backup msdirinfo shows the volume size 73T while df shows the real one, which is 7.3T, or do I misunderstand something? Thanks, tamas ---------------------------------------------------------------------------- -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |