On Tue, 2006-06-13 at 10:42 -0500, Michael Reed wrote: > Mounted file systems have no clue either. Even with no activity on the > fs, if the target stays missing beyond the device loss timeout and then > returns, the file system cannot be accessed without intervention. > > When the target does return, the file system has to be unmounted and > remounted on a new "sd" device. This is even if there was no activity > on the file system while its target was absent, i.e., it wouldn't otherwise > require an unmount/remount. But lets examine the options: If you leave an uncontactable target hanging around, the SCSI error handler will activate anyway when the command timeout passes (currently 30s) and the device will be offlined. Bringing it back online will require user intervention and likely necessitate an unmount and a remount to repair the filesystem anyway. Even if you go further and hold off the error handler, what this will do is slowly hang the system since anything that touches an inode on the blocked target will be put into D wait. I really think pro-actively removing the target is better than either of the other two options. The device loss timer represents an acceptable compromise between the need to keep the target across short disconnect/reconnect events and the need to keep the system functioning. James - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
