[systemd-bugs] [Bug 66702] New: g_udev_client_query_by_device_number fails on disks with subvolumes

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jul 8 07:48:43 PDT 2013


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

          Priority: medium
            Bug ID: 66702
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: g_udev_client_query_by_device_number fails on disks
                    with subvolumes
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: jpakkane at gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 82191
  --> https://bugs.freedesktop.org/attachment.cgi?id=82191&action=edit
Source code to demonstrate the issue

Sorry if this bug is filed in the wrong place. Information on GUdev is sparse
and as far as I can tell, systemd is the upstream.

Anyway, the g_udev_client_query_by_device_number function fails on directories
that are in subvolumes. An example is a btrfs file system with two subvolumes,
@ (mounted as root) and @home (mounted as /home). This also happens when using
encrypted home directories.

Having a subvolume might not be the real reason it fails, but that is what
seems to be triggering the issue.

To replicate, download the attached source code. Compile it with "gcc -Wall -o
idnum idnum.c `pkg-config --cflags --libs glib-2.0 gio-2.0 gudev-1.0`".

When run on a plain ext4 volume, the output is this:

./idnum
Device id is 2065.

Whereas on btrfs the output is this:

./idnum
Device id is 25.
Could not get device from num.

Originally filed here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1197796

-- 
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/20130708/2c310841/attachment.html>


More information about the systemd-bugs mailing list