On 7/4/07, <b class="gmail_sendername">Otavio Salvador</b> <<a href="mailto:otavio@debian.org">otavio@debian.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Otavio Salvador <<a href="mailto:otavio@debian.org">otavio@debian.org</a>> writes:<br><br>> Michael Brennan <<a href="mailto:brennan.brisad@gmail.com">brennan.brisad@gmail.com</a>> writes:<br>><br>>> 2. How should the problem with O_DIRECT on my computer be solved?
<br>>> Open without O_DIRECT or find out the correct alignment in some way?<br>><br>> Hello Michael,<br>><br>> Is you able to reproduce it using lastest kernels or just with 2.4?<br>> Have you tested with lastest
2.4 series too?<br></blockquote></div><br><div>Yes, I have tried the latest kernels from both 2.4 and 2.6 now and<br>I found that 2.4 does not work while 2.6 works fine.<br></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I did some research about it and looks like we're not suppose to use<br>O_DIRECT but madvice or posix_fadvice.</blockquote></span><div><br>What is the main reason this non-buffering mechanism is used in parted?<br>Is it for performance? Or something other, like reducing the risk of
<br>corrupting data?<br>The other partitioning tools I've used seem to use normal write operations<br>and then sync the disks right afterwards, on the other hand, they only write<br>the partition table to disk and does not have the advanced features parted has.
<br><br>Michael</div>