1. 20 8月, 2008 1 次提交
  2. 16 8月, 2008 1 次提交
  3. 27 7月, 2008 1 次提交
  4. 02 8月, 2008 2 次提交
    • T
      ext4: don't assume extents can't cross block groups when truncating · 34071da7
      Theodore Ts'o 提交于
      With the FLEX_BG layout, there is no reason why extents can't cross
      block groups, so make the truncate code reserve enough credits so we
      don't BUG if we come across such an extent.
      Signed-off-by: N"Theodore Ts'o" <tytso@mit.edu>
      34071da7
    • T
      ext4: Fix ext4_ext_journal_restart() · 0123c939
      Theodore Ts'o 提交于
      The ext4_ext_journal_restart() is a convenience function which checks
      to see if the requested number of credits is present, and if so it
      closes the current transaction and attaches the current handle to the
      new transaction.  Unfortunately, it wasn't proprely checking the
      return value from ext4_journal_extend(), so it was starting a new
      transaction when one was not necessary, and returning an error when
      all that was necessary was to restart the handle with a new
      transaction.
      Signed-off-by: N"Theodore Ts'o" <tytso@mit.edu>
      0123c939
  5. 03 8月, 2008 1 次提交
  6. 12 7月, 2008 1 次提交
  7. 15 7月, 2008 1 次提交
    • M
      ext4: delayed allocation ENOSPC handling · d2a17637
      Mingming Cao 提交于
      This patch does block reservation for delayed
      allocation, to avoid ENOSPC later at page flush time.
      
      Blocks(data and metadata) are reserved at da_write_begin()
      time, the freeblocks counter is updated by then, and the number of
      reserved blocks is store in per inode counter.
              
      At the writepage time, the unused reserved meta blocks are returned
      back. At unlink/truncate time, reserved blocks are properly released.
      
      Updated fix from  Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
      to fix the oldallocator block reservation accounting with delalloc, added
      lock to guard the counters and also fix the reservation for meta blocks.
      Signed-off-by: NAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
      Signed-off-by: NMingming Cao <cmm@us.ibm.com>
      Signed-off-by: NTheodore Ts'o <tytso@mit.edu>
      d2a17637
  8. 12 7月, 2008 9 次提交
  9. 30 4月, 2008 3 次提交
  10. 17 4月, 2008 2 次提交
  11. 30 4月, 2008 1 次提交
  12. 29 4月, 2008 3 次提交
  13. 17 4月, 2008 1 次提交
  14. 29 4月, 2008 1 次提交
  15. 17 4月, 2008 1 次提交
  16. 26 2月, 2008 2 次提交
  17. 16 2月, 2008 1 次提交
    • V
      ext4: modify block allocation algorithm for the last group · 74d3487f
      Valerie Clement 提交于
      When a directory inode is allocated in the last group and the last group
      contains less than s_blocks_per_group blocks, the initial block allocated
      for the directory is not always allocated in the same group as the
      directory inode, but in one of the first groups of the filesystem (group 1
      for example).
      Depending on the current process's pid, ext4_find_near() and 
      ext4_ext_find_goal() can return a block number greater than the maximum
      blocks count in the filesystem and in that case the block will be not
      allocated in the same group as the inode.
      
      The following patch fixes the problem.
      
      Should the modification also be done in ext2/3 code?
      Signed-off-by: NValerie Clement <valerie.clement@bull.net>
      Signed-off-by: NMingming Cao <cmm@us.ibm.com>
      Signed-off-by: N"Theodore Ts'o" <tytso@mit.edu>
      74d3487f
  18. 22 2月, 2008 1 次提交
  19. 26 2月, 2008 1 次提交
  20. 16 2月, 2008 1 次提交
  21. 29 1月, 2008 5 次提交