Your message dated Mon, 27 Apr 2015 09:54:34 +0200
with message-id <[email protected]>
and subject line Re: [Ceph-maintainers] Bug#783150: ceph-common: Jessie VM
fails to boot if systemd-sysv installed and a rbd set to be mounted at
boot in fstab
has caused the Debian Bug report #783150,
regarding ceph-common: Jessie VM fails to boot if systemd-sysv installed and a
rbd set to be mounted at boot in fstab
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.)
--
783150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783150
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ceph-common
Version: 0.80.9-1~bpo70+1
Severity: important
Hello,
I'm using Wheezy Ceph packages from ceph.com on a Jessie computer. (Jessie
packages not available.)
This mostly works. The only problem I have is that if the package systemd-sysv
is installed (instead
of sysvinit-core, they conflict with one another) and fstab lists a rbd device
to be mounted at boot,
then boot hangs partway through and does not finish. (I can include the last
lines which appear if desired.)
I think this is because appropriate systemd files are not included in the
Wheezy package. systemd can be installed on
wheezy, but even more people will be using it with jessie.
As mentioned, a workaround is to install sysvinit-core which replaces
systemd-sysv.
If you have packages to test, I'd be a guinea pig.
Thanks!
C.
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages ceph-common depends on:
ii libblkid1 2.25.2-6
ii libboost-thread1.49.0 1.49.0-3.2
ii libc6 2.19-18
ii libgcc1 1:4.9.2-10
ii libgoogle-perftools4 2.2.1-0.2
ii libkeyutils1 1.5.9-5+b1
ii libnspr4 2:4.10.7-1
ii libnss3 2:3.17.2-1.1
ii librados2 0.80.9-1~bpo70+1
ii librbd1 0.80.9-1~bpo70+1
ii libstdc++6 4.9.2-10
ii libuuid1 2.25.2-6
ii python-ceph 0.80.9-1~bpo70+1
ii python-requests 2.4.3-6
ceph-common recommends no packages.
Versions of packages ceph-common suggests:
pn ceph <none>
pn ceph-mds <none>
-- Configuration Files:
/etc/ceph/rbdmap changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Chad
Please don't report bugs on ceph.com packges to the Debian bug tracking
system. There's nothing Debian can do about these bugs. See beow for my
comments nonetheless.
If you want to further discuss and eventually resolve this bug, please
reply directly to the [email protected] mailingist.
Chad W Seys <[email protected]> writes:
> Package: ceph-common
> Version: 0.80.9-1~bpo70+1
> Severity: important
>
> Hello,
> I'm using Wheezy Ceph packages from ceph.com on a Jessie computer.
> (Jessie packages not available.)
> This mostly works. The only problem I have is that if the package
> systemd-sysv is installed (instead
> of sysvinit-core, they conflict with one another) and fstab lists a rbd
> device to be mounted at boot,
> then boot hangs partway through and does not finish. (I can include the last
> lines which appear if desired.)
> I think this is because appropriate systemd files are not included in the
> Wheezy package. systemd can be installed on
> wheezy, but even more people will be using it with jessie.
> As mentioned, a workaround is to install sysvinit-core which
> replaces systemd-sysv.
Which version of systemd is that? The version in wheezy is very old. Can
you retest if the problem also appears with the version from
wheezy-backports?
How exactly do you mount your rbd devices with sysvinit? Is there an
initscript that maps the rbd device before fstab get processed?
Please include all debug information you can get.
Gaudenz
--- End Message ---
