From: WK <wk...@bn...> - 2011-07-30 00:59:36
|
Have you verified that you aren't firewalling out any MFS ports between the client/master/chunkservers? Try with iptables turned off and see if you still see the issues. Absent that review your mount command. Also check make sure selinux is not getting in the way. -wk On 7/29/11 1:20 PM, Dennis Jacobfeuerborn wrote: > Hi, > I'm starting to play with MooseFS and while the setup seemed to work fine I > ran into trouble after mounting it. > > My Setup is a Centos 6 host system and four Centos 6 virtual machines > installed as master, metalogger and two chunk servers. > Installing everything went smoothly and I can see the two chunk server in > the cgi stats interface. Both chunk servers have a 1gb partition formatted > as ext4 mounted under /mnt/data for the storage. > The cgi interface shows 2GiB total space and 1.3GiB available. > > I can mount the filesystem on a client and df -h shows 1.4G of free space > which looks ok. However the moment I try to copy a file no matter how small > I immediately get a "No space left on device" error. Doing a "ls" after > that shows the file on the filesystem with a size of 0 bytes. A "mkdir > /mnt/mfs/test" for example works fine though. > > I see the following in the syslog on the client: > > Jul 29 21:47:11 centos6 mfsmount[9930]: file: 6, index: 0 - fs_writechunk > returns status 21 > Jul 29 21:47:11 centos6 mfsmount[9930]: error writing file number 6: ENOSPC > (No space left on device) > > Any ideas what the problem could be? > > Regards, > Dennis > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |