| 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: Tue, 11 Mar 2008 15:31:17 +0100 From: Artur Skawina <art_k@...pl> To: Daniel Phillips <phillips@...nq.net> CC: Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org Subject: Re: [ANNOUNCE] Ramback: faster than a speeding bullet Artur Skawina wrote: > Now, if you add snapshots to the backing store it suddenly becomes much > more interesting -- you no longer need to put so much trust in all the > hw. Should the device fail for whatever reason then you just rollback to > the last good snapshot upon restart. No corrupted fs, no fsck; you lose > some newly written data (that you couldn't recover w/o a snapshot anyway), > but can trust the rest of it (assuming you trust the fs and storage hw, > but that's no different then w/o ramback). or you could keep two devices as backing store, use one and switch to the other when the fs is consistent. This could as simple as noticing zero dirty data in the ramdisk or, if something is constantly writing to it, reacting periodically to some barrier (needs cow/doublebuffering in order to not throttle the writer, but you already do this). Means ramdisk can be as large as 1/2 the stable storage and a bit more i/o (resyncing after switch to the other device), but gives you two copies of the data; one stable and one that can be used to recover newer data should you need to. artur -- 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