Re: Phoronix test

Re: Phoronix test

[Alex Davis]

tytso said:
>Of course, if the crappy proprietary video driver from ATI (or Nvidia)
>scribbled garbage over cached inode tables which were then written
>back to disk, there's not much anyone can do about it, no matter what
>file system they were running.

According to the story, Phoronix were using the open source ATI drivers
for all testing.


I code, therefore I am


      

Re: Phoronix test

[Marco]

What commit is responsible for the boost in IO thread tester shown on
phoronix (at 31/01/2010)?
http://www.phoromatic.com/kernel-tracker.php

And is really ext4 so unreliable as they say in here?:
http://www.phoronix.com/scan.php?page=news_item&px=Nzk0OA

It happens also to me using git master: several times my GPU goes wild
(i915) and the only thing to do is press the halt button. And ext4
sometimes looses data, without doing a fsck at restart.
Is there a way to know something went wrong, even if fsck did not say anything?

Bye
Marco

Re: Phoronix test

[tytso]

On Tue, Feb 02, 2010 at 04:20:07PM +0100, Marco wrote:
> 
> And is really ext4 so unreliable as they say in here?:
> http://www.phoronix.com/scan.php?page=news_item&px=Nzk0OA
> 
> It happens also to me using git master: several times my GPU goes
> wild (i915) and the only thing to do is press the halt button. And
> ext4 sometimes looses data, without doing a fsck at restart.  Is
> there a way to know something went wrong, even if fsck did not say
> anything?

If you can reliably reproduce data failure after a crash that involves
a file containing existing data (i.e., not a file that was being
actively written at the time of the crash), I would certainly like to
know about it.  

If the Phoronix people had written to me (as far as I know, they
haven't bothered to send mail to me or the linux-ext4 list), I would
have told them that if they lost information that was located in the
same directory as one that was beeing modified, but those files hadn't
been written recently (not even in the same ext4 mount session), to
shutdown the system, and run fsck on the file system, and that
hopefully the files would appear in lost+found.

Of course, if the crappy proprietary video driver from ATI (or Nvidia)
scribbled garbage over cached inode tables which were then written
back to disk, there's not much anyone can do about it, no matter what
file system they were running.

My guess is that the reason why they didn't bother sending e-mail to
the developers first is they wanted lots of web hits since they get
their revenue from web ads (and that's more important than the lost
data), but maybe that's just me being cynical....

       	   	 	     	      - Ted