SUSE Support

Here When You Need Us

tmpfs file system causes SLES11 network to not come up when booting

This document (7006027) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 (FCS)

Situation

The network interface(s) will not come up during boot up.  They will come up using the ifup command immediately after the system finishes the boot process, but not during it.

The problem can occur on:
  • Xen para-virtualized
  • VMware (Workstation, Server, ESX)
  • Physical servers
It is not based on special hardware (network cards).

The boot.msg file shows that the setup of eth0 times out:
Setting up (localfs) network interfaces:
    lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
doneWaiting for mandatory devices: eth0 __NSC__
29 28 27 26 24 23 22 21 20 19 17 16 15 14 13 12 10 9 8 7 6 5 4 2 1 0
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth0 is down
failed eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . . .failed

Resolution

The best resolution is to move to SLES11 SP1 or later. 
A change was made beginning with SLES11 SP1 whereas the cause of this issue was removed.

Cause

The problem is that /dev/shm is holding state information for the network devices when a new mount, for type tmpfs, is enacted.  The new, virtual mount does not contain the state information so the network device will activate without intervention.

Additional Information

Until the host can be updated to SLES11SP1 (or later), a workaround is to:

  1. remove the following line from /etc/fstab

         shmfs        /dev/shm   tmpfs      size=240m

  2. add the following line to /etc/fstab

         udev         /dev       tmpfs      noauto,size=240m   0  0
Notes:
  • The 240m size is just included as an example.  The default size for tmpfs is 50% of RAM and can be modified (although leaving the default is suggested if no specific application requirements are identified).
  • The udev mnt is visible in the output of "cat /proc/mounts" and is mounted by the /etc/init.d/boot "System Boot Control" script (boot log mesgs are "Mounting tmpfs at /dev" and/or "Remounting tmpfs at /dev" [applying the size parameter]) already before any /etc/init.d/boot.* scripts are called.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7006027
  • Creation Date: 18-May-2010
  • Modified Date:28-Sep-2022
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

tick icon

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

tick icon

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.