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.
I am in a project to find a solution for root file system full (/) on Linux servers. I know that it is difficult to fix this as we don’t know who or what application will dump the files on root FS. But I was asked to find some sort of common solution for this problems or suggestions. Can anyone have gone through this before, If so please help me.
...what evo2 said plus prevention like analyzing what gets logged (in the sense that multiple consecutive errors should be fixed instead of letting them fill up logs and maybe add proactive measures where this concerns brute force attacks) and remote log / free disk space monitoring with say Nagios.
I am serching for a common solution or suggessions. In my list i have 200 incidents which has 50 repeated issues. Is it anything that can impliment on all servers to reduce the incidents.
If you have /var, /tmp and /home as separate partitions they shouldn't be anything that routinely writes to / to fill it up. If that is a case I would find out what program does this and fix that issue. Usually, on a system configured like yours, you should be able to mount / as read-only, preventing any writes to that partition.
Yes it was manually moved some files to the / file system by user or application team members. Once i informed them they removed the application files. Any work areound can u pls suggest?
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
Quote:
Originally Posted by Febi881
Yes it was manually moved some files to the / file system by user or application team members. Once i informed them they removed the application files. Any work areound can u pls suggest?
first of all, off topic, but please spell out your words (text speak such as 'u' and 'pls' are against the rules here FYI)
second, it has been mentioned in your situation that mounting / as read-only is a viable option in your situation, this would deny anyone or anything privilege to write to / in the first place. this seems to me the most simple solution short of writing a script that checks for new files and moves them to their respective owner's home directory, which would be cumbersome at best.
Work around for team members to not write to /? Why do they have that capability in the first place, are they working with root-privileges? Give them restricted privileges, use sudo for giving limited root access to those that need it.
Yes, to change contents of it (like installing software or changing configuration files) you have to remount it r/w first, then go back to r/o later. Other than that, no.
The question still remains why your users are able to write to that partition. If they indeed work with root privileges there is nothing that hinders them to remount the partition themselves r/w to fill it up again. My first concern would be to fix that.
Just a question, if we have few NFS/NETAPP filesystems mounted on this root file system with application user as owners, will this read-only root file system will affect them from read-write operations.
Just a question, if we have few NFS/NETAPP filesystems mounted on this root file system with application user as owners, will this read-only root file system will affect them from read-write operations.
If you mount those filesystems rw then they are not affected.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.