Thread View: comp.os.linux.misc
4 messages
4 total messages
Started by Sean Chivers
Wed, 15 Aug 2001 14:04
Boot problem "VFS: file-max limit 8192 reached" anyone help?
Author: Sean Chivers
Date: Wed, 15 Aug 2001 14:04
Date: Wed, 15 Aug 2001 14:04
34 lines
2944 bytes
2944 bytes
Hi all. I had a surprise booting up to Mandrake 7.2 today. Boot was correct from hdb1, with all hardware and drivers loaded ok. No hint of trouble until logon was complete. After Last Logon date, the error in the subject header is given, then the kernel proceeds to attempt to load the ld-linux.so.2 module. It waits a while then returns the syntax "Unable to load interpreter /lib/ld-linux.so.2". If I attempt to "startx", I get the syntax "blah blah(path&filename):Too many files open in system". Looks like a memory or virutal ram problem. But I am not in the least any sort of expert in such matters. Unfortunately I can't remember if I was stuffing around with any Mandrake x settings to cause this... Anyway, I thought it might be a boot sector problem, because I recently had to re-install (dare I say it...) Win 98 SE (on a completely separate drive and partition, so I booted from kernel floppy, but got the same problem. Don't remember seeing this before re-installing LILO after the win install. But there again, I simply dont' recall, as I've been too busy at work to logon at home for a long while... (any excuse). Can anyone venture a guess as to the cause and (hopefully) solution to my dilemma? I appreciate your assistance, Regards, Sean.
Re: Boot problem "VFS: file-max limit 8192 reached" anyone help?
Author: Jan Just Keijser
Date: Fri, 17 Aug 2001 12:07
Date: Fri, 17 Aug 2001 12:07
72 lines
3429 bytes
3429 bytes
have you been messing with ulimit settings anywhere? e.g. in the /etc/rc.d/rc.* scripts? the message you're seeing is normally caused by having ulimit -n > /proc/sys/fs/file-max e.g. you did ulimit -n unlimited or ulimit -n <some-big-number> somewhere. Find the place where you changed ulimit settings, otherwise, try increasing the file-max value: echo 32768 > /proc/sys/fs/file-max echo 131072 > /proc/sys/fs/inode-max (according to /usr/src/linux/Documentation/proc.txt, inode-max = 3 or 4 * file-max is recommended). but this does eat up a little RAM... HTH, JJK In article <3B7A8163.C5949FB3@senet.com.au>, Sean Chivers <saminc@senet.com.au> wrote: >Hi all. > >I had a surprise booting up to Mandrake 7.2 today. > >Boot was correct from hdb1, with all hardware and drivers loaded ok. No >hint of trouble until logon was complete. After Last Logon date, the >error in the subject header is given, then the kernel proceeds to >attempt to load the ld-linux.so.2 module. > >It waits a while then returns the syntax "Unable to load interpreter >/lib/ld-linux.so.2". > >If I attempt to "startx", I get the syntax "blah blah(path&filename):Too >many files open in system". > >Looks like a memory or virutal ram problem. But I am not in the least >any sort of expert in such matters. > >Unfortunately I can't remember if I was stuffing around with any >Mandrake x settings to cause this... > >Anyway, I thought it might be a boot sector problem, because I recently >had to re-install (dare I say it...) Win 98 SE (on a completely separate >drive and partition, so I booted from kernel floppy, but got the same >problem. Don't remember seeing this before re-installing LILO after the >win install. But there again, I simply dont' recall, as I've been too >busy at work to logon at home for a long while... (any excuse). > >Can anyone venture a guess as to the cause and (hopefully) solution to >my dilemma? > >I appreciate your assistance, > >Regards, Sean. > > --------------------------- JJK / Jan Just Keijser Unix/Linux Systems Engineer smtp: janjust@cisco.com flames > /dev/null 2>&1 ---------------------------
Re: Boot problem "VFS: file-max limit 8192 reached" anyone help?
Author: Eric en Jolanda
Date: Fri, 17 Aug 2001 20:03
Date: Fri, 17 Aug 2001 20:03
54 lines
3402 bytes
3402 bytes
<snip good ideas> I've seen posts with this problem before. (The OP should try to search groups.google.com) I don't recall the solution (A missing library?) But it was X messing, not ulimit limiting the number of open files. Did you upgrade Mandrake recently? try `ldd /path/to/X` and see if anything is missing. Eric > >I had a surprise booting up to Mandrake 7.2 today. > > > >Boot was correct from hdb1, with all hardware and drivers loaded ok. No > >hint of trouble until logon was complete. After Last Logon date, the > >error in the subject header is given, then the kernel proceeds to > >attempt to load the ld-linux.so.2 module. > > > >It waits a while then returns the syntax "Unable to load interpreter > >/lib/ld-linux.so.2". > > > >If I attempt to "startx", I get the syntax "blah blah(path&filename):Too > >many files open in system". > > > >Looks like a memory or virutal ram problem. But I am not in the least > >any sort of expert in such matters. > > > >Unfortunately I can't remember if I was stuffing around with any > >Mandrake x settings to cause this... > > > >Anyway, I thought it might be a boot sector problem, because I recently > >had to re-install (dare I say it...) Win 98 SE (on a completely separate > >drive and partition, so I booted from kernel floppy, but got the same > >problem. Don't remember seeing this before re-installing LILO after the > >win install. But there again, I simply dont' recall, as I've been too > >busy at work to logon at home for a long while... (any excuse). > > > >Can anyone venture a guess as to the cause and (hopefully) solution to > >my dilemma? > > > >I appreciate your assistance, > > > >Regards, Sean. > > > > > > --------------------------- > JJK / Jan Just Keijser > Unix/Linux Systems Engineer > smtp: janjust@cisco.com > > flames > /dev/null 2>&1 > ---------------------------
Re: Boot problem "VFS: file-max limit 8192 reached" anyone help?
Author: tommy
Date: Mon, 27 Aug 2001 13:47
Date: Mon, 27 Aug 2001 13:47
58 lines
3538 bytes
3538 bytes
On Wed, 15 Aug 2001 23:34:19 +0930, Sean Chivers <saminc@senet.com.au> wrote: >Hi all. > >I had a surprise booting up to Mandrake 7.2 today. > >Boot was correct from hdb1, with all hardware and drivers loaded ok. No >hint of trouble until logon was complete. After Last Logon date, the >error in the subject header is given, then the kernel proceeds to >attempt to load the ld-linux.so.2 module. > >It waits a while then returns the syntax "Unable to load interpreter >/lib/ld-linux.so.2". > >If I attempt to "startx", I get the syntax "blah blah(path&filename):Too >many files open in system". > >Looks like a memory or virutal ram problem. But I am not in the least >any sort of expert in such matters. > >Unfortunately I can't remember if I was stuffing around with any >Mandrake x settings to cause this... > >Anyway, I thought it might be a boot sector problem, because I recently >had to re-install (dare I say it...) Win 98 SE (on a completely separate >drive and partition, so I booted from kernel floppy, but got the same >problem. Don't remember seeing this before re-installing LILO after the >win install. But there again, I simply dont' recall, as I've been too >busy at work to logon at home for a long while... (any excuse). > >Can anyone venture a guess as to the cause and (hopefully) solution to >my dilemma? > >I appreciate your assistance, > >Regards, Sean. > > Seems like you are in a bad way having 8192 files open at boot. The good news is this is configurable on the fly. You can up the tunable file-max in the kernel by echo'ing the new limit to /proc/sys/fs/file-max: echo 16384 > /proc/sys/fs/file-max This will double the amount of available file handles but is temporary. if you want it to be permenent then put it in a startup file /etc/rc.d/rc.local or equivalent. You should be able to use "lsof" to take a look at the open files which may help diagnose what has gone wrong. -- Good Luck Tommy
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads