Hi Beyers, I am currently using G4L to restore the partition which has the OS files. The driver code is on a NFS partition. Right now, it makes me about 7 minutes to "restore" the machine.
I might try the USB idea if this keeps happening very frequently. Roman Beyers Cronje wrote: > Hi Roman, > > I've done some work in the past on the e1000 driver but never had major > issues with file system damage as a result of crashes. So this is just > off the top of my head, I'm wondering if booting/using a USB > flash memory stick for testing might save time, at least it should be a > lot quicker to rebuild if things go wrong. > > Beyers > > On Tue, Aug 19, 2008 at 12:25 AM, Roman Chertov <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hello, > I am not sure how many people follow e1000, list but they have made > a split between e1000 to e1000 and e1000e. There is also an igb driver > which is pretty similar to e1000e code. We got 6 quad-port Intel which > require the use of the igb driver. I am currently trying to port the > igb driver to Click, and I am facing a few issues. The main issue is > when the machine crashes, it has a tendency to damage the file system, > so that even fsck cannot fix all the issues. I am curious if anybody > had issues with crashes causing fs corruption and how the minimized the > effects. > > Roman > _______________________________________________ > click mailing list > [email protected] <mailto:[email protected]> > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
