Bug 717794

Created attachment 510563 [details]
dmesg from boot with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg"

boot with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg"
mount -o remount,rw /
dmesg output attached.

[    7.114072] systemd[1]: Child 291 died (code=exited, status=32/n/a)
[    7.115071] systemd[1]: tmp.mount mount process exited, code=exited status=32

Suggestions on where to look next welcome.

A couple of suggestions:
 - add "StandardOutput=kmsg" to the tmp.mount unit file
 - boot with "enforcing=0"
See if there's some more information from mount in the dmesg then.

Booting with "enforcing=0" did not help.  I will add StandardOutput=kmsg as well to see if it makes any difference.

Is there some shortcut to all those?

StandardOutput=kmsg log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg

Is a tad long for reboots just to enable logging.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I usually keep them in my grub.conf.

booting with enforcing=0 or selinux=0 makes no difference at all.

same messages generated.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Have the line in /etc/fstab. Reboot (no special parameters needed this time). When you get the maintenance prompt, give the root password. Run "/bin/mount /tmp". Do you get an error?

mounted fine manually.

automount process started by systemd went nuts however.

# df -h | wc -l
32786

no way to repair short of another reboot.  loadave was above 6 simply due to automount subsystem.




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Hum I'm unable to duplicate this with a test.mount unit.. 

# mkdir 'p /test

# cat /lib/systemd/system/test.mount
[Unit]
Description=/test TMPFS Directory
Before=local-fs.target

[Mount]
What=tmpfs
Where=/test
Type=tmpfs
Options=size=500M,nr_inodes=1k,mode=1777,nosuid,nodev,fscontext=system_u:object_r:tmp_t:s0

# systemctl start test.mount && systemctl status test.mount && df -h | grep test
test.mount - /test TMPFS Directory
	  Loaded: loaded (/lib/systemd/system/test.mount)
	  Active: active (mounted) since Fri, 05 Aug 2011 17:02:44 +0000; 25ms ago
	   Where: /test
	    What: tmpfs
	 Process: 32700 ExecMount=/bin/mount tmpfs /test -t tmpfs -o size=500M,nr_inodes=1k,mode=1777,nosuid,nodev,fscontext=system_u:object_r:tmp_t:s0 (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/test.mount
tmpfs                 500M     0  500M   0% /test

Works for me wondering if this is somehow related to the /tmp directory? 

d.johnson can you duplicate this with a simple test directory ?

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Adding to /etc/fstab directly, and removing the unit created above makes a different error appear.

"Starting File System Check on /test aborted because of a dependency failed.
Starting /test aborted because a dependency failed.
Starting Relabel of all filesystems, if necessary aborted because a dependency failed.
Starting Mark the need to relabel after reboot aborted because a dependency failed.
Welcome to emergency mode.  Use "systemctl default" or ^D to activate default module.
Give root password for maintenance"

And then refuses root password.

Also fails on f16.

commenting this fstab line out makes it boot normally again.




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Could you please put the whole fstab here as an attachment?

Created attachment 552452 [details]
/etc/fstab file after kluding it to work

Retained entry in /etc/fstab, but appended the option "noauto".  Then added a
mount statement to rc.local.  Boots normally now, but this is an extremely
hackish solution.

Moved mountpoint to /var/lib/mock, so that it is useful.

Why "2 2" for the tmpfs? Try changing it to "0 0" so that fsck is not attempted on it.

Removed "noauto" and replaced "2 2" with "0 0".  Reboot.

The tmpfs mount point was not mounted, but mounts fine manually or from rc.local.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Hmm, I have:
  tmpfs  /tmp      tmpfs   defaults    0 0

which works totally fine.

(In reply to comment #14)
> The tmpfs mount point was not mounted

Did it just silently skip the mount and booted otherwise normally, or did you get dropped into the emergency shell again?

What did "systemctl status var-lib-mock.mount" say?

Was there anything logged from mount in dmesg or /var/log/messages?

Silently skipped, but does mount fine from rc.local or from command prompt post-bootup.  Nothing really noteworthy in dmesg or messages.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Please update systemd to the latest version from updates-testing and capture a new debug log with it (booting with "log_buf_len=1M systemd.log_level=debug
systemd.log_target=kmsg", then saving the output of dmesg).

tmpfs works fine for other users. The requested log has not been provided. Closing.

Hello, I am experimenting the same bug :/

How can I provide more data to help your to resolve this ?

I will create a VM to try to run with the correct argument to make the logs asked on comment 19 :)