![]() | |||||||||||||
Messages in this thread |
> > Of course you get problems if a raw devices changes underneath a > > mounted filesystem, I would expect that. That is _NOT_ what we were > > talking about _AT ALL_. The point is that the device itself caches > > the state of the disc over an erase, so even if the device is > > unmounted before an erase, when it is re-mounted, the stale data is > > read from the device's own cache, which should have been invalidated > > by the erase. > > Is it realy a hardware issue? I originally thought so, but maybe I was wrong. Jens posted a patch to invalidate kernel buffers on an umount - if the problem persists with that patch, I still believe it is a hardware fault. > Oh, and it is very simple to shout on anyone "Just eject and reload, > there is no issue, everything pointless". Well, I never suggested that, and I don't think it's an acceptable solution, unless the problem is limited to a few broken drives. John. - 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/ | ||||||||||||
| Last update: 2005-03-22 13:00 [W:0.346 / U:0.080 seconds] ©2003-2008 Jasper Spaans | |||||||||||||