Up to [Development] / xfs-linux
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.65 / (download) - annotate - [select for diffs], Wed Jun 25 06:15:11 2008 UTC (9 years, 3 months ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
CVS Tags: HEAD
Changes since 1.64: +10 -0
lines
Diff to previous 1.64 (colored)
use minleft when allocating in xfs_bmbt_split() The bmap btree split code relies on a previous data extent allocation (from xfs_bmap_btalloc()) to find an AG that has sufficient space to perform a full btree split, when inserting the extent. When converting unwritten extents we don't allocate a data extent so a btree split will be the first allocation. In this case we need to set minleft so the allocator will pick an AG that has space to complete the split(s). Merge of xfs-linux-melb:xfs-kern:31357a by kenmcd. use minleft when allocating in xfs_bmbt_split()
Revision 1.64 / (download) - annotate - [select for diffs], Mon Apr 28 16:19:36 2008 UTC (9 years, 5 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.63: +5 -8
lines
Diff to previous 1.63 (colored)
Fix check for block zero access in xfs_write_iomap_allocate() The check for block zero access should be done on non-realtime inodes. Fix the logic error in xfs_write_iomap_allocate(), and simplify the logic on all checks for block zero access in xfs_iomap.c Merge of xfs-linux-melb:xfs-kern:30998a by kenmcd. Fix check for block zero access in xfs_write_iomap_allocate().
Revision 1.63 / (download) - annotate - [select for diffs], Mon Apr 21 06:17:24 2008 UTC (9 years, 5 months ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.62: +3 -3
lines
Diff to previous 1.62 (colored)
shrink mrlock_t The writer field is not needed for non_DEBU builds so remove it. While we're at i also clean up the interface for is locked asserts to go through and xfs_iget.c helper with an interface like the xfs_ilock routines to isolated the XFS codebase from mrlock internals. That way we can kill mrlock_t entirely once rw_semaphores grow an islocked facility. Also remove unused flags to the ilock family of functions. Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:30902a by kenmcd. shrink mrlock_t
Revision 1.62 / (download) - annotate - [select for diffs], Wed Apr 9 16:34:37 2008 UTC (9 years, 6 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.61: +5 -2
lines
Diff to previous 1.61 (colored)
Catch errors returned from xfs_bmap_last_offset(). xfs_bmap_last_offset() can fail and return an error. xfs_iomap_write_allocate() fails to detect and propagate the error. Merge of xfs-linux-melb:xfs-kern:30802a by kenmcd. Catch errors returned from xfs_bmap_last_offset().
Revision 1.61 / (download) - annotate - [select for diffs], Mon Nov 5 15:04:07 2007 UTC (9 years, 11 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.60: +5 -5
lines
Diff to previous 1.60 (colored)
optimize XFS_IS_REALTIME_INODE w/o realtime config Use XFS_IS_REALTIME_INODE in more places, and #define it to 0 if CONFIG_XFS_RT is off. This should be safe because mount checks in xfs_rtmount_init: # define xfs_rtmount_init(m) (((mp)->m_sb.sb_rblocks == 0)? 0 : (ENOSYS)) so if we get mounted w/o CONFIG_XFS_RT, no realtime inodes should be encountered after that. Defining XFS_IS_REALTIME_INODE to 0 saves a bit of stack space, presumeably gcc can optimize around the various "if (0)" type checks: xfs_alloc_file_space -8 xfs_bmap_adjacent -16 xfs_bmapi -8 xfs_bmap_rtalloc -16 xfs_bunmapi -28 xfs_free_file_space -64 xfs_imap +8 <-- ? hmm. xfs_iomap_write_direct -12 xfs_qm_dqusage_adjust -4 xfs_qm_vop_chown_reserve -4 Signed-off-by: Eric Sandeen <sandeen@sandeen.net> Merge of xfs-linux-melb:xfs-kern:30014a by kenmcd. Use XFS_IS_REALTIME_INODE() rather than open coding the check.
Revision 1.60 / (download) - annotate - [select for diffs], Fri Nov 2 03:11:36 2007 UTC (9 years, 11 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.59: +50 -25
lines
Diff to previous 1.59 (colored)
Fix transaction overrun during writeback. Prevent transaction overrun in xfs_iomap_write_allocate() if we race with a truncate that overlaps the delalloc range we were planning to allocate. If we race, we may allocate into a hole and that requires block allocation. At this point in time we don't have a reservation for block allocation (apart from metadata blocks) and so allocating into a hole rather than a delalloc region results in overflowing the transaction block reservation. Fix it by only allowing a single extent to be allocated at a time. Merge of xfs-linux-melb:xfs-kern:30005a by kenmcd. Only allow xfs_iomap_write_allocate to allocate a single extent at a time to prevent races with truncate from causing unreserved allocation and hence transaction overruns.
Revision 1.59 / (download) - annotate - [select for diffs], Fri Sep 21 16:10:12 2007 UTC (10 years ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.58: +12 -18
lines
Diff to previous 1.58 (colored)
kill xfs_iocore_t xfs_iocore_t is a structure embedded in xfs_inode. Except for one field it just duplicates fields already in xfs_inode, and there is nothing this abstraction buys us on XFS/Linux. This patch removes it and shrinks source and binary size of xfs aswell as shrinking the size of xfs_inode by 60/44 bytes in debug/non-debug builds. Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29754a by kenmcd. kill xfs_iocore_t
Revision 1.58 / (download) - annotate - [select for diffs], Fri Sep 21 04:08:28 2007 UTC (10 years ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.57: +48 -46
lines
Diff to previous 1.57 (colored)
kill unnessecary ioops indirection Currently there is an indirection called ioops in the XFS data I/O path. Various functions are called by functions pointers, but there is no coherence in what this is for, and of course for XFS itself it's entirely unused. This patch removes it instead and significantly reduces source and binary size of XFS while making maintaince easier. Merge of xfs-linux-melb:xfs-kern:29737a by kenmcd. kill unnessecary ioops indirection
Revision 1.57 / (download) - annotate - [select for diffs], Mon Sep 17 16:04:19 2007 UTC (10 years ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.56: +0 -8
lines
Diff to previous 1.56 (colored)
Kill unused IOMAP_EOF flag Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29705a by kenmcd. kill unused IOMAP_EOF flag
Revision 1.56 / (download) - annotate - [select for diffs], Thu Sep 13 06:11:17 2007 UTC (10 years, 1 month ago) by donaldd.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.55: +2 -12
lines
Diff to previous 1.55 (colored)
kill BMAPI_UNWRITTEN There is no reason to go through xfs_iomap for the BMAPI_UNWRITTEN because it has nothing in common with the other cases. Instead check for the shutdown filesystem in xfs_end_bio_unwritten and perform a direct call to xfs_iomap_write_unwritten (which should be renamed to something more sensible one day) Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29681a by kenmcd. kill BMAPI_UNWRITTEN
Revision 1.55 / (download) - annotate - [select for diffs], Thu Sep 13 06:10:29 2007 UTC (10 years, 1 month ago) by donaldd.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.54: +1 -8
lines
Diff to previous 1.54 (colored)
kill BMAPI_DEVICE There is no reason to go into the iomap machinery just to get the right block device for an inode. Instead look at the realtime flag in the inode and grab the right device from the mount structure. I created a new helper, xfs_find_bdev_for_inode instead of opencoding it because I plan to use it in other places in the future. Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29680a by kenmcd. kill BMAPI_DEVICE
Revision 1.54 / (download) - annotate - [select for diffs], Fri Jun 8 16:04:48 2007 UTC (10 years, 4 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.53: +4 -15
lines
Diff to previous 1.53 (colored)
Cleanup inode extent size hint extraction Merge of xfs-linux-melb:xfs-kern:28866a by kenmcd. Use xfs_get_extsz_hint rather than open coded statements.
Revision 1.53 / (download) - annotate - [select for diffs], Fri Jun 8 16:03:59 2007 UTC (10 years, 4 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.52: +8 -14
lines
Diff to previous 1.52 (colored)
Prevent ENOSPC from aborting transactions that need to succeed
During delayed allocation extent conversion or unwritten extent
conversion, we need to reserve some blocks for transactions
reservations. We need to reserve these blocks in case a btree
split occurs and we need to allocate some blocks.
Unfortunately, we've only ever reserved the number of data blocks we
are allocating, so in both the unwritten and delalloc case we can
get ENOSPC to the transaction reservation. This is bad because in
both cases we cannot report the failure to the writing application.
The fix is two-fold:
1 - leverage the reserved block infrastructure XFS already
has to reserve a small pool of blocks by default to allow
specially marked transactions to dip into when we are at
ENOSPC.
Default setting is min(5%, 1024 blocks).
2 - convert critical transaction reservations to be allowed
to dip into this pool. Spots changed are delalloc
conversion, unwritten extent conversion and growing a
filesystem at ENOSPC.
This also allows growing the filesytsem to succeed at ENOSPC.
Merge of xfs-linux-melb:xfs-kern:28865a by kenmcd.
Allow unwritten extent conversion and delayed allocation tranactions
to use reserved space instead of silently failing at ENOSPC.
Revision 1.52 / (download) - annotate - [select for diffs], Fri Mar 30 04:04:14 2007 UTC (10 years, 6 months ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.51: +4 -4
lines
Diff to previous 1.51 (colored)
Fix to prevent the notorious 'NULL files' problem after a crash. 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. Merge of xfs-linux-melb:xfs-kern:28322a by kenmcd. Fix to prevent the notorious 'NULL files' problem after a crash.
Revision 1.51 / (download) - annotate - [select for diffs], Fri Mar 2 02:59:33 2007 UTC (10 years, 7 months ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.50: +3 -4
lines
Diff to previous 1.50 (colored)
The last argument "lsn" of xfs_trans_commit() is always called with NULL. Patch provided by Eric Sandeen. Signed-off-by: Eric Sandeen <sandeen@sandeen.net> Merge of xfs-linux-melb:xfs-kern:28199a by kenmcd. The last argument "lsn" of xfs_trans_commit() is always called with NULL. Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Revision 1.50 / (download) - annotate - [select for diffs], Wed Feb 7 02:50:13 2007 UTC (10 years, 8 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.49: +0 -2
lines
Diff to previous 1.49 (colored)
Remove unused header files for MAC and CAP checking functionality. xfs_mac.h and xfs_cap.h provide definitions and macros that aren't used anywhere in XFS at all. They are left-overs from "to be implement at some point in the future" functionality that Irix XFS has. If this functionality ever goes into Linux, it will be provided at a different layer, most likely through the security hooks in the kernel so we will never need this functionality in XFS. Patch provided by Eric Sandeen (sandeen@sandeen.net). Signed-off-by: Eric Sandeen <sandeen@sandeen.net> Merge of xfs-linux-melb:xfs-kern:28036a by kenmcd. Remove unused xfs_cap.h/xfs_mac.h header files. Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Revision 1.49 / (download) - annotate - [select for diffs], Tue Feb 6 14:35:53 2007 UTC (10 years, 8 months ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.48: +3 -5
lines
Diff to previous 1.48 (colored)
Remove unused argument to xfs_bmap_finish The firstblock argument to xfs_bmap_finish is not used by that function. Remove it and cleanup the code a bit. Patch provided by Eric Sandeen. Signed-off-by: Eric Sandeen <sandeen@sandeen.net> Merge of xfs-linux-melb:xfs-kern:28034a by kenmcd. Remove unused firstblock argument from xfs_bmap_finish. Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Revision 1.48 / (download) - annotate - [select for diffs], Fri Aug 18 04:02:25 2006 UTC (11 years, 1 month ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.47: +33 -54
lines
Diff to previous 1.47 (colored)
Improve error handling for the zero-fsblock extent detection code. Merge of xfs-linux-melb:xfs-kern:26802a by kenmcd.
Revision 1.47 / (download) - annotate - [select for diffs], Thu Jun 15 03:58:11 2006 UTC (11 years, 4 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.46: +0 -2
lines
Diff to previous 1.46 (colored)
Remove version 1 directory code. Never functioned on Linux, just pure bloat. Merge of xfs-linux-melb:xfs-kern:26251a by kenmcd.
Revision 1.46 / (download) - annotate - [select for diffs], Thu Apr 13 10:13:05 2006 UTC (11 years, 6 months ago) by olaf
Branch: MAIN
Changes since 1.45: +12 -12
lines
Diff to previous 1.45 (colored)
Add parameters to xfs_bmapi() and xfs_bunmapi() to have them report the range spanned by modifications to the in-core extent map. Add XFS_BUNMAPI() and XFS_SWAP_EXTENTS() macros that call xfs_bunmapi() and xfs_swap_extents() via the ioops vector. Change all calls that may modify the in-core extent map for the data fork to go through the ioops vector. This allows a cache of extent map data to be kept in sync. Provide extra parameter for XFS_BMAPI(). Replace invocations of xfs_bmapi() with XFS_BMAPI().
Revision 1.45 / (download) - annotate - [select for diffs], Mon Mar 20 17:11:22 2006 UTC (11 years, 6 months ago) by yingping
Branch: MAIN
Changes since 1.44: +1 -1
lines
Diff to previous 1.44 (colored)
Fixing KDB's xrwtrc command, also added the current process id into the trace. Added current process id to xfs_iomap_enter_trace
Revision 1.44 / (download) - annotate - [select for diffs], Wed Jan 25 00:34:27 2006 UTC (11 years, 8 months ago) by cattelan
Branch: MAIN
Changes since 1.43: +0 -1
lines
Diff to previous 1.43 (colored)
Bring the XFS code in sync with the changed from 2.6.16-rc1
Revision 1.43 / (download) - annotate - [select for diffs], Wed Dec 21 14:35:09 2005 UTC (11 years, 9 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.42: +22 -12
lines
Diff to previous 1.42 (colored)
Fix compiler warnings from older gcc versions wrt printfalike arguments. Merge of xfs-linux-melb:xfs-kern:24901a by kenmcd.
Revision 1.42 / (download) - annotate - [select for diffs], Fri Dec 2 02:48:45 2005 UTC (11 years, 10 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.41: +1 -0
lines
Diff to previous 1.41 (colored)
Sort out cosmetic differences between user and kernel copies of some sources. Merge of xfs-linux-melb:xfs-kern:24659a by kenmcd.
Revision 1.41 / (download) - annotate - [select for diffs], Fri Nov 11 14:16:20 2005 UTC (11 years, 11 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.40: +211 -179
lines
Diff to previous 1.40 (colored)
Implement the di_extsize allocator hint for non-realtime files as well. Also provides a mechanism for inheriting this property from the parent directory for new files. Merge of xfs-linux-melb:xfs-kern:24367a by kenmcd.
Revision 1.40 / (download) - annotate - [select for diffs], Fri Oct 21 15:50:16 2005 UTC (11 years, 11 months ago) by sandeen
Branch: MAIN
Changes since 1.39: +0 -8
lines
Diff to previous 1.39 (colored)
remove unused code from xfs_iomap_write_direct remove unused code from xfs_iomap_write_direct
Revision 1.39 / (download) - annotate - [select for diffs], Mon Sep 26 15:00:47 2005 UTC (12 years ago) by sandeen
Branch: MAIN
Changes since 1.38: +4 -8
lines
Diff to previous 1.38 (colored)
Remove dead code in xfs_iomap_write_direct; save some stack Don't put more imaps on the stack than we're going to use, take out some unused vars & calculations done on them
Revision 1.38 / (download) - annotate - [select for diffs], Fri Sep 23 03:51:28 2005 UTC (12 years ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.37: +12 -26
lines
Diff to previous 1.37 (colored)
Update license/copyright notices to match the prefered SGI boilerplate. Merge of xfs-linux-melb:xfs-kern:23903a by kenmcd.
Revision 1.37 / (download) - annotate - [select for diffs], Fri Sep 23 03:48:50 2005 UTC (12 years ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.36: +6 -7
lines
Diff to previous 1.36 (colored)
Remove xfs_macros.c, xfs_macros.h, rework headers a whole lot. Merge of xfs-linux-melb:xfs-kern:23901a by kenmcd.
Revision 1.36 / (download) - annotate - [select for diffs], Mon Sep 5 03:47:46 2005 UTC (12 years, 1 month ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.35: +2 -3
lines
Diff to previous 1.35 (colored)
Fix incorrect use of BMAPI_READ in unwritten extent handling (luckily just cosmetic). Merge of xfs-linux-melb:xfs-kern:23718a by kenmcd.
Revision 1.35 / (download) - annotate - [select for diffs], Thu Jul 7 03:42:17 2005 UTC (12 years, 3 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.34: +8 -9
lines
Diff to previous 1.34 (colored)
Fix regression in transaction reserved-block accounting for direct writes. Merge of xfs-linux-melb:xfs-kern:23088a by kenmcd.
Revision 1.34 / (download) - annotate - [select for diffs], Mon Jun 20 03:44:04 2005 UTC (12 years, 3 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.33: +27 -38
lines
Diff to previous 1.33 (colored)
Merge fixes into realtime quota code, since one/two reported, still not enabled though. Merge of xfs-linux-melb:xfs-kern:22900a by kenmcd.
Revision 1.33 / (download) - annotate - [select for diffs], Fri Apr 29 15:10:40 2005 UTC (12 years, 5 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.32: +4 -4
lines
Diff to previous 1.32 (colored)
Cleanup use of loff_t vs xfs_off_t in the core code. Merge of xfs-linux-melb:xfs-kern:22378a by kenmcd.
Revision 1.32 / (download) - annotate - [select for diffs], Fri Apr 29 15:09:58 2005 UTC (12 years, 5 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.31: +11 -9
lines
Diff to previous 1.31 (colored)
Use the right offset when ensuring a delayed allocate conversion has covered the offset originally requested. Can cause data corruption when multiple processes are performing writeout on different areas of the same file. Quite difficult to hit though. Merge of xfs-linux-melb:xfs-kern:22377a by kenmcd.
Revision 1.31 / (download) - annotate - [select for diffs], Thu Mar 17 03:45:25 2005 UTC (12 years, 6 months ago) by cattelan
Branch: MAIN
Changes since 1.30: +3 -1
lines
Diff to previous 1.30 (colored)
Fix a bug in xfs_iomap for extent handling of write cases. This may be the cause of several open PV's of incorrect delay flags being set and then tripping asserts. Do not return a delay alloc extent when the caller is asking to do a write.
Revision 1.30 / (download) - annotate - [select for diffs], Tue Aug 3 04:06:25 2004 UTC (13 years, 2 months ago) by nathans
Branch: MAIN
Changes since 1.29: +4 -2
lines
Diff to previous 1.29 (colored)
Fix accidental reverting of sync write preallocations.
Revision 1.29 / (download) - annotate - [select for diffs], Mon Aug 2 17:20:16 2004 UTC (13 years, 2 months ago) by sandeen
Branch: MAIN
Changes since 1.28: +64 -4
lines
Diff to previous 1.28 (colored)
Code checks to trap access to fsb zero. Added checks to trap access to block zero in xfs_iomap_write_direct,xfs_iomap_write_delay,xfs_iomap_write_allocate and xfs_iomap_write_unwritten.
Revision 1.28 / (download) - annotate - [select for diffs], Thu Jul 8 07:06:40 2004 UTC (13 years, 3 months ago) by nathans
Branch: MAIN
Changes since 1.27: +2 -1
lines
Diff to previous 1.27 (colored)
Fix a possible data loss issue after an unaligned unwritten extent write.
Revision 1.27 / (download) - annotate - [select for diffs], Tue Jun 22 23:11:39 2004 UTC (13 years, 3 months ago) by overby
Branch: MAIN
Changes since 1.26: +19 -4
lines
Diff to previous 1.26 (colored)
Permit buffered writes to the real-time subvolume. Add transaction space reservation of real-time subvolume extents, and split out the space reservation for what is metadata and what is user data, putting the user data on the real-time when appropriate.
Revision 1.26 / (download) - annotate - [select for diffs], Wed May 12 21:25:17 2004 UTC (13 years, 5 months ago) by jpk
Branch: MAIN
Changes since 1.25: +20 -1
lines
Diff to previous 1.25 (colored)
Add support for allocating additional file space in stripe width sized chunks. A new fstab/mount option, "swalloc" has been defined. If specified when mounting a striped file system, allocation requests will be rounded up to a stripe width if the file size is >= stripe width, and the data is being appended to eof. The 'swalloc' option is "off" by default. Add support for the stripe width allocation option: swalloc. If the "swalloc" option was specified on the mount, the file size >= stripe width, and allocating past the allocation eof, then roundup the allocation request to a stripe width boundary (PV 783527)
Revision 1.25 / (download) - annotate - [select for diffs], Tue May 4 19:24:37 2004 UTC (13 years, 5 months ago) by jpk
Branch: MAIN
Changes since 1.24: +27 -1
lines
Diff to previous 1.24 (colored)
xfs_iomap_write_delay() was doing speculative allocations without checking if there were any real blocks already in the speculative allocation area. This could result in an allocation that overlaps pre-allocated space. This would result in an ASSERT failure in debug kernels, or invalid output from xfs_bmap. The code will now only do speculative allocation if we are writing beyond the current allocation eof. xfs_iomap_write_delay() was doing speculative allocations without checking if there were any real blocks already in the speculative allocation area. This could result in an allocation that overlaps pre-allocated space. The code will now only do speculative allocation if we are writing beyond the current allocation eof. (PV 913877)
Revision 1.24 / (download) - annotate - [select for diffs], Tue Apr 6 18:37:10 2004 UTC (13 years, 6 months ago) by jpk
Branch: MAIN
Changes since 1.23: +4 -3
lines
Diff to previous 1.23 (colored)
Correct the (file size >= stripe unit) check in xfs_iomap_write_delay(). It was comparing the file size, in BYTES, against the stripe unit size, in FSBs. (PV 911469)
Revision 1.23 / (download) - annotate - [select for diffs], Tue Feb 10 05:51:00 2004 UTC (13 years, 8 months ago) by nathans
Branch: MAIN
Changes since 1.22: +91 -10
lines
Diff to previous 1.22 (colored)
Add I/O path tracing code, twas useful in diagnosing that last unwritten extent problem.
Revision 1.22 / (download) - annotate - [select for diffs], Tue Dec 16 01:05:04 2003 UTC (13 years, 10 months ago) by cattelan
Branch: MAIN
Changes since 1.21: +795 -0
lines
Diff to previous 1.21 (colored)
Move the files around to finalize the 2.4/2.6 merge linux/xfs_iomap.c 1.20 Renamed to xfs_iomap.c
Revision 1.21 / (download) - annotate - [select for diffs], Tue Dec 16 00:57:46 2003 UTC (13 years, 10 months ago) by cattelan
Branch: MAIN
Changes since 1.20: +0 -795
lines
Diff to previous 1.20 (colored)
Delete imported files so they can re-named
Revision 1.20 / (download) - annotate - [select for diffs], Tue Nov 18 22:04:32 2003 UTC (13 years, 10 months ago) by cattelan
Branch: MAIN
Changes since 1.19: +46 -45
lines
Diff to previous 1.19 (colored)
move the iomap data structures out of pagebuf Use the new iomap flags and data structures
Revision 1.19 / (download) - annotate - [select for diffs], Tue Nov 18 01:30:09 2003 UTC (13 years, 10 months ago) by nathans
Branch: MAIN
Changes since 1.18: +2 -6
lines
Diff to previous 1.18 (colored)
Move Linux-version specific code out of xfs_iomap.c so that it can become part of the XFS core code.
Revision 1.18 / (download) - annotate - [select for diffs], Tue Nov 18 01:02:59 2003 UTC (13 years, 10 months ago) by nathans
Branch: MAIN
Changes since 1.17: +22 -11
lines
Diff to previous 1.17 (colored)
Backport minor 2.6 changes to the iomap interface to keep code more in sync.
Revision 1.17 / (download) - annotate - [select for diffs], Mon Nov 10 23:24:46 2003 UTC (13 years, 11 months ago) by nathans
Branch: MAIN
Changes since 1.16: +3 -3
lines
Diff to previous 1.16 (colored)
Fix a deadlock while writing when low on free space. Use the filemap_fdatawrite interface for flushing delayed allocate space so that we do not deadlock on pages locked by the generic write code.
Revision 1.16 / (download) - annotate - [select for diffs], Thu Aug 21 19:47:57 2003 UTC (14 years, 1 month ago) by sandeen
Branch: MAIN
Changes since 1.15: +2 -2
lines
Diff to previous 1.15 (colored)
Re-work xfs stats macros to support per-cpu data
Revision 1.15 / (download) - annotate - [select for diffs], Tue Aug 19 03:31:29 2003 UTC (14 years, 1 month ago) by nathans
Branch: MAIN
Changes since 1.14: +1 -1
lines
Diff to previous 1.14 (colored)
Fix a harmless typo - we were using a pagebuf flag not a bmap flag here; fortunately they have the same value (2).
Revision 1.14 / (download) - annotate - [select for diffs], Thu Jul 10 02:03:25 2003 UTC (14 years, 3 months ago) by nathans
Branch: MAIN
Changes since 1.13: +5 -2
lines
Diff to previous 1.13 (colored)
Make absolutely sure we don't attempt to access beyond the end of the maximum file size limit. This could happen previously with the space alloc heuristic for delalloc beyond the end of file.
Revision 1.13 / (download) - annotate - [select for diffs], Fri Jun 27 18:04:26 2003 UTC (14 years, 3 months ago) by cattelan
Branch: MAIN
Changes since 1.12: +784 -0
lines
Diff to previous 1.12 (colored)
The Big Move linux/fs/xfs/linux/xfs_iomap.c 1.11 Renamed to linux/xfs_iomap.c
Revision 1.12 / (download) - annotate - [select for diffs], Fri Jun 27 17:57:21 2003 UTC (14 years, 3 months ago) by cattelan
Branch: MAIN
CVS Tags: DENUKE
Changes since 1.11: +0 -784
lines
Diff to previous 1.11 (colored)
Nuke
Revision 1.11 / (download) - annotate - [select for diffs], Thu May 1 16:22:06 2003 UTC (14 years, 5 months ago) by cattelan
Branch: MAIN
CVS Tags: XFS-1_3_0pre1
Changes since 1.10: +37 -1
lines
Diff to previous 1.10 (colored)
Rework the way xfs includes xfs_<blah>.h headers. This reduces a lot of the compile dependenciesÂ, and should reduce some of the "recompile all" situations.
Revision 1.10 / (download) - annotate - [select for diffs], Tue Apr 22 01:31:21 2003 UTC (14 years, 5 months ago) by lord
Branch: MAIN
Changes since 1.9: +2 -2
lines
Diff to previous 1.9 (colored)
missed a mapping from PBF_SYNC to BMAP_SYNC in the full filesystem path. Merge of 2.4.x-xfs-kern:slinx:146483a by lord. move from PBF_SYNC to BMAP_SYNC when attempting to fill a filesystem completely.
Revision 1.9 / (download) - annotate - [select for diffs], Fri Apr 18 14:10:22 2003 UTC (14 years, 5 months ago) by lord
Branch: MAIN
Changes since 1.8: +23 -18
lines
Diff to previous 1.8 (colored)
A number of unwritten extent fixes, fix some reference count and locking issues, also make allocation interface always go into core xfs via the same route rather than having a distinct interface for unwritten extents. switch allocator to its own set of control flags, merge the unwritten extent path into the BMAP call more fully than it was.
Revision 1.8 / (download) - annotate - [select for diffs], Tue Apr 15 23:16:46 2003 UTC (14 years, 6 months ago) by cattelan
Branch: MAIN
Changes since 1.7: +2 -2
lines
Diff to previous 1.7 (colored)
Whitespace cleanup Clean up some whitespace... revert some whitespace changes from previous whitespace cleanup (incorrect tabs)
Revision 1.7 / (download) - annotate - [select for diffs], Mon Mar 17 06:02:57 2003 UTC (14 years, 7 months ago) by nathans
Branch: MAIN
Changes since 1.6: +13 -21
lines
Diff to previous 1.6 (colored)
Separate the quota source into its own subdirectory ala dmapi. Push a bunch of quota- and dmapi-specific code down into these subdirs which previously was compiled into the core XFS code, and don't descend into these subdirs if options config'd off. Separate the quota source into its own subdirectory ala dmapi. Push a bunch of quota- and dmapi-specific code down into these subdirs which previously was compiled into the core XFS code, and don't descend into these subdirs if options config'd off.
Revision 1.6 / (download) - annotate - [select for diffs], Tue Mar 4 20:15:43 2003 UTC (14 years, 7 months ago) by overby
Branch: MAIN
Changes since 1.5: +12 -1
lines
Diff to previous 1.5 (colored)
Add error reporting calls in error paths that return EFSCORRUPTED
Revision 1.5 / (download) - annotate - [select for diffs], Mon Feb 3 20:10:40 2003 UTC (14 years, 8 months ago) by lord
Branch: MAIN
Changes since 1.4: +7 -1
lines
Diff to previous 1.4 (colored)
cleanup delayed allocate write path a little and fix some small bugs in there. Add support for a trylock case in the release page path.
Revision 1.4 / (download) - annotate - [select for diffs], Mon Dec 16 05:46:35 2002 UTC (14 years, 9 months ago) by nathans
Branch: MAIN
Changes since 1.3: +11 -12
lines
Diff to previous 1.3 (colored)
Some cleanup, some more unwritten extent related changes. Minor cleanup and some unwritten extent related changes.
Revision 1.3 / (download) - annotate - [select for diffs], Wed Dec 11 17:27:32 2002 UTC (14 years, 10 months ago) by lord
Branch: MAIN
Changes since 1.2: +493 -655
lines
Diff to previous 1.2 (colored)
rework iocore infrastructure, remove some code and make it more orthogonal. In addition, add some of the hooks for unwritten extents. Merge of 2.4.x-xfs-dev:slinx:134603a by lord. rework iocore to be more orthogonal, add an unwritten extent conversion operation.
Revision 1.2 / (download) - annotate - [select for diffs], Mon Dec 2 01:18:39 2002 UTC (14 years, 10 months ago) by nathans
Branch: MAIN
Changes since 1.1: +36 -31
lines
Diff to previous 1.1 (colored)
Cleanup after initially investigating unwritten extents. Fix several incorrect comments, make declarations consistent.
Revision 1.1 / (download) - annotate - [select for diffs], Wed Oct 30 18:50:40 2002 UTC (14 years, 11 months ago) by lord
Branch: MAIN
break out the allocator specific parts of the xfs I/O path into a separate file, xfs_iomap.c out of xfs_lrw.c. Remove some parts of the code which were not doing anything for us. This is step one in some major reorgs of this code. move allocator based calls here from xfs_lrw.c