On Tue, May 15, 2007 at 01:02:51AM +0100, Hubertus Grobbel wrote: > I found out, that the option O_DIRECT for opening a file on a fat- > filesystem successfully completes. But reading and writing to that > file leads to EINVAL errors (using kernel 2.6.18). Make sure your buffer is page aligned and read/write in multiples of the hard block size (use blockdev --getss to figure out). Erik -- They're all fools. Don't worry. Darwin may be slow, but he'll eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: O_DIRECT for FAT
- From: Hubertus Grobbel <[email protected]>
- Re: O_DIRECT for FAT
- References:
- O_DIRECT for FAT
- From: Hubertus Grobbel <[email protected]>
- O_DIRECT for FAT
- Prev by Date: [PATCH] deprecate memclear_highpage_flush deprecation warnings
- Next by Date: Re: [PATCH 002 of 8] knfsd: exportfs: remove iget abuse
- Previous by thread: Re: O_DIRECT for FAT
- Next by thread: Re: O_DIRECT for FAT
- Index(es):