/ver 100% ... restarted virtual server - but server not coming up
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
/ver 100% ... restarted virtual server - but server not coming up
Dear All
My Linux server version is
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
It's a Virtual server. It's a file server & nfs mount in other servers from this server.
We Found that we are not able to open any new session
/ver is 100% ... our team restarted this virtual server - but server is not coming up.
1.How can I solve this ?
2. This is a file server & we have nfa mount in other servers from this server.
in all those servers df -h got hung & even ll from /
is also hang. Commented(#) nfs mount from /etc/fstab
still same issue.How can I solve this ?
Is there any way to solve it without restarting server?
If /, /var, or /usr get 100% full, no new files can be created on them, which can cause all sorts of problems (e.g. many programs put a lock file in /var/run -- if that directory can't be written to, some of them will refuse to start). The solution is to figure out why /var got filled up, and as unSpawn said, take measures to rpevent it from happening again.
When an NFS server goes down, clients with its shares mounted will generally have df hang until the server is available again or the NFS volume is forcibly unmounted (not recommended!).
How to rescue a KVM http://linux.dell.com/files/whitepap...Easy_Part2.pdf
Use that to purge /var, then find out why it happened after you get it back up and running. EG look into logrotate settings, or possibly a runaway process filled the /var.
Before you purge the disk, try to figure out which logs/prog was at fault eg take a file list.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.