Your message dated Sun, 18 Dec 2016 23:01:41 +0100
with message-id <[email protected]>
and subject line Re: systemd: slashes in partition labels
has caused the Debian Bug report #818136,
regarding systemd: slashes in partition labels
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
818136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818136
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 229-2
Including a slash (/) in a partition label leads to systemd not being able
to check the partition for errors. This in turn lead to problems accessing
the partition (with no obvious acknowledgement of problems to the user). I
and perhaps others dealing with this bug may erroneously suspect hard disk
issues.
I was able to work around this bug by removing the slashes from the labels
of the relevant partition.
I am able to reproduce the bug with the following steps:
1) Create a new partition with label "/test". (I used gnome-disks.)
2) Format the partition with ext4.
3) Add the following line to /etc/fstab:
LABEL="/test" /junk/test ext4 noauto,x-systemd.automount 1 2
4) Run the following commands as root:
mkdir -p /junk/test
cd junk
mount test
touch test/forcefsck
5) Reboot.
6) Then from a terminal:
cd /junk
cd test/
The last command hangs until control-c is pressed when the following error
is produced:
^X^C^Cbash: cd: test/: Interrupted system call
(Doing other commands such as listing directories results in a situation
when even control-c won't return you to the shell.)
"grep test /var/log/daemon.log" returns:
Mar 13 23:12:45 panther systemd[1]: junk-test.automount: Got automount
request for /junk/test, triggered by 2380 (bash)
Mar 13 23:12:45 panther systemd[1]: Starting File System Check on
/dev/disk/by-label/\x2ftest...
Mar 13 23:12:45 panther systemd-fsck[2481]: Failed to stat
/dev/disk/by-label//test: No such file or directory
Mar 13 23:12:45 panther systemd[1]:
systemd-fsck@dev-disk-by\x2dlabel-\x5cx2ftest.service:
Main process exited, code=exited, status=1/FAILURE
Mar 13 23:12:45 panther systemd[1]: Failed to start File System Check on
/dev/disk/by-label/\x2ftest.
Mar 13 23:12:45 panther systemd[1]: Dependency failed for /junk/test.
Mar 13 23:12:45 panther systemd[1]: junk-test.mount: Job
junk-test.mount/start failed with result 'dependency'.
Mar 13 23:12:45 panther systemd[1]:
systemd-fsck@dev-disk-by\x2dlabel-\x5cx2ftest.service:
Unit entered failed state.
Mar 13 23:12:45 panther systemd[1]:
systemd-fsck@dev-disk-by\x2dlabel-\x5cx2ftest.service:
Failed with result 'exit-code'.
I am running Debian testing and have been for quite a while. So, this bug
must be fairly new.
What follows below is some output of reportbug. Please let me know if you
want more information. Thank you for your work!
Best,
Pat
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-3
ii libapparmor1 2.10-3+b1
ii libaudit1 1:2.4.5-1+b1
ii libblkid1 2.27.1-4
ii libc6 2.21-9
ii libcap2 1:2.24-12
ii libcap2-bin 1:2.24-12
ii libcryptsetup4 2:1.7.0-2
ii libgcrypt20 1.6.5-2
ii libgpg-error0 1.21-2
ii libkmod2 22-1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.27.1-4
ii libpam0g 1.1.8-3.2
ii libseccomp2 2.2.3-3
ii libselinux1 2.4-3+b1
ii libsystemd0 229-2
ii mount 2.27.1-4
ii util-linux 2.27.1-4
Versions of packages systemd recommends:
ii dbus 1.10.6-1
ii libpam-systemd 229-2
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
ii udev 229-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 232-7
On Mon, 14 Mar 2016 00:09:17 -0400 Pat Hooper <[email protected]> wrote:
> Package: systemd
> Version: 229-2
>
> Including a slash (/) in a partition label leads to systemd not being able
> to check the partition for errors. This in turn lead to problems accessing
> the partition (with no obvious acknowledgement of problems to the user). I
> and perhaps others dealing with this bug may erroneously suspect hard disk
> issues.
>
> I was able to work around this bug by removing the slashes from the labels
> of the relevant partition.
>
> I am able to reproduce the bug with the following steps:
> 1) Create a new partition with label "/test". (I used gnome-disks.)
> 2) Format the partition with ext4.
> 3) Add the following line to /etc/fstab:
> LABEL="/test" /junk/test ext4 noauto,x-systemd.automount 1 2
> 4) Run the following commands as root:
> mkdir -p /junk/test
> cd junk
> mount test
> touch test/forcefsck
> 5) Reboot.
> 6) Then from a terminal:
> cd /junk
> cd test/
> The last command hangs until control-c is pressed when the following error
> is produced:
> ^X^C^Cbash: cd: test/: Interrupted system call
>
> (Doing other commands such as listing directories results in a situation
> when even control-c won't return you to the shell.)
>
> "grep test /var/log/daemon.log" returns:
> Mar 13 23:12:45 panther systemd[1]: junk-test.automount: Got automount
> request for /junk/test, triggered by 2380 (bash)
> Mar 13 23:12:45 panther systemd[1]: Starting File System Check on
> /dev/disk/by-label/\x2ftest...
> Mar 13 23:12:45 panther systemd-fsck[2481]: Failed to stat
> /dev/disk/by-label//test: No such file or directory
> Mar 13 23:12:45 panther systemd[1]:
> systemd-fsck@dev-disk-by\x2dlabel-\x5cx2ftest.service:
> Main process exited, code=exited, status=1/FAILURE
> Mar 13 23:12:45 panther systemd[1]: Failed to start File System Check on
> /dev/disk/by-label/\x2ftest.
> Mar 13 23:12:45 panther systemd[1]: Dependency failed for /junk/test.
> Mar 13 23:12:45 panther systemd[1]: junk-test.mount: Job
> junk-test.mount/start failed with result 'dependency'.
> Mar 13 23:12:45 panther systemd[1]:
> systemd-fsck@dev-disk-by\x2dlabel-\x5cx2ftest.service:
> Unit entered failed state.
> Mar 13 23:12:45 panther systemd[1]:
> systemd-fsck@dev-disk-by\x2dlabel-\x5cx2ftest.service:
> Failed with result 'exit-code'.
>
> I am running Debian testing and have been for quite a while. So, this bug
> must be fairly new.
I've tried to reproduce the problem with the exact same setup in a test
VM and it works without problems with the current version in unstable,
thus closing this bug report for that version.
If you still encounter the problem with an up-to-date sid/stretch
system, please reopen the bug report.
As a side-note, you don't need the touch ../forcefsck to make sure fsck
is run before the mount is attempted. I'm not actually sure, if that
file is still read for partitions other then the / file system.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
