[systemd-bugs] [Bug 76497] New: [ARCH] [208-210] [regression?] systemd-remount-fs fails at boot -> succeeds later after manual invocation

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=76497

          Priority: medium
            Bug ID: 76497
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: [ARCH] [208-210] [regression?] systemd-remount-fs
                    fails at boot -> succeeds later after manual
                    invocation
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: ronald645 at gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 96224
  --> https://bugs.freedesktop.org/attachment.cgi?id=96224&action=edit
Fstab of all systems

I have three systems running Arch:

- 10yr old UP system; 32bit userspace; 32bit kernel; v3.14-rc7; custom stripped
kernel; FAIL
- ~4yr old SMP system; 32bit userspace; 64bit kernel; v3.13.6-1; ARCH kernel;
SUCCESS
- 7yr old UP system; 64bit kernel; 32/64bit userspace; v3.14-rc3; custom
stripped kernel; FAIL

I have attached:
- fstab used on all three systems
- .config of the 10yr old UP system

I replaced systemd-remount-fs with a shell script that invokes the binary with
strace:

[pid   459] mount("run", "/run",
0x1a0b240,MS_MGC_VAL|MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_REMOUNT|MS_NOATIME,"mode=0755,size=5m")
= -1 EINVAL (Invalid argument) <0.000039>

If I invoke systemd-remount-fs later, I get:

[mount][pid  2411] mount("run", "/run",
0x986d978,MS_MGC_VAL|MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_REMOUNT|MS_NOATIME,"mode=0755,size=5m")
= 0

Kernel logs indicate mount fails with error code 32 (-EINVAL?). The mount
manpage says:

source had an invalid superblock. Or, a remount (MS_REMOUNT) was attempted, but
source was not already mounted on target. Or, a move (MS_MOVE) was attempted,
but source was not a mount point, or was '/'.

So, I tested if the filesystem existed before by adding

mountpoint /run

Which claimed it was a valid mountpoint before systemd-remount-fs was invoked.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140323/cb4f7be4/attachment.html>