On Mon, 22 Jun 2015, James Bottomley wrote: > I'm not sure I entirely like this: we are back again treating data > corruption problems silently. > > However, I also believe treating a single flush failure as a critical > filesystem error is also wrong: The data's all there correctly; all it > does is introduce a potential window were the FS could get corrupted in > the unlikely event the system crashed. > > Obviously, for a disk with a writeback cache that can't do flush, that > window is much wider and the real solution should be to try to switch > the cache to write through. I agree. Doing the switch manually (by writing to the "cache_type" attribute file) works, but it's a nuisance to do this when you have a portable USB drive that gets moved among a bunch of machines. > How about something like this patch? It transforms FS FLUSH into a log > warning from an error but preserves the error on any other path. You'll > still get a fairly continuous dump of warnings for one of these devices, > though ... do they respond to mode selects turning off the writeback? I would be very surprised if any of those drives support MODE SELECT at all. Maybe your patch will be acceptable, though. We'll have to hear from Markus and Matt. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in
