[systemd-bugs] [Bug 89817] New: btrfs filesystem unexpectedly unable to boot

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Mar 29 15:19:36 PDT 2015


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

            Bug ID: 89817
           Summary: btrfs filesystem unexpectedly unable to boot
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: blocker
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: lacho8713 at gmail.com
        QA Contact: systemd-bugs at lists.freedesktop.org

Upon rebooting my system, the boot process freezes, saying it's unable to mount
at least one of my btrfs partitions. This happens both in my desktop and laptop
systems.

On the desktop, attempting to mount the said partition manually froze the
system. Upon checking dmesg, I found this (please excuse any typos, as I'm
typing it on a laptop while looking at the output on my desktop's monitor):

mar 29 15:03:37 pcname systemd[1]: home.mount mount process still around after
mar 29 15:03:37 SIGKILL. Ignoring.
pcname systemd[1]: Failed to mount /home.
-- Subject: Unit home.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit home.mount has failed.
--
--The result is failed.

I have the same issue happening on my laptop. Except that the unmountable
partition is /var instead. As I stated previously, both systems run on btrfs
partitions. Also, both of them run Arch Linux.

The laptop has systemd 2.18, while the desktop has systemd 2.18-2 installed.
Both machines have version 3.19-2 of the Linux kernel installed.

-- 
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/20150329/b95cb02c/attachment.html>


More information about the systemd-bugs mailing list