On Wed, 2011-10-05 at 10:17 -0400, Alan Stern wrote: > On Wed, 5 Oct 2011, Amit Sahrawat wrote: > > > Hi, > > > > In order to verify the SYNC_CACHE command being passed. > > First I checked on the USB HDD(Seagate - Free Agent) which is gettind > > properly identified on linux. I performed - copy of a file and then > > did 'Safely Remove Hardware" - this resulted in SYNC_CACHE command > > being passed - All logs are captured for this. > > > > Then, for the same Hard Disk - I checked for the behaviour on Windows. > > There is no SYNC CACHE command being passed in this case. > > > > Again, checked for a different hard disk(Seagate) - which has cache > > but not shown in Linux. In that case also, there is no SYNC CACHE > > command. > > > > Please find the logs for the '3' cases attached. > > This is a little disappointing. If Windows doesn't use the SYNCHRONIZE > CACHE command, it's quite likely that some USB drives will crash when > they receive it. > > This strongly suggests that we should not change the current code. I agree ... it means they go by the SCSI mode pages too, so we'll be no worse than they are. Plus we don't risk upsetting the rest of the USB device universe. James -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
