1. 10 Jun, 2009 2 commits
  2. 05 Jun, 2009 1 commit
  3. 03 Jun, 2009 1 commit
  4. 02 Jun, 2009 1 commit
  5. 26 May, 2009 2 commits
    • Steven Whitehouse's avatar
      GFS2: Remove args subdir from gfs2 sysfs files · f6eb5349
      Steven Whitehouse authored
      Since we can cat /proc/mounts there is no need to have this
      subdirectory in the gfs2 sysfs files. In fact this does not
      reflect the full range of possible mount argumenmts, where
      as /proc/mounts does.
      
      There was only one userland user of this set of sysfs files
      and it will function perfectly well without these files
      being present (in fact that subcommand of gfs2_tool is
      obsolete anyway).
      
      The tune/* subdirectory is also considered mostly obsolete,
      but there are a few uses of this until mount arguments can
      be added for the last few functions for which there are no
      equivalents currently. However the tune/* directory is still
      in my sights and new code should avoid using it. Only the gfs2_quota
      and gfs2_tool programs are know to use tune/* at the moment.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      f6eb5349
    • Steven Whitehouse's avatar
      GFS2: Remove lockstruct subdir from gfs2 sysfs files · e1b28aab
      Steven Whitehouse authored
      The lockstruct sub directory contained two entries, both of
      which are duplicated elsewhere in the gfs2 sysfs files as
      well as being available via /proc/mounts. There is no userland program
      using either of them, so this patch removes them.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      e1b28aab
  6. 22 May, 2009 5 commits
  7. 21 May, 2009 2 commits
    • Steven Whitehouse's avatar
      GFS2: Be more aggressive in reclaiming unlinked inodes · 1ce97e56
      Steven Whitehouse authored
      This patch increases the frequency with which gfs2 looks
      for unlinked, but still allocated inodes. Its the equivalent
      operation to ext3's orphan list, but done with bitmaps in
      the resource groups.
      
      This also fixes a bug where a field in the rgrp was too small.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      1ce97e56
    • Steven Whitehouse's avatar
      GFS2: Add a rgrp bitmap full flag · 60a0b8f9
      Steven Whitehouse authored
      During block allocation, it is useful to know if sections of disk
      are full on a finer grained basis than a single resource group.
      This can make a performance difference when resource groups have
      larger numbers of bitmap blocks, since we no longer have to search
      them all block by block in each individual bitmap.
      
      The full flag is set on a per-bitmap basis when it has been
      searched and found to have no free space. It is then skipped in
      subsequent searches until the flag is reset. The resetting
      occurs if we have to drop the glock on the resource group for any
      reason, or if we deallocate some blocks within that resource
      group and thus free up some space.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      60a0b8f9
  8. 20 May, 2009 1 commit
    • Steven Whitehouse's avatar
      GFS2: Improve resource group error handling · 09010978
      Steven Whitehouse authored
      This patch improves the error handling in the case where we
      discover that the summary information in the resource group
      doesn't match the bitmap information while in the process of
      allocating blocks. Originally this resulted in a kernel bug,
      but this patch changes that so that we return -EIO and print
      some messages explaining what went wrong, and how to fix it.
      
      We also remember locally not to try and allocate from the
      same rgrp again, so that a subsequent allocation in a
      different rgrp should succeed.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      09010978
  9. 19 May, 2009 3 commits
    • Steven Whitehouse's avatar
      GFS2: Don't warn when delete inode fails on ro filesystem · ef9e8b14
      Steven Whitehouse authored
      If the filesystem is read-only, then we expect that delete inode
      will fail, so there is no need to warn about it.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      ef9e8b14
    • Steven Whitehouse's avatar
      GFS2: Update docs · e9ccb73a
      Steven Whitehouse authored
      Update a few things which were out of date, and fix a typo.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      e9ccb73a
    • Steven Whitehouse's avatar
      GFS2: Umount recovery race fix · fe64d517
      Steven Whitehouse authored
      This patch fixes a race condition where we can receive recovery
      requests part way through processing a umount. This was causing
      problems since the recovery thread had already gone away.
      
      Looking in more detail at the recovery code, it was really trying
      to implement a slight variation on a work queue, and that happens to
      align nicely with the recently introduced slow-work subsystem. As a
      result I've updated the code to use slow-work, rather than its own home
      grown variety of work queue.
      
      When using the wait_on_bit() function, I noticed that the wait function
      that was supplied as an argument was appearing in the WCHAN field, so
      I've updated the function names in order to produce more meaningful
      output.
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      fe64d517
  10. 13 May, 2009 3 commits
  11. 12 May, 2009 1 commit
  12. 11 May, 2009 3 commits
  13. 10 May, 2009 12 commits
  14. 09 May, 2009 3 commits