On Thursday 01 March 2007 17:35, Daniel O'Connor wrote: > > in /rescue and use './sysctl' (and other commands in rescue). I think > > you will still be able to execute static executables in the current > > directory vis a relative path even if the FS is deadlocked. (As long > > as your shell isn't trying to write command history to a file). > > hmm.. I will see if I can maintain an open shell.. Going to be a PITA given > the length of time between failures.
I just logged in OK as it's done it again. Unfortunately it has a version of ATARAID which doesn't support crash dumps. Argh. I was incrementally dumping sysctl trees and when I got to vm it hung.. eureka:~>sysctl vm load: 0.07 cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k load: 0.07 cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k load: 0.07 cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k load: 0.05 cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k I tried to reboot in another window but.. eureka:~>reboot load: 0.06 cmd: csh 71159 [allproc] 0.03u 0.00s 0% 4652k I am pondering an update to at least the ATA sub system so I can generate a crash dump though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pgpl3jJEVgXJd.pgp
Description: PGP signature
