| 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
| ||
|
Message-ID: <20060717150105.GB8276@merlin.emma.line.org> Date: Mon, 17 Jul 2006 17:01:05 +0200 From: Matthias Andree <matthias.andree@....de> To: Christian Trefzer <ctrefzer@....de> Cc: Xavier Roche <roche+kml2@...lead.com>, linux-kernel@...r.kernel.org Subject: Re: reiserFS? Christian Trefzer schrieb am 2006-07-16: > fsck on a faulty drive might cause even more damage - how do you know > that other areas of the device are OK? All drives I bought in the recent years shipped with ARRE and ARWE set. Any halfway decent fsck tool can just rewrite the b0rked sector and the drive transparently remaps a spare. If reiser4 crashes the kernel instead, it's not failure resilient and is certainly not ready for production. > I also oppose the ReiserFS-v3.x design philosophy regarding faulty > storage layer, but in any case where your _live_ data is valuable and > uptime counts, you _really_should_ use a RAID of some sort. ...and certainly a backup system that gives you FAST access to the data. RAID doesn't protect against accidents with rm(1) or, worse, wipe(1). -- Matthias Andree - 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