Menu
▾
▴
moosefs-users
|
From: Dennis J. <den...@co...> - 2011-07-29 20:46:49
|
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 |
|
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 |
|
From: Dennis J. <den...@co...> - 2011-07-30 01:46:17
|
I already had iptables disabled and now I also disabled selinux on all systems but I'm still seeing this problem. This time (after I rebooted all systems once) when I issue the copy command nothing happens for about 60 seconds and the I get the "no space" error again: [root@centos6 ~]# mfsmount /mnt/mfs/ -H mfsmaster mfsmaster accepted connection with parameters: read-write,restricted_ip ; root mapped to root:root [root@centos6 ~]# df -h |grep -E "mfs|Avail" Filesystem Size Used Avail Use% Mounted on mfsmaster:9421 1.4G 0 1.4G 0% /mnt/mfs [root@centos6 ~]# cp sf2.stap /mnt/mfs/test/ cp: closing `/mnt/mfs/test/sf2.stap': No space left on device [root@centos6 ~]# df -h |grep -E "mfs|Avail" Filesystem Size Used Avail Use% Mounted on mfsmaster:9421 1.4G 0 1.4G 0% /mnt/mfs [root@centos6 ~]# ls -l /mnt/mfs/test/ total 0 -rw-r--r--. 1 root root 0 Jul 30 03:35 sf2.stap Regards, Dennis On 07/30/2011 02:59 AM, WK wrote: > 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 > > > ------------------------------------------------------------------------------ > 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 |
|
From: Michal B. <mic...@ge...> - 2011-08-02 06:38:10
|
Hi Dennis! You have too little disks. MooseFS reserves some space only for itself - it is not a percent of the disk size, but a fixed size. You should have at least 50GB for the chunkservers. Kind regards -Michal -----Original Message----- From: Dennis Jacobfeuerborn [mailto:den...@co...] Sent: Friday, July 29, 2011 10:21 PM To: moo...@li... Subject: [Moosefs-users] Cannot write to mounted filesystem 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 |
|
From: Dennis J. <den...@co...> - 2011-08-02 11:53:24
|
Hi Michal, thanks for the pointer I was already beginning to think that this might be a problem. You said I *should* have 50GB for chunkservers but can I get away with less? I've only started with MooseFS and right now I'm trying to use 4 virtual machines to get a feel for it and I do not intend to do any real work with it. The documentation talks about "several gigabytes". Would 5 or 10 GB be sufficient as well? If there is an absolute minimum then the chunkserver daemon should probably exit with an error if there is not enough space available to allow it to operate properly. Regards, Dennis On 08/02/2011 08:37 AM, Michal Borychowski wrote: > Hi Dennis! > > You have too little disks. MooseFS reserves some space only for itself - it > is not a percent of the disk size, but a fixed size. You should have at > least 50GB for the chunkservers. > > > Kind regards > -Michal > > > -----Original Message----- > From: Dennis Jacobfeuerborn [mailto:den...@co...] > Sent: Friday, July 29, 2011 10:21 PM > To: moo...@li... > Subject: [Moosefs-users] Cannot write to mounted filesystem > > 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 > |
|
From: Michal B. <mic...@ge...> - 2011-08-02 13:58:58
|
You can try 10GB or even 5GB, but this is absolute minimum. Yes, we'll add some information to the chunkserver process Regards -Michal -----Original Message----- From: Dennis Jacobfeuerborn [mailto:den...@co...] Sent: Tuesday, August 02, 2011 1:53 PM To: Michal Borychowski Cc: moo...@li... Subject: Re: [Moosefs-users] Cannot write to mounted filesystem Hi Michal, thanks for the pointer I was already beginning to think that this might be a problem. You said I *should* have 50GB for chunkservers but can I get away with less? I've only started with MooseFS and right now I'm trying to use 4 virtual machines to get a feel for it and I do not intend to do any real work with it. The documentation talks about "several gigabytes". Would 5 or 10 GB be sufficient as well? If there is an absolute minimum then the chunkserver daemon should probably exit with an error if there is not enough space available to allow it to operate properly. Regards, Dennis On 08/02/2011 08:37 AM, Michal Borychowski wrote: > Hi Dennis! > > You have too little disks. MooseFS reserves some space only for itself - it > is not a percent of the disk size, but a fixed size. You should have at > least 50GB for the chunkservers. > > > Kind regards > -Michal > > > -----Original Message----- > From: Dennis Jacobfeuerborn [mailto:den...@co...] > Sent: Friday, July 29, 2011 10:21 PM > To: moo...@li... > Subject: [Moosefs-users] Cannot write to mounted filesystem > > 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 > ---------------------------------------------------------------------------- -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X