Your message dated Sun, 3 Jan 2016 15:42:06 +0100
with message-id <[email protected]>
and subject line Re: Bug#804511: systemd: won't let me mount /media/dvd after
plugging in a USB optical drive
has caused the Debian Bug report #804511,
regarding systemd: won't let me mount /media/dvd after plugging in a USB
optical drive
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.)
--
804511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804511
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 227-2
I have an optical drive in my PC, with an fstab entry:
/dev/dvd /media/dvd udf,iso9660 user,noauto 0 0
Today I plugged in another optical drive via USB; and since unplugging
it, systemd won't let me use /media/dvd for a loopback mount.
For example, I run "mount -o loop test.iso /media/dvd; ls -l /media/dvd"
and can see the contents. But systemd immediately unmounts it:
Nov 08 20:48:51 terra kernel: UDF-fs: warning (device loop0): udf_load_vrs:
No anchor found
Nov 08 20:48:51 terra kernel: UDF-fs: Rescanning with blocksize 2048
Nov 08 20:48:51 terra kernel: UDF-fs: warning (device loop0): udf_load_vrs:
No anchor found
Nov 08 20:48:51 terra kernel: UDF-fs: Rescanning with blocksize 2048
Nov 08 20:48:51 terra kernel: UDF-fs: INFO Mounting volume 'CDROM', timestamp
2015/11/08 23:14 (1000)
Nov 08 20:48:51 terra systemd[1]: media-dvd.mount: Unit is bound to inactive
unit dev-sr1.device. Stopping, too.
Nov 08 20:48:51 terra systemd[1]: Unmounting /media/dvd...
Nov 08 20:48:51 terra systemd[1]: Unmounted /media/dvd.
Nov 08 20:48:51 terra systemd[1]: media-dvd.mount: Unit entered failed state.
I've included the "media-dvd.mount" section from systemd-analyze below.
I don't know how that job got associated with sr1 or how to disassociate
it (/dev/dvd points to sr0). Given that "noauto" is set, I don't expect
systemd to react at all.
A workaround is to use another mountpoint.
-- Michael
-> Unit media-dvd.mount:
Description: /media/dvd
Instance: n/a
Unit Load State: loaded
Unit Active State: failed
Inactive Exit Timestamp: Sun 2015-11-08 20:48:51 EST
Active Enter Timestamp: Sun 2015-11-08 20:48:51 EST
Active Exit Timestamp: Sun 2015-11-08 20:48:51 EST
Inactive Enter Timestamp: Sun 2015-11-08 20:48:51 EST
GC Check Good: yes
Need Daemon Reload: no
Transient: no
Slice: system.slice
CGroup: n/a
CGroup realized: no
CGroup mask: 0x0
CGroup members mask: 0x0
Name: media-dvd.mount
Documentation: man:fstab(5)
Documentation: man:systemd-fstab-generator(8)
Fragment Path: /run/systemd/generator/media-dvd.mount
Source Path: /etc/fstab
Requires: -.mount
Wants: system.slice
BindsTo: dev-sr1.device
WantedBy: dev-sr1.device
Conflicts: umount.target
Before: local-fs.target
Before: umount.target
After: systemd-journald.socket
After: local-fs-pre.target
After: system.slice
After: dev-sr1.device
After: -.mount
References: -.mount
References: systemd-journald.socket
References: local-fs-pre.target
References: umount.target
References: dev-sr1.device
References: system.slice
References: local-fs.target
RequiresMountsFor: /media /dev/dvd
StopWhenUnneeded: no
RefuseManualStart: no
RefuseManualStop: no
DefaultDependencies: yes
OnFailureJobMode: replace
IgnoreOnIsolate: yes
IgnoreOnSnapshot: no
Mount State: failed
Result: exit-code
Where: /media/dvd
What: /dev/dvd
File System Type: udf,iso9660
Options: user,noauto
From /proc/self/mountinfo: no
From fragment: yes
DirectoryMode: 0755
UMask: 0022
WorkingDirectory: /
RootDirectory: /
NonBlocking: no
PrivateTmp: no
PrivateNetwork: no
PrivateDevices: no
ProtectHome: no
ProtectSystem: no
IgnoreSIGPIPE: yes
LimitNOFILE: 4096
StandardInput: null
StandardOutput: journal
StandardError: inherit
SyslogFacility: daemon
SyslogLevel: info
KillMode: control-group
KillSignal: SIGTERM
SendSIGKILL: yes
SendSIGHUP: no
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, mips
Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-2
ii libapparmor1 2.10-2+b1
ii libaudit1 1:2.4.4-4
ii libblkid1 2.27.1-1
ii libc6 2.19-22
ii libcap2 1:2.24-12
ii libcap2-bin 1:2.24-12
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.4-3
ii libkmod2 21-1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.27.1-1
ii libpam0g 1.1.8-3.1
ii libseccomp2 2.2.3-2
ii libselinux1 2.3-2+b1
ii libsystemd0 227-2
ii mount 2.27.1-1
ii sysv-rc 2.88dsf-59.2
ii udev 227-2
ii util-linux 2.27.1-1
Versions of packages systemd recommends:
ii dbus 1.10.2-1
ii libpam-systemd 227-2
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hello Michael(s),
Michael Biebl [2015-11-11 15:08 +0100]:
> Am 11.11.2015 um 04:12 schrieb Michael Gold:
> > I've noticed that the /dev/dvd symlink changes from sr0 to sr1 when the
> > drive is attached, which may be relevant. And systemd first tried to
>
> Ah, this might be related indeed.
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774080
This got fixed in 228-3 now, and indeed I suspect it's the same bug.
Thus I close this now.
Please speak up if it still happens with 228-3.
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
