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...
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.
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.)
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?