Page 1 of 7 123 ... LastLast
Results 1 to 10 of 67

Thread: EXT4 Lets Us Down, There Goes Our R600/700 Mesa Tests

  1. #1
    Join Date
    Jan 2007
    Posts
    14,543

    Default EXT4 Lets Us Down, There Goes Our R600/700 Mesa Tests

    Phoronix: EXT4 Lets Us Down, There Goes Our R600/700 Mesa Tests

    For the past several days benchmarks have been going on a plethora of ATI Radeon HD 2000/3000/4000 (R600/700 generation) graphics cards as well as some of the older Radeon X1000 (R500) hardware for reference. All of this testing has been done with the current open-source ATI driver stack with Mesa to show where the performance is at for the H1'2010 Linux distributions...

    http://www.phoronix.com/vr.php?view=Nzk0OA

  2. #2
    Join Date
    Mar 2009
    Posts
    141

    Default

    Alright already. We get it. Ext4 sucks. Quitcherbitchin' about it in every other article.

  3. #3
    Join Date
    Nov 2007
    Location
    Die trolls, die!
    Posts
    525

    Default reisub

    I can't guarantee that it would have worked in this instance, but way back when I still used to get hard locks with my ati card the alt+sysrq+reisub sequence saved me quite a lot of data, especially the s part.

  4. #4
    Join Date
    Apr 2008
    Posts
    325

    Default

    *cough* back-ups *cough*

    Sorry, as a Hell-Desk worker, I can't find much sympathy with any techie loosing more than a days data.

  5. #5
    Join Date
    Mar 2009
    Posts
    141

    Default

    sucks about the lost tests though. i noticed data loss / corruption problems in the early 2.6.32-rcs, but haven't had a problem since. (of course most likely at the cost of performance.

    Perhaps ext3 will be a better option until btrfs is stabilized.

  6. #6
    Join Date
    May 2008
    Posts
    95

    Default

    Nice way (or not? heh) to prompt implementing remote export of PTS result data during testing. Great feature

  7. #7
    Join Date
    Feb 2010
    Posts
    11

    Default

    Actually, it may not be an actual EXT4 bug. I was doing some work a few days ago on a tmpfs (I'm also using .32 kernel) and the whole directory just disappeared, by itself, while I'm using EXT4 for a long time already, and I haven't lost a single file to it. And yes, I've done quiet a few hard reboots through this filesystem's lifetime. (Well, this one may be perhaps unrelated, I'm just saying that it may be a bug elsewhere.)

  8. #8
    Join Date
    Mar 2009
    Posts
    141

    Default

    Quote Originally Posted by RobbieAB View Post
    *cough* back-ups *cough*

    Sorry, as a Hell-Desk worker, I can't find much sympathy with any techie loosing more than a days data.
    Yeah any testing that involves likely and repeated crashing and hard restarts means backups and fscks are mandatory IMO. I'd do it over a network and just write the results directly over NFS or rsync or something.

    If I'm bisecting a panic-inducing kernel commit, or testing unstable overclock settings with mprime i always backup beforehand. Same would apply to testing a boatload of video cards likely to cause an X lockup, though you can sometimes ssh in and reboot 'gracefully' from those.

    BTW: that has to be a pain swapping out all those cards. Are they hotswappable or something, or you use the kernel soft reboots?

  9. #9
    Join Date
    Jul 2008
    Location
    Berlin, Germany
    Posts
    821

    Default

    Next time store test results remotely, eg. on NFS. That way a software or hardware failure on the test box will not cause loss of the test data.

  10. #10

    Default

    Quote Originally Posted by Smorg View Post
    BTW: that has to be a pain swapping out all those cards. Are they hotswappable or something, or you use the kernel soft reboots?
    Just been turning it off, swapping the card, cleanly powering the system back up.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •