1. 14 7月, 2007 4 次提交
    • E
      [XFS] Clean up function name handling in tracing code · 3a59c94c
      Eric Sandeen 提交于
      Remove the hardcoded "fnames" for tracing, and just embed them in tracing
      macros via __FUNCTION__. Kills a lot of #ifdefs too.
      
      SGI-PV: 967353
      SGI-Modid: xfs-linux-melb:xfs-kern:29099a
      Signed-off-by: NEric Sandeen <sandeen@sandeen.net>
      Signed-off-by: NDavid Chinner <dgc@sgi.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      3a59c94c
    • D
      [XFS] Quota inode has no parent. · b11f94d5
      David Chinner 提交于
      Avoid using a special "zero inode" as the parent of the quota inode as
      this can confuse the filestreams code into thinking the quota inode has a
      parent. We do not want the quota inode to follow filestreams allocation
      rules, so pass a NULL as the parent inode and detect this condition when
      doing stream associations.
      
      SGI-PV: 964469
      SGI-Modid: xfs-linux-melb:xfs-kern:29098a
      Signed-off-by: NDavid Chinner <dgc@sgi.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      b11f94d5
    • D
      [XFS] Concurrent Multi-File Data Streams · 2a82b8be
      David Chinner 提交于
      In media spaces, video is often stored in a frame-per-file format. When
      dealing with uncompressed realtime HD video streams in this format, it is
      crucial that files do not get fragmented and that multiple files a placed
      contiguously on disk.
      
      When multiple streams are being ingested and played out at the same time,
      it is critical that the filesystem does not cross the streams and
      interleave them together as this creates seek and readahead cache miss
      latency and prevents both ingest and playout from meeting frame rate
      targets.
      
      This patch set creates a "stream of files" concept into the allocator to
      place all the data from a single stream contiguously on disk so that RAID
      array readahead can be used effectively. Each additional stream gets
      placed in different allocation groups within the filesystem, thereby
      ensuring that we don't cross any streams. When an AG fills up, we select a
      new AG for the stream that is not in use.
      
      The core of the functionality is the stream tracking - each inode that we
      create in a directory needs to be associated with the directories' stream.
      Hence every time we create a file, we look up the directories' stream
      object and associate the new file with that object.
      
      Once we have a stream object for a file, we use the AG that the stream
      object point to for allocations. If we can't allocate in that AG (e.g. it
      is full) we move the entire stream to another AG. Other inodes in the same
      stream are moved to the new AG on their next allocation (i.e. lazy
      update).
      
      Stream objects are kept in a cache and hold a reference on the inode.
      Hence the inode cannot be reclaimed while there is an outstanding stream
      reference. This means that on unlink we need to remove the stream
      association and we also need to flush all the associations on certain
      events that want to reclaim all unreferenced inodes (e.g. filesystem
      freeze).
      
      SGI-PV: 964469
      SGI-Modid: xfs-linux-melb:xfs-kern:29096a
      Signed-off-by: NDavid Chinner <dgc@sgi.com>
      Signed-off-by: NBarry Naujok <bnaujok@sgi.com>
      Signed-off-by: NDonald Douwsma <donaldd@sgi.com>
      Signed-off-by: NChristoph Hellwig <hch@infradead.org>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      Signed-off-by: NVlad Apostolov <vapo@sgi.com>
      2a82b8be
    • V
      [XFS] Use is_power_of_2 instead of open coding checks · 16a087d8
      Vignesh Babu 提交于
      SGI-PV: 966576
      SGI-Modid: xfs-linux-melb:xfs-kern:28950a
      Signed-off-by: NVignesh Babu <vignesh.babu@wipro.com>
      Signed-off-by: NDavid Chinner <dgc@sgi.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      16a087d8
  2. 08 5月, 2007 3 次提交
    • L
      [XFS] Fix to prevent the notorious 'NULL files' problem after a crash. · ba87ea69
      Lachlan McIlroy 提交于
      The problem that has been addressed is that of synchronising updates of
      the file size with writes that extend a file. Without the fix the update
      of a file's size, as a result of a write beyond eof, is independent of
      when the cached data is flushed to disk. Often the file size update would
      be written to the filesystem log before the data is flushed to disk. When
      a system crashes between these two events and the filesystem log is
      replayed on mount the file's size will be set but since the contents never
      made it to disk the file is full of holes. If some of the cached data was
      flushed to disk then it may just be a section of the file at the end that
      has holes.
      
      There are existing fixes to help alleviate this problem, particularly in
      the case where a file has been truncated, that force cached data to be
      flushed to disk when the file is closed. If the system crashes while the
      file(s) are still open then this flushing will never occur.
      
      The fix that we have implemented is to introduce a second file size,
      called the in-memory file size, that represents the current file size as
      viewed by the user. The existing file size, called the on-disk file size,
      is the one that get's written to the filesystem log and we only update it
      when it is safe to do so. When we write to a file beyond eof we only
      update the in- memory file size in the write operation. Later when the I/O
      operation, that flushes the cached data to disk completes, an I/O
      completion routine will update the on-disk file size. The on-disk file
      size will be updated to the maximum offset of the I/O or to the value of
      the in-memory file size if the I/O includes eof.
      
      SGI-PV: 958522
      SGI-Modid: xfs-linux-melb:xfs-kern:28322a
      Signed-off-by: NLachlan McIlroy <lachlan@sgi.com>
      Signed-off-by: NDavid Chinner <dgc@sgi.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      ba87ea69
    • L
      [XFS] propogate return codes from flush routines · d3cf2094
      Lachlan McIlroy 提交于
      This patch handles error return values in fs_flush_pages and
      fs_flushinval_pages. It changes the prototype of fs_flushinval_pages so we
      can propogate the errors and handle them at higher layers. I also modified
      xfs_itruncate_start so that it could propogate the error further.
      
      SGI-PV: 961990
      SGI-Modid: xfs-linux-melb:xfs-kern:28231a
      Signed-off-by: NLachlan McIlroy <lachlan@sgi.com>
      Signed-off-by: NStewart Smith <stewart@flamingspork.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      d3cf2094
    • E
      [XFS] The last argument "lsn" of xfs_trans_commit() is always called with · 1c72bf90
      Eric Sandeen 提交于
      NULL.
      
      Patch provided by Eric Sandeen.
      
      SGI-PV: 961693
      SGI-Modid: xfs-linux-melb:xfs-kern:28199a
      Signed-off-by: NEric Sandeen <sandeen@sandeen.net>
      Signed-off-by: NLachlan McIlroy <lachlan@sgi.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      1c72bf90
  3. 10 2月, 2007 5 次提交
  4. 21 11月, 2006 1 次提交
  5. 11 11月, 2006 2 次提交
  6. 28 9月, 2006 2 次提交
  7. 28 7月, 2006 1 次提交
  8. 28 6月, 2006 1 次提交
  9. 20 6月, 2006 1 次提交
  10. 19 6月, 2006 1 次提交
  11. 09 6月, 2006 10 次提交
  12. 11 4月, 2006 1 次提交
  13. 29 3月, 2006 1 次提交
  14. 22 3月, 2006 3 次提交
  15. 17 3月, 2006 4 次提交
    • N
      [XFS] endianess annotations for xfs_attr_shortform_t · 3b244aa8
      Nathan Scott 提交于
      SGI-PV: 943272
      SGI-Modid: xfs-linux-melb:xfs-kern:25501a
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NNathan Scott <nathans@sgi.com>
      3b244aa8
    • N
      [XFS] Fix an infinite loop issue in bulkstat when a corrupt inode is · b12dd342
      Nathan Scott 提交于
      detected.  Thanks to Roger Willcocks.
      
      SGI-PV: 951054
      SGI-Modid: xfs-linux-melb:xfs-kern:25477a
      Signed-off-by: NNathan Scott <nathans@sgi.com>
      b12dd342
    • N
      [XFS] Complete transition away from linvfs naming convention, finally. · ec86dc02
      Nathan Scott 提交于
      SGI-PV: 947038
      SGI-Modid: xfs-linux-melb:xfs-kern:25474a
      Signed-off-by: NNathan Scott <nathans@sgi.com>
      ec86dc02
    • M
      [XFS] There are a few problems with the new · 8867bc9b
      Mandy Kirkconnell 提交于
      xfs_bmap_search_multi_extents() wrapper function that I introduced in mod
      xfs-linux:xfs-kern:207393a. The function was added as a wrapper around
      xfs_bmap_do_search_extents() to avoid breaking the top-of-tree CXFS
      interface.  The idea of the function was basically to extract the target
      extent buffer (if muli- level extent allocation mode), then call
      xfs_bmap_do_search_extents() with either a pointer to the first extent in
      the target buffer or a pointer to the first extent in the file, depending
      on which extent mode was being used.  However, in addition to locating the
      target extent record for block bno, xfs_bmap_do_search_extents() also sets
      four parameters needed by the caller: *lastx, *eofp, *gotp, *prevp. 
      Passing only the target extent buffer to xfs_bmap_do_search_extents()
      causes *eofp to be set incorrectly if the extent is at the end of the
      target list but there are actually more extents in the next er_extbuf.
      Likewise, if the extent is the first one in the buffer but NOT the first
      in the file, *prevp is incorrectly set to NULL.  Adding the needed
      functionality to xfs_bmap_search_multi_extents() to re-set any incorrectly
      set fields is redundant and makes the call to xfs_bmap_do_search_extents()
      not make much sense when multi-level extent allocation mode is being used.
       This mod basically extracts the two functional components from
      xfs_bmap_do_search_extents(), with the intent of obsoleting/removing
      xfs_bmap_do_search_extents() after the CXFS mult-level in-core extent
      changes are checked in.  The two components are:  1) The binary search to
      locate the target extent record, and 2) Setting the four parameters needed
      by the caller (*lastx, *eofp, *gotp, *prevp).  Component 1: I created a
      new function in xfs_inode.c called xfs_iext_bno_to_ext(), which executes
      the binary search to find the target extent record.
      xfs_bmap_search_multi_extents() has been modified to call
      xfs_iext_bno_to_ext() rather than xfs_bmap_do_search_extents().  Component
      2: The parameter setting functionality has been added to
      xfs_bmap_search_multi_extents(), eliminating the need for
      xfs_bmap_do_search_extents().  These changes make the removal of
      xfs_bmap_do_search_extents() trival once the CXFS changes are in place. 
      They also allow us to maintain the current XFS interface, using the new
      search function introduced in mod xfs-linux:xfs-kern:207393a.
      
      SGI-PV: 928864
      SGI-Modid: xfs-linux-melb:xfs-kern:207866a
      Signed-off-by: NMandy Kirkconnell <alkirkco@sgi.com>
      Signed-off-by: NNathan Scott <nathans@sgi.com>
      8867bc9b