| View previous topic :: View next topic |
| Author |
Message |
Merlin
Guest
|
 Posted: Wed Nov 19, 2008 2:05 am Post subject: mounting /tmp right |
 |
|
Hi there,
I am running suse 9.1 as a root server and I believe there is a
misconfiguration concerning the file system. The LAMP System crashed now
the second time because the DB could not write to /tmp. /tmp was full
and has only 2GB free. Then I rebootet and the system did have to
recheck /dev/sda7 because it was not clean unmounted.
~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 940M 96M 797M 11% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/sda5 4.7G 1.5G 3.2G 32% /usr
/dev/sda6 4.7G 929M 3.8G 20% /var
/dev/sda7 218G 141G 66G 69% /home
none 2.0G 112K 2.0G 1% /tmp
Why is /tmp on none? Should it not be mounted on /sda7 for example?
Thank you for any hint on how to configure this right.
Best regards,
Merlin |
|
| |
|
 Back to top |
Lew Pitcher
Guest
|
| Posted: Wed Nov 19, 2008 2:34 am Post subject: Re: mounting /tmp right |
|
|
On November 18, 2008 15:05, in alt.os.linux.suse, Merlin
(merlin_x@fastmail.fm) wrote:
| Quote: | Hi there,
I am running suse 9.1 as a root server and I believe there is a
misconfiguration concerning the file system. The LAMP System crashed now
the second time because the DB could not write to /tmp.
|
That's one thing to look into: why your DB wants to write files in /tmp.
AFAIK, your DBMS should be writing files in a /var directory, or on a raw
device directly, not in /tmp.
| Quote: | /tmp was full and has only 2GB free.
|
I think I understand what you mean. The write to /tmp reported "No space",
but /tmp showed as having 2Gb freespace
| Quote: | Then I rebootet and the system did have to
recheck /dev/sda7 because it was not clean unmounted.
~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 940M 96M 797M 11% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/sda5 4.7G 1.5G 3.2G 32% /usr
/dev/sda6 4.7G 929M 3.8G 20% /var
/dev/sda7 218G 141G 66G 69% /home
none 2.0G 112K 2.0G 1% /tmp
Why is /tmp on none?
|
Good question. Show us the contents of /etc/fstab and /etc/mtab, and the
output from the mount( command. Most likely, /tmp is a tmpfs "ramdisk"
(but, in that case, it should have shown as tmpfs in the df(1) listing) or
some other ram-based temporary storage. In that case, the size of /tmp
depends on the system load; a system using a lot of swap space would run
out of /tmp earlier than a system that uses little or no swap space.
| Quote: | Should it not be mounted on /sda7 for example?
|
It doesn't look like it should. /dev/sda7 is already mounted as your /home
directory; you wouldn't want it double-mounted as /tmp as well. And, the
contents of /home are different from what you'd expect in /tmp. Is
your /home directory correct (does it have user home directories in it, or
does it look like it is full of temporary files)?
| Quote: | Thank you for any hint on how to configure this right.
Best regards,
Merlin
|
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------ |
|
| |
|
| Back to top |
David Bolt
Guest
|
| Posted: Wed Nov 19, 2008 3:09 am Post subject: Re: mounting /tmp right |
|
|
On Tue, 18 Nov 2008, Merlin wrote:-
| Quote: | Hi there,
I am running suse 9.1 as a root server
|
Hmm...
| Quote: | and I believe there is a misconfiguration concerning the file system.
The LAMP System crashed now the second time because the DB could not
write to /tmp. /tmp was full and has only 2GB free.
|
Okay.
| Quote: | Then I rebootet and the system did have to recheck /dev/sda7 because it
was not clean unmounted.
|
That's normal.
| Quote: | ~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 940M 96M 797M 11% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/sda5 4.7G 1.5G 3.2G 32% /usr
/dev/sda6 4.7G 929M 3.8G 20% /var
/dev/sda7 218G 141G 66G 69% /home
none 2.0G 112K 2.0G 1% /tmp
|
Got plenty of memory and/or swap? That's what /tmp is presently using.
| Quote: | Why is /tmp on none?
|
Because that's where it's been configured to be mounted.
| Quote: | Should it not be mounted on /sda7 for example?
|
Well, I personally always mount my /tmp on a separate partition of its
own[0]. It helps to prevent silly things like filling up all the memory
and/or swap when mounted on none, or filling up / when not kept separate
from it.
| Quote: | Thank you for any hint on how to configure this right.
|
Look at the output from:
fdisk -l
and compare it to /etc/fstab. It could be there's an unused partition
that someone forgot to attach /tmp to. If there isn't, it's possible to
create a directory under /home and symlink /tmp to it.
[0] I also do this with /var/log, just so something suddenly dumping
large amounts of data to a log file doesn't do the same thing.
Regards,
David Bolt
--
Team Acorn: http://www.distributed.net/ OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
SUSE 10.1 32 | | openSUSE 10.3 32b | openSUSE 11.0 32b
| openSUSE 10.2 64b | openSUSE 10.3 64b | openSUSE 11.0 64b
RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 |
|
| |
|
| Back to top |
|
