linux-kernel - EnhanceIO(TM) caching driver features [2/3]

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <A44CB407BBB85C498149811C52498A450872ED@MYMBX3.stec-inc.ad>
Date:	Fri, 24 May 2013 09:19:51 +0000
From:	OS Engineering <osengineering@...c-inc.com>
To:	Jens Axboe <axboe@...nel.dk>, LKML <linux-kernel@...r.kernel.org>
CC:	Padmini Balasubramaniyan <padminib@...c-inc.com>,
	Amit Phansalkar <aphansalkar@...c-inc.com>
Subject: EnhanceIO(TM) caching driver features [2/3]

Hi,

Here is a description of error handling as stated in a previous email.

When an IO is submitted to a cache and an OS crash or an abrupt power failure occurs before the cahe completes the IO and returns success status  - The end result after a reboot is that some of the blocks contained in the IO range could be persistent. The rest may not be persistent. In no case will garbage data be found in the IO range. This is in-line with the behavior of RAID systems or volume management software packages. Enterprise class filesystems and databases are capable of handling this situation correctly.

When an SSD fails, dirty data is lost. This may cause an entire filesystem or a database to go corrupt. Administrators however are able to limit exposure to dirty data by using EnhanceIO(TM) automatic clean-up tunables and a forced clean-up.

Attached spreadsheet gives an exhaustive list of the error conditions EnhanceIO(TM) driver handles.
-Amit

Download attachment "eioerrorhandling.ods" of type "application/oleobject" (7688 bytes)