On Tue, Oct 06, 2009 at 10:30:44AM +0200, Hermann Lauer wrote: > 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
What do you mean by 'the device disappears'? The device node will not go away; do you just mean to say that the connection is lost? > 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. -persist will indeed not help in getting the RAID device to move to degraded mode -- on the contrary; the idea of -persist is that the NBD kernel module will suspend reads from or writes to the device until the connection has reappeared. I'm not sure whether this has already been implemented as such in 2.6.26, but in any case you should not try it. The timeout option should, however, get the RAID device to work after the specified timeout. I'm not sure why it isn't working. What happens if you wait "timeout" seconds and try to read from the device manually (e.g., by doing "dd if=/dev/nbd0 of=/dev/zero count=1")? -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
