[ale] /tmp set to read-only on boot (need help)
Doug McNash
dmcnash at charter.net
Thu Jun 16 15:59:52 EDT 2005
Hmm, that's what it did not long ago. Now I see that a mount -a on a FC1
system behaves as you describe and mount -a -v behaves as I would expect.
I have obviously not done a mount -a in a while.
I suppose that since the mount -a was such a common thing that people did
that someone got tired of the warning and changed the mount command.
That leaves the question as to why you see it unanswered?
On Thu, 16 Jun 2005, Ryan Fish wrote:
> I've never received any form of diagnostic message when issuing "mount -a"
> at any time before but I guess you could be right (I honestly do not know).
> I have always just used that cmd to force NFS mounts if they failed to start
> properly.
>
> -Ryan
>
> -----Original Message-----
> From: Doug McNash [mailto:dmcnash at charter.net]
> Sent: Thursday, June 16, 2005 2:13 PM
> To: FishR at bellsouth.net; Atlanta Linux Enthusiasts
> Subject: RE: RE: [ale] /tmp set to read-only on boot (need help)
>
>
> mount -a causes a mount to be issued for each filesystem listed /etc/fstab
> so
> if a filesystem is already mounted you should expect a diagnostic message.
>
> That's normal - ignore it or be more selective in what you mount.
>
> >
> > [root at server02 tmp]# mount -a
> > mount: /dev/sda1 already mounted or /boot busy
> >
> > Any ideas?
> >
> > Thank you again.
> > -Ryan
> >
> > -----Original Message-----
> > From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of Ryan
> > Fish
> > Sent: Thursday, June 16, 2005 12:44 PM
> > To: Chris Fowler
> > Cc: 'Atlanta Linux Enthusiasts'
> > Subject: Re: RE: [ale] /tmp set to read-only on boot (need help)
> >
> > That did it. I can now write to /tmp again.
> >
> > Thank you!
> > -Ryan
> >
> >
> > >
> > > From: Chris Fowler <cfowler at outpostsentinel.com>
> > > Date: 2005/06/16 Thu PM 12:42:23 EDT
> > > To: FishR at bellsouth.net
> > > CC: "'Atlanta Linux Enthusiasts'" <ale at ale.org>
> > > Subject: RE: [ale] /tmp set to read-only on boot (need help)
> > >
> > > mount / -o rw,remount; touch /tmp/file
> > >
> > > On Thu, 2005-06-16 at 12:28 -0400, Ryan Fish wrote:
> > > > Due to /tmp not being listed in /etc/fstab or /etc/mtab that command
> > (mount
> > > > /tmp -o rw,remount ) does not work.
> > > >
> > > > [root at server02 root]# mount /tmp -o rw,remount
> > > > mount: can't find /tmp in /etc/fstab or /etc/mtab
> > > >
> > > >
> > > > [root at server02 root]# more /etc/fstab
> > > > LABEL=/ / ext3 defaults
> > 1 1
> > > > LABEL=/boot /boot ext3 defaults
> > 1 2
> > > > none /dev/pts devpts gid=5,mode=620
> > 0 0
> > > > LABEL=/mc /mc ext3 defaults
> > 1 2
> > > > LABEL=/oracle /oracle ext3 defaults
> > 1 2
> > > > none /proc proc defaults
> > 0 0
> > > > none /dev/shm tmpfs defaults
> > 0 0
> > > > LABEL=/var /var ext3 defaults
> > 1 2
> > > > /dev/sdb1 swap swap defaults
> > 0 0
> > > > /dev/cdrom /mnt/cdrom udf,iso9660
> > > > noauto,owner,kudzu,ro 0 0
> > > > /dev/fd0 /mnt/floppy auto
> > noauto,owner,kudzu 0
> > > > 0
> > > > 192.168.3.202:/mc/backups/server02/exp
> > /mc/backups/database/mc/exp_bk/exp
> > > > nfs rw,hard,intr 1 2
> > > > 192.168.3.202:/mc/backups/systems/server02/rman
> > > > /mc/backups/database/mc/exp_bk/expold nfs rw,hard,intr 1 2
> > > >
> > > >
> > > > [root at server02 root]# more /etc/mtab
> > > > /dev/sda2 / ext3 rw 0 0
> > > > none /proc proc rw 0 0
> > > > none /dev/pts devpts rw,gid=5,mode=620 0 0
> > > > /dev/sdb2 /mc ext3 rw 0 0
> > > > /dev/sda5 /oracle ext3 rw 0 0
> > > > /dev/sda3 /var ext3 rw 0 0
> > > >
> > > >
> > > > [root at server02 root]# mount
> > > > /dev/sda2 on / type ext3 (rw)
> > > > none on /proc type proc (rw)
> > > > none on /dev/pts type devpts (rw,gid=5,mode=620)
> > > > /dev/sdb2 on /mc type ext3 (rw)
> > > > /dev/sda5 on /oracle type ext3 (rw)
> > > > /dev/sda3 on /var type ext3 (rw)
> > > >
> > > > -Ryan
> > > >
> > > > -----Original Message-----
> > > > From: Christopher Fowler [mailto:cfowler at outpostsentinel.com]
> > > > Sent: Thursday, June 16, 2005 12:11 PM
> > > > To: FishR at bellsouth.net; Atlanta Linux Enthusiasts
> > > > Subject: Re: [ale] /tmp set to read-only on boot (need help)
> > > >
> > > > mount /tmp -o rw,remount
> > > >
> > > > 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
> >
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> >
>
More information about the Ale
mailing list