![]() | |||||||||||||
Messages in this thread |
On Wed, Jan 23, 2002 at 10:42:33PM +0100, Oliver Neukum wrote: > On Wednesday 23 January 2002 09:06, Samuel Maftoul wrote: > > On Tue, Jan 22, 2002 at 08:01:44PM +0100, Oliver Neukum wrote: > > > > When a second user comes and unmounts a disk, then the data are flushed > > > > (the old data) and he gets a fs corruption, because the data were not > > > > from his disk. > > > > > > No. The sbp2 driver should report a disk change. If such a thing happens, > > > > According to my log, sbp2 has an event, It does see the new disk as I > > can mount it ( something bizarre: The first disk I plug, the sbp2 driver > > tells me the vendor and model of the disk, but all other disk won't tell > > me anything until I realod sbp2 module ( I think reloading is ok but not > > tested > > Do you use some kind of hotplugging script ? yes, I use suse 7.2 with updated modutils and kernel to 2.4.17 ( from unofficial suse rpm produced by suse ) and I'm using suse7.3's hotplug with ieee1394.agent that I got through the hotplug cvs server maybe to chemical :) I think that anyway we should prevent this happens if it's possible. ( I didn't lost any data since I tested with some spare disk ). I can also put a umount in my ieee1394.agent, I thought about it and probably will do it. > > Regards > Oliver - 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 12:15 [W:0.226 / U:0.070 seconds] ©2003-2008 Jasper Spaans | |||||||||||||