Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
iscsi [2009/05/25 00:35] 127.0.0.1 external edit |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== the definitive guide to Debian Etch open-iscsi ====== | ||
- | |||
- | This time we are going to use th backports repository and the Etcn’n' | ||
- | |||
- | So, first of all add the backports repository: | ||
- | |||
- | echo “deb http:// | ||
- | |||
- | and do some basic stuff: | ||
- | |||
- | # aptitude update | ||
- | # aptitude install debian-backports-keyring | ||
- | # aptitude update | ||
- | |||
- | Now, let’s install the newer 2.6.24 kernel from the Debian Etch’n' | ||
- | |||
- | |||
- | # aptitude install linux-image-2.6-amd64-etchnhalf # remove amd64 if you’re on x86_32 | ||
- | |||
- | now here, if you are a Broadcom NeteXtreme 2 user (lsmod|grep bnx2), be careful and remember to install these NEW package before rebooting, or you will have an unpleasant surprise | ||
- | |||
- | |||
- | # aptitude install firmware-bnx2 | ||
- | |||
- | This is due to a change in newer Linux versions | ||
- | |||
- | Then reboot, cross your fingers and then install the newer open-iscsi package: | ||
- | |||
- | # aptitude install -t etch-backports open-iscsi | ||
- | |||
- | Everything should be ok and this time you should have all the config files in the right place, a proper script to mount/ | ||
- | Anyway, I still prefer the old-school config file, so usually I replace the Debian stock one with something like this: | ||
- | |||
- | |||
- | node.active_cnx = 1 | ||
- | # | ||
- | node.startup = automatic | ||
- | # | ||
- | # | ||
- | # | ||
- | node.session.timeo.recovery_timeout = 15 | ||
- | node.session.err_timeo.abort_timeout = 10 | ||
- | node.session.err_timeo.reset_timeout = 30 | ||
- | node.session.iscsi.InitialR2T = No | ||
- | node.session.iscsi.ImmediateData = Yes | ||
- | node.session.iscsi.FirstBurstLength = 262144 | ||
- | node.session.iscsi.MaxBurstLength = 16776192 | ||
- | node.session.iscsi.DefaultTime2Wait = 0 | ||
- | node.session.iscsi.DefaultTime2Retain = 0 | ||
- | node.session.iscsi.MaxConnections = 0 | ||
- | node.conn[0].iscsi.HeaderDigest = None | ||
- | node.conn[0].iscsi.DataDigest = None | ||
- | node.conn[0].iscsi.MaxRecvDataSegmentLength = 65536 | ||
- | |||
- | I have highlighted one line because that parameter is used to choose the timeout after which an iSCSI device is considered dead, and thus that path discarded (we’ll talk about paths later). | ||
- | |||
- | So, time to discover new devices now: | ||
- | |||
- | # / | ||
- | # iscsiadm -m discovery -t sendtargets -p $SAN_IP_ADDRESS | ||
- | # / | ||
- | |||
- | check out your dmesg output and look for new /dev/sdX devices. | ||
- | Some partitioning and formatting later, you can edit your fstab with something like this | ||
- | |||
- | |||
- | / | ||
- | |||
- | and you should be done! |