On 8/31/10 10:53 AM, Lars Ellenberg wrote:
On Mon, Aug 30, 2010 at 10:58:51AM -0400, Mathieu Gagné wrote:
Hi,
We are having issues with symbolic links in /dev/drbd/by-res/ and
/dev/drbd/by-disk not being cleared after a resource is
removed/unconfigured.
The issue was claimed to be fixed with 8.3.1rc2:
http://lists.linbit.com/pipermail/drbd-user/2009-March/011771.html
Nope, that was a different issue than yours, (symlinks have not been
updated to new names when they should have) and it was fixed.
Ok.
Unfortunately, the issue is not fixed and can still be reproduced.
We are using DRBD 8.3.7 but used the latest version of
scripts/drbd.rules from git.
According to git log, this file has not changed for +15 months:
http://git.drbd.org/drbd-8.3.git/?p=drbd-8.3.git;a=history;f=scripts/drbd.rules;h=080635f05e63414a34ce85bb1afa11351f3d0ed9;hb=HEAD
The issue can be reproduced with those steps:
1) create a new standalone resource resname (add it to drbd.conf)
2) drbdadm create-md resname
3) drbdadm attach resname
4) drbdadm -- -o primary resname
5) drbdadm down resname
Results:
1) Both symbolic links in /dev/drbd/by-res/ and /dev/drbd/by-disk
still exist.
Expected.
The device's state is now "unconfigured", but the device still exists.
I do agree that the DRBD device is now unconfigured.
However the DRBD resource itself does not exist anymore in the
configuration, therefore:
- The disk is not associated to any DRBD device (by-disk)
- The DRBD resource does not exist anymore (by-res)
Therefore why would there still be a need for the presence of those
symbolic links which are now a false representation of the reality?
--
Mathieu
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
