Skip to content

B
Bluefield Linux

mellanox / Bluefield Linux
接近 1 年 前同步成功

通知 3
Star 0
Fork 0
B
Bluefield Linux

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 27 8月, 2009 2 次提交
    • S
      GFS2: Rename eattr.[ch] as xattr.[ch] · 307cf6e6
      由 Steven Whitehouse 提交于 
      Use the more conventional name for the extended attribute
support code. Update all the places which care.
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      307cf6e6
    • S
      GFS2: Clean up of extended attribute support · 40b78a32
      由 Steven Whitehouse 提交于 
      This has been on my list for some time. We need to change the way
in which we handle extended attributes to allow faster file creation
times (by reducing the number of transactions required) and the
extended attribute code is the main obstacle to this.

In addition to that, the VFS provides a way to demultiplex the xattr
calls which we ought to be using, rather than rolling our own. This
patch changes the GFS2 code to use that VFS feature and as a result
the code shrinks by a couple of hundred lines or so, and becomes
easier to read.

I'm planning on doing further clean up work in this area, but this
patch is a good start. The cleaned up code also uses the more usual
"xattr" shorthand, I plan to eliminate the use of "eattr" eventually
and in the mean time it serves as a flag as to which bits of the code
have been updated.
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      40b78a32
  3. 25 8月, 2009 1 次提交
  5. 24 8月, 2009 2 次提交
  7. 18 8月, 2009 1 次提交
    • W
      GFS2: free disk inode which is deleted by remote node -V2 · 970343cd
      由 Wengang Wang 提交于 
      this patch is for the same problem that Benjamin Marzinski fixes at commit
b94a170e

quotation of the original problem:

---cut here---
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.
---end cut---

after applying Benjamin's patch, I think there is still a case in which the disk
inode remains even when "no space" is hit. the case is that when running
d_prune_aliases() against the inode, there are one or more dentries(aliases)
which have reference count number > 0. in this case the dentries won't be pruned.
and even later, the reference count becomes to 0, the dentries can still be
cached in memory. unfortunately, no callback come again, things come back to
the state before the callback runs. thus the on disk inode remains there until
in memoryinode is removed for some other reason(shrinking inode cache or unmount
the volume..).

this patch is to remove those dentries when their reference count becomes to 0 and
the inode is deleted by remote node. for implementation, gfs2_dentry_delete() is
added as dentry_operations.d_delete. the function returns true when the inode is
deleted by remote node. in dput(), gfs2_dentry_delete() is called and since it
returns true, the dentry is unhashed from dcache and then removed. when all dentries
are removed, the in memory inode get removed so that the on disk inode is freed.
Signed-off-by: NWengang Wang <wen.gang.wang@oracle.com>
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      970343cd
  9. 17 8月, 2009 6 次提交
  11. 16 8月, 2009 2 次提交
  13. 15 8月, 2009 1 次提交
  15. 14 8月, 2009 25 次提交