| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 13 Dec 2006 17:37:48 +0900 From: Tejun Heo <htejun@...il.com> To: Andrew Robinson <andrew.rw.robinson@...il.com> CC: linux-kernel@...r.kernel.org Subject: Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means) Andrew Robinson wrote: > When I said hibernate, I did mention it was to disk, not to ram. I > woke my computer up from work remotely using wakeonlan. When the > computer was responsive, I started getting I/O errors and when I saw > my kernel log I saw file corruption problems with my "/dev/sda2" > device (which is my root file system and is one of two, the other is > the swap partition) sata_nv is just now receiving suspend/resume support in devel tree. 2.6.19 sata_nv doesn't have it and STD might have worked but I wouldn't be surprised if it doesn't work from time to time or gets broken due to unrelated changes in kernel. So, IO errors after STD are bad but kind of expected. I dunno what went wrong with your fs after such IO errors. Destroyed fs after some IO errors is pretty extreme tho. So, my 5 cents is... don't do hibernation till 2.6.20 is out. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists