Linux - Server This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
03-09-2011, 01:08 PM
|
#1
|
Member
Registered: Dec 2003
Posts: 78
Rep:
|
crontab -e read-only filesystem error
Hello...
When I try to edit teh crontab with the crontab -e command I get the following:
/tmp/crontab.XXXXz56XMg: Read-only file system...
mount command shows all filesystems as (rw)
The server is redhat 4.7, vanilla install. How do I edit the crontab? Rebooting the server doesn't help and there is adequate space for usage on the server per df -h...
I appreciate your help as I need to change the root crontab as soon as possible. Everything I've seen on the 'Net has been inconclusive or ineffective.
Thanks!
Blaine
|
|
|
03-09-2011, 01:15 PM
|
#2
|
Senior Member
Registered: Dec 2004
Location: Marburg, Germany
Distribution: openSUSE 15.2
Posts: 1,339
|
Is /tmp mounted from another server? Even when it's mounted rw on the client side, it could be exported as ro.
|
|
|
03-09-2011, 01:26 PM
|
#3
|
Member
Registered: Aug 2009
Location: Chicago
Distribution: CentOS
Posts: 114
Rep:
|
There may be a filesystem issue. You will see that error sometimes when there is corruption requiring an fsck. You can edit the crontab directly by editing /var/spool/cron/username, but you may need to restart crond.
Also, try to touch /tmp/test or something to see if you can write to /tmp as root.
|
|
|
03-09-2011, 05:29 PM
|
#4
|
Member
Registered: Dec 2003
Posts: 78
Original Poster
Rep:
|
I get the same filesystem (ro) error when I do a touch or try to restart crond...
Only difference now is that crond is apparently unable to start again as well...
How would I do an fsck on this system?
Thanks!
Blaine
|
|
|
03-09-2011, 05:35 PM
|
#5
|
Member
Registered: Oct 2006
Posts: 179
Rep:
|
Can you post the output of "df -h" and "df -i" command ?
Also the contents of /etc/fstab..
Quote:
Originally Posted by blainemiller
Hello...
When I try to edit teh crontab with the crontab -e command I get the following:
/tmp/crontab.XXXXz56XMg: Read-only file system...
mount command shows all filesystems as (rw)
The server is redhat 4.7, vanilla install. How do I edit the crontab? Rebooting the server doesn't help and there is adequate space for usage on the server per df -h...
I appreciate your help as I need to change the root crontab as soon as possible. Everything I've seen on the 'Net has been inconclusive or ineffective.
Thanks!
Blaine
|
|
|
|
03-09-2011, 05:36 PM
|
#6
|
Member
Registered: Aug 2009
Location: Chicago
Distribution: CentOS
Posts: 114
Rep:
|
Yeah, it pretty much sounds like your filesystem is cooked. If you want to run fsck, first you need to find out which device /tmp resides on. Just type mount and it will show where everything is mounted. It may or may not be on a separate device from /, if you don't see a separate entry for /tmp, then the device is the same as the one used for /. Then, you'll want to boot off a live cd, or installation DVD and go to recovery mode. From there, run fsck -y -C /dev/sda4 or whatever device /tmp resides on. You want to do this off installation media because you do not want to run fsck on a mounted filesystem. So, for hte same reason, do not allow the installation media to attempt to automatically mount your drives (it will usually ask first).
I'd suggest making backups of anything important before you run fsck, because there is always a chance that you'll get some data loss.
|
|
|
03-09-2011, 06:21 PM
|
#7
|
Member
Registered: Dec 2003
Posts: 78
Original Poster
Rep:
|
Thanks for everyone's help... I'm going to go ahead and scrub this system and reload it from scratch. It's only a VM, so it shouldn't be too tedious. There was nothing of importance on it datawise and reloading the applications resident on the server while tedious, is more doable than trying to continue trouble shooting this mess...
I thank you all and will mark this as resolved...
Blaine
|
|
|
03-09-2011, 06:32 PM
|
#8
|
Senior Member
Registered: Dec 2004
Location: Marburg, Germany
Distribution: openSUSE 15.2
Posts: 1,339
|
Well, in this case: maybe the file for the virtual file system on the real host is owned by someone else than the user of the VM.
|
|
|
All times are GMT -5. The time now is 09:15 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|