From 25025f3a5a0781c3b4c8717333d7ccc5e7c135b5 Mon Sep 17 00:00:00 2001 From: Vladislav Bolkhovitin Date: Tue, 17 Aug 2010 19:13:00 +0000 Subject: [PATCH] Update docs about kernel versions where BLOCKIO problem (http://lkml.org/lkml/2010/7/28/315) was fixed. Big thanks to Bryan Mesich ! git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@1955 d57e44dd-8a1f-0410-8b47-8ef2f437770f --- scst/README | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/scst/README b/scst/README index 5c7380d4a..da937adfa 100644 --- a/scst/README +++ b/scst/README @@ -1444,10 +1444,11 @@ IMPORTANT: Since data in BLOCKIO and FILEIO modes are not consistent between simultaneously, you will almost instantly corrupt your data on that device. -IMPORTANT: Kernels starting from 2.6.32 have a problem, which prevents BLOCKIO -========= from working with RAID5/DM. See http://lkml.org/lkml/2010/7/28/315. - Hopefully, it will be fixed soon. Meanwhile, it is recommended to use - kernels below 2.6.32 for BLOCKIO on RAID5/DM devices. +IMPORTANT: Some kernels starting from 2.6.32 have a problem, which prevents +========= prevents BLOCKIO from working correctly with RAID5/DM. See + http://lkml.org/lkml/2010/7/28/315. That problem was fixed in + 2.6.32.19, 2.6.34.4, 2.6.35.2 and 2.6.36-rc1. It is strongly + recommended to not use affected kernels with BLOCKIO. IMPORTANT: In SCST 1.x BLOCKIO worked by default in NV_CACHE mode, when ========= each device reported to remote initiators as having write through