You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Benjamin Marzinski b94a170e96 GFS2: remove dcache entries for remote deleted inodes ... When a file is deleted from a gfs2 filesystem on one node, a dcache entry for it may still exist on other nodes in the cluster. If this happens, gfs2 will be unable to free this file on disk. Because of this, it's possible to have a gfs2 filesystem with no files on it and no free space. With this patch, when a node receives a callback notifying it that the file is being deleted on another node, it schedules a new workqueue thread to remove the file's dcache entry. Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>		16 years ago
..
Kconfig	…
Makefile	…
acl.c	…
acl.h	…
aops.c	…
bmap.c	…
bmap.h	…
dentry.c	…
dir.c	…
dir.h	…
eaops.c	…
eaops.h	…
eattr.c	…
eattr.h	…
export.c	…
file.c	…
gfs2.h	…
glock.c	GFS2: remove dcache entries for remote deleted inodes	16 years ago
glock.h	GFS2: remove dcache entries for remote deleted inodes	16 years ago
glops.c	GFS2: remove dcache entries for remote deleted inodes	16 years ago
glops.h	…
incore.h	GFS2: remove dcache entries for remote deleted inodes	16 years ago
inode.c	…
inode.h	…
lock_dlm.c	…
log.c	…
log.h	…
lops.c	…
lops.h	…
main.c	…
meta_io.c	…
meta_io.h	…
ops_fstype.c	…
ops_inode.c	…
quota.c	…
quota.h	…
recovery.c	…
recovery.h	…
rgrp.c	…
rgrp.h	…
super.c	GFS2: remove dcache entries for remote deleted inodes	16 years ago
super.h	…
sys.c	…
sys.h	…
trace_gfs2.h	…
trans.c	…
trans.h	…
util.c	…
util.h	…