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 getting read only filesystem error so I followed the steps as,
1. umount /tmp
2. fsck -y /tmp
but getting error message as "device busy" where there are no processes running for tmp (fuser /tmp & ps) but there are some open files in lsof so
how to remove the multiple open files in lsof for tmp.Also I dont want to reboot the server.
The filesystem resides on a partition/disk - it doesn't matter if it is a logical volume or not. It is that device you use for fsck. It is the same one you used when you created the filesystem.
ok, if that /tmp is a filesytem & no processes are link to it & i want to avoid reboot as well.
If it's mounted, you can't (and SHOULDN'T) fsck it. Your choices are to reboot into rescue/maintenance mode and fsck it, or not.
You SAY nothing is running on it or using it, but the fact it's saying it's busy tells you that SOMETHING is. Either your LVM software, a system process, or SOMETHING. It would have taken a few minutes to reboot the server and do this...far longer than posting threads about it, and you'd have been done by now.
I can reboot the server but its a production server.Also I want to find out the alternate way or solution to remount the "read only filesystem" without reboot.
I can reboot the server but its a production server.
...which doesn't matter AT ALL, since if it's having problems, those problems need to be FIXED. Schedule downtime, and do it.
Quote:
Also I want to find out the alternate way or solution to remount the "read only filesystem" without reboot.
As you've been told several times:THERE IS NO ALTERNATE WAY OR SOLUTION. You HAVE TO unmount it to fix it...period. You can't unmount that particular partition while the system is up, so AGAIN: you have to reboot into maintenance/rescue mode.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.