[ale] /tmp set to read-only on boot (need help)

[Ryan Fish]

Yes, it is possible.  However, I do not know how I would be able to tell if that happened as I was not at a console when I rebooted the server.  It did take quite a long time for it to come back online though...

-Ryan

> 
> From: Jim Popovitch <jimpop at yahoo.com>
> Date: 2005/06/16 Thu PM 12:38:56 EDT
> To: Atlanta Linux Enthusiasts <ale at ale.org>
> Subject: Re: [ale] /tmp set to read-only on boot (need help)
> 
> Is it possible /tmp had a fsck error during boot and was mounted ro
> temporarily?
> 
> -Jim P.
> 
> On Thu, 2005-06-16 at 11:50 -0400, Ryan Fish wrote:
> > I'm not sure why, but /tmp is set to read-only on a RHEL3 AS server.  I am trying to set it back to allow writing but am failing so far.
> > 
> > Here is what I am seeing (I am unable to write to /tmp in any manner.):
> > 
> > [root at mcdb02 root]# crontab -e
> > /tmp/crontab.17515: Read-only file system
> > 
> > 
> > When trying to force the mounts to setup I see the following:
> > 
> > [root at mcdb02 root]# mount -a
> > mount: /dev/sda1 already mounted or /boot busy
> > 
> > There is no mention of /tmp in /etc/fstab or /etc/mtab
> > 
> > I can write to other locations on the server.
> > 
> > Any ideas on what I can try to get this fixed?  I guess a clean reboot should allow it to function properly again but I am trying to get by without doing that.
> > 
> > Thank you.
> > -Ryan
> > 
> > 
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>