| Summary: |
systemd mounts a random subset of the system's md block device at each boot |
| Product: |
[openSUSE] openSUSE 12.1
|
Reporter: |
Daniel Lescohier <daniel.lescohier> |
| Component: |
Basesystem | Assignee: |
E-mail List <bnc-team-screening> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
E-mail List <qa-bugs> |
| Severity: |
Normal
|
|
|
| Priority: |
P5 - None
|
CC: |
fcrozat
|
| Version: |
Final | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86-64 | |
|
| OS: |
openSUSE 12.1 | |
|
| Whiteboard: |
|
|
Found By:
|
---
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
| Attachments: |
Output of blkid
fstab
|
Created attachment 473153 [details] Output of blkid User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 With sysv init, it's 100% reliable in mounting all /dev/md devices at every boot. With systemd, a different subset of the eight md devices succeed in mounting. E.g., in the last boot I tried, all but /dev/md3 succeeded. However, when I logged in to vt1 terminal and did /sbin/swapon -a, it did add /dev/md3 as the second swap partition. In a prior boot, three of the /dev/md devices failed to mount. The three devices included local filesystems, so init level 5 did not start, logged in to the vt1 terminal. There were errors on the screen that fsck couldn't run. So it seems to be a timing issue; it seems that for md devices with filesystems, sometimes fsck tries to run before the md device is ready; and for swap md devices, sometimes swapon runs before the md device is ready. This happened both with the original opensuse 12.1 systemd, and the 12.1 updated systemd I installed yesterday: htpc:/home/daniel # rpm -qi systemd Name : systemd Version : 37 Release : 3.6.1 Architecture: x86_64 Install Date: Fri 27 Jan 2012 05:30:26 PM EST I will attach the output of blkid and my /etc/fstab. I've switched back to sysv init for now. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3.