Messages in this thread |  | | | Subject | Re: AIO, DIO fsx tests failures on 2.6.19-rc1-mm1 | | From | Badari Pulavarty <> | | Date | Mon, 16 Oct 2006 13:38:19 -0700 |
| |
On Mon, 2006-10-16 at 13:13 -0700, Zach Brown wrote: > > Here is the easiest case to fix first :) > > simple DIO wrote more than asked for :( > > > > elm3b29:~ # /root/fsx-linux -N 10000 -o 128000 -r 2048 -w 4096 -Z -R -W > > jnk > > mapped writes DISABLED > > truncating to largest ever: 0x32740 > > truncating to largest ever: 0x39212 > > truncating to largest ever: 0x3bae9 > > short write: 0x17000 bytes instead of 0x14000 <<<<<< > > So the answer is that -rc1-mm1 doesn't quite have the most recent > version of this patch. Grab the final patch at the end of this post > from Andrew: > > http://lkml.org/lkml/2006/10/11/234 > > It fixes up a misunderstanding that came from > generic_file_buffered_write()'s habit of adding its 'written' input into > the amount of bytes it announces having written in its return value. > > From mm-commits it looks like -mm2 will have the full patch. >
Hmm.. with that patch applied, I still have fsx failures. This time read() returning -EINVAL. Are there any other fixes missing in -mm ?
Thanks, Badari
elm3b29:~ # /root/fsx-linux -N 10000 -o 128000 -r 2048 -w 4096 -Z -R -W jnkI mapped writes DISABLED truncating to largest ever: 0x32740 truncating to largest ever: 0x39212 truncating to largest ever: 0x3bae9 truncating to largest ever: 0x3c1e3 truncating to largest ever: 0x3d1cd truncating to largest ever: 0x3e8b8 truncating to largest ever: 0x3ed14 truncating to largest ever: 0x3f9c2 truncating to largest ever: 0x3ff9f doread: read: Invalid argument Segmentation fault
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |