On 07/25/2011 01:40 PM, Helge Kreutzmann wrote: > On Sun, Jul 24, 2011 at 11:12:41PM +0200, Christian Kastner wrote: >> One possibility would be that something went wrong during the recent >> /var/run -> /run transition (I see the above mounts under /run) > > /run is a symlink to /var/run on that machine.
Well, that's the first weird thing -- AFAIK it should be the other way around. Looking at sysvinit's changelog, the above could be a result of the transition process, but I'm not sure. >> Could you look into /etc/fstab (and maybe /etc/default/tmpfs) and see if >> you can spot something fishy? > > /etc/fstab: > /dev/mapper/system_vg-var_vg /var ext3 nodev,nosuid,data=ordered 0 > 2 > /dev/mapper/system_vg-aptcache_lv /var/cache/apt-cacher-ng > ext3 nodev,nosuid,noexec,data=ordered 0 2 > > Those tmpfs file systems are not mentioned. From a brief look, it appears as though /etc/init.d/mountkernfs.sh automatically takes care of them. > syslog.1:Jul 24 18:31:11 sneo kernel: tmpfs: Bad mount option data > > So somehow the tmpfs-entries inherit the mount options from /var? Nope > I removed the "data=ordered" from /var and together with the following > changes, the "Bad mount option" error message is gone. I'd put that back in. It's irrelevant to this case, but there was some controversy regarding data safety around it (although I really don't recall what it was) > Next I tried to get tmpfs mounted on /var/run > > I disabled the other two tmpfs entries in /etc/default/rcS, i.e. > /run/lock and /runshm. > > I added /var/run explicitly into /etc/fstab > tmpfs /var/run tmpfs nodev,nosuid,size=5242880,mode=755 > 0 0 > > Now, after a reboot, tmpfs is supposedly mounted (i.e. mount|grep > tmpfs). However, the files in /var/run look like before. When I umount > /var/run, I get an error message that the file system is not mounted. > Now, in mount|grep tmpfs /var/run is no longer listed. When I mount > /var/run explicitly afterwards, /var/run is empty as expected (and > tmpfs mounted). > > I'm clearly running out of ideas how to get /var/run mounted as tmpfs. > Actually, I probably don't understand which script mounts what and > when; ideally, /var/run would simply be zeroed at reboot... Again, to me it looks like something went wrong during the /run transition. For example, this is an excerpt from my /etc/fstab: # /var UUID=<foo> /var jfs defaults 0 2 # This mount for /run replaces the default configured in # /etc/default/tmpfs tmpfs /run tmpfs nosuid,noexec,size=1m,mode=755 0 0 # This mount for /run/lock replaces the default configured in # /etc/default/tmpfs tmpfs /run/lock tmpfs nodev,noexec,nosuid,size=1m,mode=1777 0 0 I'm not sure I can help any further because I followed the transition only in passing, but perhaps you can find some hints in the changelog entries[0] for that transition? Christian [0] see 2.88dsf-13.3, 2.88dsf-13.5 http://packages.debian.org/changelogs/pool/main/s/sysvinit/current/changelog
signature.asc
Description: OpenPGP digital signature
