[parted-devel] Failure with O_DIRECT

[Michael Brennan]

On 7/4/07, Otavio Salvador <otavio at debian.org> wrote:
>
> Otavio Salvador <otavio at debian.org> writes:
>
> > Michael Brennan <brennan.brisad at gmail.com> writes:
> >
> >> 2. How should the problem with O_DIRECT on my computer be solved?
> >> Open without O_DIRECT or find out the correct alignment in some way?
> >
> > Hello Michael,
> >
> > Is you able to reproduce it using lastest kernels or just with 2.4?
> > Have you tested with lastest 2.4 series too?
>

Yes, I have tried the latest kernels from both 2.4 and 2.6 now and
I found that 2.4 does not work while 2.6 works fine.

I did some research about it and looks like we're not suppose to use
> O_DIRECT but madvice or posix_fadvice.


What is the main reason this non-buffering mechanism is used in parted?
Is it for performance?  Or something other, like reducing the risk of
corrupting data?
The other partitioning tools I've used seem to use normal write operations
and then sync the disks right afterwards, on the other hand, they only write
the partition table to disk and does not have the advanced features parted
has.

Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/parted-devel/attachments/20070705/e91e6cb3/attachment.htm