=== RELEASE 0.9.5 ===

Thu Mar 22 23:56:33 MET 2007 mikulas

	Fixed an error when freeing extent that was larger than 2TB and block
	size was larger than 512. The error couldn't lead to data corruption,
	only to the situation that part of the extent was not freed and error
	message was written to log

Tue Feb 20 16:27:38 MET 2007 mikulas

	NEW_WORKQUEUE should be defined from 2.6.20 kernels, not from 2.6.19
	Fixed compilation problems with 2.6.19

=== RELEASE 0.9.4 ===

Sun Jan  7 22:16:05 CET 2007 mikulas

	Make it compile on kernel 2.6.19 and 2.6.20-rc

Sun Jan  7 21:13:47 CET 2007 mikulas

	Changed an inode allocation from GFP_KERNEL to GFP_NOFS --- removes a
	deadlock possibility and creates a failure possibility (that most other
	filesystems also have)

	It should be probably changed to allocate inode outside the lock with
	GFP_KERNEL

Sun Jan  7 20:30:41 MET 2007 mikulas

	Fixed abuse of i_blkbits --- it would cause error on 2.6.19 but it
	didn't compile anyway

=== RELEASE 0.9.3 ===

Wed Jan  3 05:25:29 MET 2007 mikulas

	Directories were corrupted and/or kernel locked up if someone tried to
	create filename longer than 255 characters, now it returns ENAMETOOLONG
	(found with fsstress)

Tue Jan  2 03:05:08 CET 2007 mikulas

	Fixed getting bad hints on allocator (the bug didn't damage data but
	lead to fragmentation and bad performance)

Tue Jan  2 02:07:49 MET 2007 mikulas

	Tree structure changed so that utilities are in separate subdirectories
	(the conding style is still pending change, but I want to do some
	testing after that)

Tue Jan  2 01:26:06 MET 2007 mikulas
	
	Reverted 64-bit inode numbers until -EOVERFLOW is resolved

Sat Dec 23 23:27:53 MET 2006 mikulas

	Fixed readdir looping when excessive hash collisions happened

Sat Dec 23 22:39:45 MET 2006 mikulas

	spadfsck fixes:
	Fixed crash when root directory was dnode (approx > 80 entries)
	Fixed memory leak (only noticeable with --debug-malloc)
	Fixed ininite loop during apage rebuild
	When user declined to fix errors, it could errorneously report
		unreliable device
	When allocating chains (this could only happen because of hash
		mismatch), it did not correctly set prev pointer
	When recovering directories, it did set badly up-dnode pointer (and
		set it again correctly on second run)

Sat Dec 23 21:02:09 MET 2006 mikulas

	Return 64-bit inode numbers on 2.6.19
	Reduced ino_t collision possibility (to devices > 256Gib) on previous
	kernels or on old applications that use old 32-bit ino_t

Sat Dec 23 20:18:01 MET 2006 mikulas

	Inode counts in statfs now report total and free blocks in metadata zone
	(but the filesystem is able to operate even if it runs out of metadata
	zone and there is free space in other zones)

	I hope that 0 free inodes statistics won't confuse applications,
	according to POSIX they shouldn't rely on statvfs results

Sat Dec 23 20:15:56 MET 2006 mikulas

	Fixed possibility that readdir skips some entries if directory is split
	between successive readdir calls

Sat Dec 23 04:16:38 MET 2006 mikulas

	Fixed reading memory few bytes beyond buffer end

Sun Dec 10 21:06:25 cet 2006 mikulas

	Added comments to code

Sun Nov  5 01:10:09 MET 2006 mikulas

	Removed a forgotten debug print from spadfsck

=== RELEASE 0.9.2 ===

Fri Nov  3 19:37:43 MET 2006 mikulas

	Use largefile when available instead of _llseek (some broken newer
	systems don't have _syscall macros)
	Fix compile of utilities with libc5

Fri Nov  3 19:36:54 MET 2006 Jan Engelhardt <jengelh@linux01.gwdg.de>

	Build using tools from modules/kernel-version/build directory, not from
	kernel source

=== RELEASE 0.9.1 ===

Fri Nov  3 02:12:31 CET 2006 mikulas

	Fixed compilation on 2.6.18 and 2.6.19rc kernels

=== RELEASE 0.9.0 ===

Fri Nov  2 22:44:17 MET 2006 mikulas

	First public release

vim: textwidth=80
