From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: Re: Re: BUG in kernel: Wrong Handling of USB =?UTF-8?Q?HDD=E2=80=99s?= in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type) Date: Wed, 05 Oct 2011 13:08:15 -0700 Message-ID: <1317845295.7238.15.camel@dabdike> References: <1317835442.7238.8.camel@dabdike> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Alan Stern , Douglas Gilbert , linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Christoph Hellwig To: Amit Sahrawat Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2011-10-06 at 01:21 +0530, Amit Sahrawat wrote: > > The best we could probably offer is an interface to turn on the WCE bit > > in software (technically, you can do this today > > in /scsi/class/scsi_disk//cache_type, it's just that it will try > > to commit the change as a MODE_SELECT which will presumably fail). > Thanks James, is this related with SCSI command MODE_SELECT? and this > is to be passed when there is some failure? > or simply doing an "echo " to > /scsi/class/scsi_disk//cache_type? can you please elaborate a > little You tell me since you have the device. What that echo does is that it does try to make the change permanent with a mode select ... that likely won't work and the cache change only takes if the revalidated disk says the write back has been enabled (which I really think it won't). So I think you need an additional software bit to flip for the case where the device lies. James