Unable to write to temp_path ('/tmp') - Read-only file system
UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
Unable to write to temp_path ('/tmp') - Read-only file system
I am very new to linux; I have a server running Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-72-generic-pae i686)
I mistakenly plugged in a MSA 500 (Data Storage box) to this linux server and then subsequently unplugged it, and now anything I try todo I get Read Only errors.
I believe the system has remounted my partition as ro and I need to un-mount and run fsck, but I am unsure how todo this exactly. Also do I need to use a Live CD to boot into?
I will paste the results of what I have found below. I have found:
Could you post the output of "mount" so I can see what is currently mounted?
You can remount a partition like this,
Code:
sudo mount -o remount,rw /partition/identifier /mount/point
However, if it is your root partition, you may just have to reboot, You cannot unmount your root partition while the system is running. I don't believe you can remount either, but I've never tried. If you need to run fsck on a partition it will need to be unmounted. If this is your root partition you will have to do this from a boot disk.
I am suppose to leave for vacation tomo and if I can't get this fixed that is out!
I see your cmd, on mount, but honestly I am not sure what the /partition/identifier /mount/point exactly means
Thanks again, info u requested below
root@pontus:/home/ezine# mount
/dev/mapper/pontus-root on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/cciss/c0d0p1 on /boot type ext2 (rw)
//venus/E$/Icinga_Backups on /mnt type cifs (rw)
mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
It's possible that information reported by mount(8) is not
up to date. For actual information about system mount points
check the /proc/mounts file.
and reboot with no tmpfs line in /etc/fstab (in that case it will use the default mount at /dev/shm )
or you can mount the tmpfs in ram instead, with this line:
Here is a more advanced example showing how to add tmpfs mounts for users. This is useful for websites, mysql tmp files, ~/.vim/, and more. It's important to try and get the ideal mount options for what you are trying to accomplish. The goal is to have as secure settings as possible to prevent abuse. Limiting the size, and specifying uid and gid + mode is very secure. For more information on this subject, follow the links listed in the #See also section.
The /tmp reference is a symptom, not the real problem. As /tmp is not specifically mounted elsewhere, it is still a sub directory to the root filesystem - which is mounted ro (the fstab option is why).
fsck on the root is best done from a liveCD. Note that fsck ensures the integrity of the filesystem - not necessarily the individual files. I'm guessing you don't have a recent backup you can restore.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.