Patrick Caulfield 254da030df [DLM] Don't delete misc device if lockspace removal fails ... Currently if the lockspace removal fails the misc device associated with a lockspace is left deleted. After that there is no way to access the orphaned lockspace from userland. This patch recreates the misc device if th dlm_release_lockspace fails. I believe this is better than attempting to remove the lockspace first because that leaves an unattached device lying around. The potential gap in which there is no access to the lockspace between removing the misc device and recreating it is acceptable ... after all the application is trying to remove it, and only new users of the lockspace will be affected. Signed-Off-By: Patrick Caulfield <pcaulfie@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>		2007-05-01 09:10:44 +01:00
..
ast.c
ast.h
config.c
config.h
debug_fs.c
dir.c
dir.h
dlm_internal.h
Kconfig
lock.c
lock.h
lockspace.c
lockspace.h
lowcomms-sctp.c
lowcomms-tcp.c	[DLM] Fix uninitialised variable in receiving	2007-05-01 09:10:34 +01:00
lowcomms.h
lvb_table.h
main.c
Makefile
member.c
member.h
memory.c
memory.h
midcomms.c
midcomms.h
rcom.c
rcom.h
recover.c
recover.h
recoverd.c
recoverd.h
requestqueue.c
requestqueue.h
user.c	[DLM] Don't delete misc device if lockspace removal fails	2007-05-01 09:10:44 +01:00
user.h
util.c
util.h