In <20000204021524.8BE6B3D8CF@degger.muc.suse.de> Daniel.Egger@suse.de (Daniel.Egger@suse.de) wrote:
> Hi developers,
> I just noticed that the sysrq comibation sysrq-u isn't
> working properly here since at least 2.3.20 (I don't have
> older kernels to test) up to 2.3.42. Even with a vital system
> it won't unmount any of my partitions so a check is necessary
> on the next startup...
> 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. 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)...
-
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/
This archive was generated by hypermail 2b29 : Mon Feb 07 2000 - 21:00:10 EST