On 05/12/2010 12:56 PM, Ian MacDonald wrote:
We have the following new setup; Karmic with root on iSCSI (local boot
partition since the NIC doesn't support native iSCSI). This was
surprisingly easy following vanilla iSCSI Ubuntu installer and a few
post-install tweaks from /usr/share/doc/open-iscsi/README.Debian
Here's the logical setup:
UbuntuKarmicServer Initiator (local /boot) Single GigE -> iSCSI GigE ->
Debian Lenny Target (Dual GigE ChannelBonding w/ balance-alb, 2TB LVM2
over LUKs+RAID1)
The IET target also serves some VMFS3 volumes that are shared amongst a
bunch of ESX 3.5 servers without issue. (We are somewhat happy with the
VMFS3 from IET alb-ChannelBonded overtop LUKS+RAID).
We had some issues with the initiator loosing connections with the
target in this new Karmic rootfs on iSCSI setup. The problem is that
after some time the filesystem switches to a read-only mount following
I/O errors after some activity on the initiator.
Do you have the log messages for that? Did you see any ping/nop timeout
messages (for root on iscsi set node.conn[0].timeo.noop_out_interval and
node.conn[0].timeo.noop_out_timeout to 0).
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
