On 10/05/2017 10:12, Carlos Maiolino wrote:
Well, having a planned infra-structure is a way, and using UUIDs for mounting the filesystems are two good ways to avoid mistakes with multiple mounts. UUIDs are unique for each filesystem, so even if the device name changes between boots, you can still be sure to mount the correct filesystem on the correct system by using their UUIDs
Sure, but this does not protect, for example, from a cloned virtual machine which mount a remote iSCSI path and which is started without knowing that. When the cloned machine tries to mount the remote path, bad things can happen.
The most obvious protection is at the iSCSI level, but only the old IETD SCSI target daemon seem to provide such as feature by the virtue of the "MaxSessions" parameter (I have not tested it, anyway). Another protection at the iSCSI level is granted by SCSI reservation, which works quite well but are somewhat harder to setup.
Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx GPG public key ID: FF5F32A8 -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
