DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=MOuyl0bTeYZogAKZX+hnQHvj9tXn2Pn1FawdlIXtIxTxdahyPQtjWH9gkU5lKkDRQkCQqCpGxVtkLRcsATCE2f9jJVgZVrj6dh4yi+fzjGFLu7VGfuO0iJVGPUmh939Yfjxn61NQ6fseL7ZK5cLuSkPllJwB5gSTlpbRpsUq6i8=  ;
Message-ID: <20051229162935.67301.qmail@web34106.mail.mud.yahoo.com>
Date: Thu, 29 Dec 2005 08:29:35 -0800 (PST)
From: Kenny Simpson <theonetruekenny@yahoo.com>
Subject: RAID controller safety
To: linux kernel <linux-kernel@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1147
Lines: 27

Hello,
  I am trying to determine which drivers and what hardware can be used to give reliable fsync
behavior.  I see many drivers with FIXME or TODO comments which make me nervous.
  I see the sd driver supports the direct SYNCHRONIZE_CACHE, but I'me having a hard time tracing
through how this translates to raid controllers and their drivers.
  Specificly, I am looking at the Adaptec RAID controllers and their i2o drivers.  I am told the
kernel's i2o driver lacks a strong guarantee on fsync, and so far am unable to determine if the
dpt_i2o driver also falls short in this reguard.

  I don't mean to start a 'drives lie - disable all caching, buy FC drives' flame war.  I know
drives can lie, but I'd like to know if the drivers are lying too.

thanks,
-Kenny


__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/