@rknichols, the RAMTMP option isn't present in /etc/default/tmpfs. It is, however, present in /etc/default/rcS for some reason. The only reason I looked is because it was cross referenced in /etc/default/tmpfs. I went ahead and switched the yes to no, dropped to ctrl alt f1, sudo /etc/init.d/mdm stop, but I kept getting some sort of write cache error on a fixed time interval (maybe 5-10 seconds)? I was trying to lsof | grep /tmp (and also "/tmp", just in case), but no output of anything using /tmp. I eventually couldn't issue any command, so I used reisub. Everything rebooted fine, but I wasn't able to complete the full process you linked here from LM Forums, which haven't elicited much by the way. I've always found better help in this forum. I'm just not sure how best to proceed. I wasn't unable to umount /tmp, or check for processes using /tmp to my satisfaction.
Output of /etc/default/tmpfs.
# Size defaults for tmpfs filesystems mounted in early boot, before
# filesystems from /etc/fstab are mounted.
# NOTE: This file is deprecated. Please see rcS(5) for details on how
# to configure tmpfs size limits.
# _SIZE variables are the maximum size (in bytes) that tmpfs
# filesystems can use. The size will be rounded down to a multiple of
# the page size, 4096 bytes. If no size is set, TMPFS_SIZE will be
# used as the default.
# Note that more complex mount options may be used by the creation of a
# suitable entry in /etc/fstab. For example:
# tmpfs /run tmpfs size=10% 0 0
# is equivalent to RUN_SIZE=10%, and will override the RUN_SIZE
# setting. This will allow additional options such as nr_blocks and
# nr_inodes to be used, and also adjustment of the mode, nodev,
# nosuid, noexec options should any change from the defaults be
# TMPFS_SIZE: maximum size for all tmpfs filesystems if no specific
# size is provided. If no value is provided here, the kernel default
# will be used.
# RUN_SIZE: maximum size of /run (was previously /var/run)
# Defaults to 10% core memory; the size required varies widely
# depending upon the demands of the software being run; this heuristic
# scales /run usage on system size. Samba in particular has been seen
# to use at least 50MiB in a large heavily used server. Typical usage
# is hundreds of KiB, maximum is tens of MiB.
# LOCK_SIZE: maximum size of /run/lock (was previously /var/lock)
# Typical usage: tens of KiB; maximum hundreds of KiB. Default of
# 5MiB should ensure the limit is never reached.
LOCK_SIZE=5242880 # 5MiB
# SHM_SIZE: maximum size of /run/shm (was previously /dev/shm)
# No default size; the size required varies widely depending upon the
# demands of the software being run.
# TMP_SIZE: maximum size of /tmp
# No default size.
This is the output of /etc/default/rcS now:
# Default settings for the scripts in /etc/rcS.d/
# For information about these variables see the rcS(5) manual page.
# This file belongs to the "initscripts" package.
# delete files in /tmp during boot older than x days.
# '0' means always, -1 or 'infinite' disables the feature
# spawn sulogin during boot, continue normal boot if not used in 30 seconds
# do not allow users to log in until the boot has completed
# assume that the BIOS clock is set to UTC time (recommended)
# be more verbose during the boot process
# automatically repair filesystems with inconsistencies during boot
# mount /run/lock as a tmpfs (separately from /run)
# mount /run/shm as a tmpfs (separately from /run)
# mount /tmp as a tmpfs
Should I attempt to switch RAMLOCK and RAMSHM to "no"? I'm sorry I whizzed through the cache write through error. If I can reproduced the error, I'll post the output if you like.