Package: nbd-client
Version: 1:2.9.11-3
Severity: important
with the raid1 setup below if the nbd-server stops nbd-client dies too, the
/dev/nbd0 device
disappears and a "cat /proc/mdstat" simple hangs. The raid layer seems to get
no error from
the nbd0 device to disable the device. Adding the -persits option or a
timeout=5 to the
nbd-client doesn't help.
Any ideas or requests for more information are welcome,
greetings
Hermann
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
md1 : active raid1 nbd0[1](W) cciss/c0d1[0]
292935872 blocks [2/2] [UU]
#commandline:
nbd-client timeout=5 server.iwr.uni-heidelberg.de 12399 /dev/nbd0
#dmesg (nothing else):
[353466.516947] nbd0: unknown partition table
[353545.607459] nbd0: Receive control failed (result -32)
[353545.666352] nbd0: shutting down socket
[353545.712550] nbd0: queue cleared
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages nbd-client depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-18 GNU C Library: Shared libraries
nbd-client recommends no packages.
nbd-client suggests no packages.
-- debconf information:
* nbd-client/killall: false
nbd-client/device:
nbd-client/host:
nbd-client/port:
nbd-client/type: raw
nbd-client/number: 0
nbd-client/no-auto-config:
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
