Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Have I just missed something, or in the 6.10 version of datadisk is 'datadisk: ... : resynchronizing, NOT de-activated' just the fallback something is wrong message??? /proc/drbd looks to be showing that they are synced. I know my first problem is to figure out how to make umount unmount the device, but the message at the end about resynchronizing worries me. I am trying to fallover from one machine to the other so I can update the packages including the kernel and drbd (to 6.12), and am now asking myself if it would be safe to issue the shutdown (forcing the unmount) and then let the other machine pick up (via heartbeat). At least heartbeat on the other node stopped when it got to this device and I was able to fall it back the other way until I figure out what's up. Any help understanding would be nice. #grep -e version -e ^1 /proc/drbd ;/etc/ha.d/resource.d/datadisk disk0 stop version: 0.6.10 (api:64/proto:62) 1: cs:Connected st:Primary/Secondary ns:818114288 nr:0 dw:102600808 dr:1683356862 pe:0 ua:0 datadisk: 'disk0' /dev/nb1 is mounted on /disk0, trying to unmount datadisk: 'disk0' trying to kill users of /dev/nb1 datadisk: ERROR: fuser -k -m /dev/nb1 [1]: datadisk: ERROR: NO OUTPUT datadisk: ERROR: umount -v /dev/nb1 [1]: datadisk: ERROR: umount: /disk0: device is busy datadisk: ERROR: umount -v /dev/nb1 FAILED datadisk: 'disk0[/dev/nb1]': resynchronizing, NOT de-activated -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter