Messages in this thread |  | | | Date | Fri, 4 Feb 2000 16:41:29 +0300 (MSK) | | From | Khimenko Victor <> | | Subject | Re: Sysrq not working properly... |
| |
On Fri, 4 Feb 2000 Daniel.Egger@suse.de wrote:
> On 4 Feb, Khimenko Victor wrote: > > >> Ideas? > > > This is how SysRq-U is SUPPOSED to work :-) It even says so: > > -- cut -- > > SysRq: Emergency Remount R/O > > -- cut -- > > > System is STILL mounted and so SHOULD BE changed after reboot. > > Yes, of course.... > I should have said: it isn't mounted r/o.... > Huh ??? You CAN save to drive after SysRq-U ???
> > It's > > good idea: SysRq is EMERGENCY tool after all and it's allways good > > idea to check everything after emergency :-) SysRq-U will prevent > > FUTHER filesystem corruption but if filesystem was ALREADY corrupted > > when you pressed SysRq-U it can not be fixed without fsck (and you are > > NOT supposed to use SysRq-U when there are no possible curruption: > > just reboot as usual)... > > Let's say (despite of my writings): it doesn't work as supposed... :) > It won't remount the drives... > ???? It does so here: I can not write anything on disk after SysRq-U. Of course disk will be fscked after reboot.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |