CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 1 of 13

About Forum Howtos & FAQs Low graphics Shell Scripts RSS/Feed

Cursos LINUX LPI - GREEN Modo texto/terminal, Debian, RedHat Sistemas, Redes, Samba, Firewall www.green.com.br Unified Storage Server 32TB SATA/SAS Enterprise Scale 10G NAS/iSCSI Solution with Condre www.chelsio.com

nixcraft - insight into linux admin work

CentOS / Red Hat Linux: Install and manage iSCSI Volume

by Vivek Gite on October 30, 2007 45 comments Internet SCSI (iSCSI) is a network protocol s that allows you to use of the SCSI protocol over TCP/IP networks. It is good alternative to Fibre Channel-based SANs. You can easily manage, mount and format iSCSI Volume under Linux. It allows access to SAN storage over Ethernet.

Open-iSCSI Project
Open-iSCSI project is a high-performance, transport independent, multi-platform implementation of iSCSI. Open-iSCSI is partitioned into user and kernel parts. Instructions are tested on: [a] RHEL 5 [b] CentOS 5 [c] Fedora 7 [d] Debian / Ubuntu Linux

Install Required Package

iscsi-initiator-utils RPM package - The iscsi package provides the server daemon for the iSCSI protocol, as well as the utility programs used to manage it. iSCSI is a protocol for distributed disk access using SCSI commands sent over Internet Protocol networks. This package is available under Redhat Enterprise Linux / CentOS / Fedora Linux and can be installed using yum command:
# yum install iscsi-initiator-utils

A note about Debian / Ubuntu Linux

If you are using Debian / Ubuntu Linux install open-iscsi package, enter:
$ sudo apt-get install open-iscsi

iSCSI Configuration
There are three steps needed to set up a system to use iSCSI storage: 1. 2. 3. 4. iSCSI startup using the init script or manual startup. You need to edit and configure iSCSI via /etc/iscsi/iscsid.conf file Discover targets. Automate target logins for future system reboots. You also need to obtain iSCSI username, password and storage server IP address (target host)

Step # 1: Configure iSCSI

Open /etc/iscsi/iscsid.conf with vi text editor:
# vi /etc/iscsi/iscsid.conf

Setup username and password:

node.session.auth.username = My_ISCSI_USR_NAME node.session.auth.password = MyPassword discovery.sendtargets.auth.username = My_ISCSI_USR_NAME

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 2 of 13

discovery.sendtargets.auth.password = MyPassword

Where,

node.session.* is used to set a CHAP username and password for initiator authentication by the target(s). discovery.sendtargets.* is used to set a discovery session CHAP username and password for the initiator authentication by the target(s)

You may also need to tweak and set other options. Refer to man page for more information. Now start the iscsi service:
# /etc/init.d/iscsi start

Step # 2: Discover targets

Now use iscsiadm command, which is a command-line tool allowing discovery and login to iSCSI targets, as well as access and management of the open-iscsi database. If your storage server IP address is 192.168.1.5, enter:
# iscsiadm -m discovery -t sendtargets -p 192.168.1.5 # /etc/init.d/iscsi restart

Now there should be a block device under /dev directory. To obtain new device name, type:
# fdisk -l

or
# tail -f /var/log/messages

Output:
Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct 10 10 10 10 10 10 10 10 10 10 10 10 10 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 12:42:20 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 ora9is2 kernel: kernel: kernel: kernel: kernel: kernel: kernel: kernel: kernel: kernel: kernel: kernel: iscsid: Vendor: EQLOGIC Model: 100E-00 Rev: 3.2 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdd: 41963520 512-byte hdwr sectors (21485 MB) sdd: Write Protect is off SCSI device sdd: drive cache: write through SCSI device sdd: 41963520 512-byte hdwr sectors (21485 MB) sdd: Write Protect is off SCSI device sdd: drive cache: write through sdd: unknown partition table sd 3:0:0:0: Attached scsi disk sdd sd 3:0:0:0: Attached scsi generic sg3 type 0 rtc: lost some interrupts at 2048Hz. connection0:0 is operational now

/dev/sdd is my new block device.

Step # 3: Format and Mount iSCSI Volume

You can now partition and create a filesystem on the target using usual fdisk and mkfs.ext3 commands:
# fdisk /dev/sdd # mke2fs -j -m 0 -O dir_index /dev/sdd1

OR
# mkfs.ext3 /dev/sdd1

Tip: If your volume is large size like 1TB, run mkfs.ext3 in background using nohup:
# nohup mkfs.ext3 /dev/sdd1 &

Mount new partition:

# mkdir /mnt/iscsi # mount /dev/sdd1 /mnt/iscsi

Step #4: Mount iSCSI drive automatically at boot time

First make sure iscsi service turned on at boot time:
# chkconfig iscsi on

Open /etc/fstab file and append config directive:

/dev/sdd1 /mnt/iscsi ext3 _netdev 0 0

Save and close the file.

Further readings:

Official Open iSCSI documentation Read iscsiadm and related man pages

This blog post is 1 of 4 in the "Linux iSCSI Initiator (SCSI protocol over TCP/IP networks) Tutorial" series. Keep reading the rest of the series:

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 3 of 13

Table of Contents: 1. 2. 3. 4. CentOS / Red Hat Linux: Install and manage iSCSI Volume CentOS 4 / Redhat Enterprise Linux 4 iSCSI Installation and Configuration ( iscsi initiators ) How To: Windows Server / XP / 2000 / 2003 ISCSI Initiator Configuration Linux tgtadm: Setup iSCSI Target ( SAN )

{ 45 comments read them below or add one } 1 srinath January 29, 2008 IT is very good and keepit up Reply 2 anees June 4, 2008 I am trying according to your document and run these steps and found these errors. any good solution? # /etc/init.d/iscsi start Checking iscsi [ OK ] Loading iscsi driver: FATAL: Module iscsi_sfnet not found. [FAILED] #/sbin/iscsi-ls -l iSCSI driver is not loaded Reply 3 Enrico /slash/ June 5, 2008 to reach iscsi_sfnet you try to start first iscsid bye Reply 4 devnull August 8, 2008 hiya, well done, thanks. Works perfect with Scientific Linux 5 (32 and 64 bit) and MSA 2012i, I just used xfs for my instalation. cheers/zdrowka! Reply 5 Paras Pradhan August 13, 2008 When I run isciadmin i get the following error. Help ! 10.42.40.198 is the ip address of the server running iscsi and iscsid. [root@swt60p iscsi]# iscsiadm -m discovery -t sendtargets -p 10.42.40.198 iscsiadm: cannot make connection to 10.42.40.198:3260 (111) iscsiadm: connection to discovery address 10.42.40.198 failed iscsiadm: cannot make connection to 10.42.40.198:3260 (111) iscsiadm: connection to discovery address 10.42.40.198 failed iscsiadm: cannot make connection to 10.42.40.198:3260 (111) iscsiadm: connection to discovery address 10.42.40.198 failed Paras. Reply

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 4 of 13

6 not-a-guru July 1, 2010 I had the same issue. Turns out SELinux is preventing access. I dont really require that on this box, so I set it to permissive. Reply 7 Rob Dyke October 6, 2008 Perfect solution. Got my Fedora 9 workstation talking to my openfiler server in no time at all. Many thanks. Reply 8 Amr Hamdy December 15, 2008 Thanks, It works so nice on RHEL 5.2 But I think its better to do; mkfs.ext3 /dev/sdd1 &>somelog & disown Than; nohup mkfs.ext3 /dev/sdd1 & Reply 9 Alan February 13, 2009 How do you tell which targets are associated with which device? The discovery process found both iscsi targets on the zfs server Im using and want to make sure Im making a new filesystem on the right one Reply 10 Robert February 24, 2009 I got the same error as Paras Pradhan. Any solution to that? Reply 11 Vivek Gite February 24, 2009 Robert, Make sure firewall is not blocking connection. Reply 12 Bjoern March 4, 2009 Robert and Paras: Is a network ACL installed at the ISCSI target system? Is the connection working proper? If your useing for example openfiler as your target system check the status of the connection by useing: netcat -an | grep 3260 you will see the remote system is trying to connect to your filer. Or you can add a hig debug-level to you iscsiadm command: iscsiadm -d 9 -m discovery -t sendtargets -p 192.168.1.5 Bjoern Reply 13 sreeram March 13, 2009 simple and fast.. thanks a lot Reply 14 John doyle April 10, 2009

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 5 of 13

You can also label the devices this way if they change or are renamed etc on reboot you will be mounting by label and not device name. e2label on the /dev/vg/lv eg e2label e2label /dev/vg4/lv4 /home4 The in etc/fstab LABEL=/home4 /home4 ext3 _netdev 0 0 Reply 15 Martin Corona May 19, 2009 Is there a howto to get this installed at OS install time? Interested in seeing if it could be done Reply 16 Shaun Forsyth June 8, 2009 Great Guide, wanted to say thanks. This saved me god knows how many hours of research. Also wanted to point out a great unti
lshw

Which can be install using

yum isntall lshw

this makes it about 100 times easyer to find the new device name Reply 17 Ugo Bellavance July 16, 2009 Little note: netfs service must be on in chkconfig in red-hat, else the mountpoints are not mounted. Reply 18 el nugraha July 17, 2009 im not sure Reply 19 Vivek Gite July 17, 2009 about what? Reply 20 jap July 31, 2009 Thanks for the guide, Maybe stupid question, but i dont undertand where i can find or set initiator name? Or i dont need it? What should i set on storage site? Thank you, Jap Reply 21 jap July 31, 2009 sorry, it is there :-] /etc/iscsi/initiatorname.iscsi stujap Reply

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 6 of 13

22 Skau August 28, 2009 Robert and Paras, you probably get this error because iscsi and iscsid is not started on your client nodes, reboot those (or use service iscsi start; service iscsid start) and you will be able to discover your devices. I had the same error, chkconfig showed me that they were on but a reboot of the clients solved my problems Reply 23 flo December 10, 2009 Good job !!! But when i check my fs on my das this is the result : real 0m24.005s user 0m0.000s sys 0m0.000s ########## 0+10 enregistrements lus. 0+10 enregistrements crits. real 0m0.001s user 0m0.000s sys 0m0.001s ########## 0+10 enregistrements lus. 0+10 enregistrements crits. real 0m0.001s user 0m0.000s sys 0m0.001s ########## 0+9 enregistrements lus. 0+9 enregistrements crits. real 0m0.535s user 0m0.000s sys 0m0.001s I do not know why sometime the response time is very long Thx Reply 24 VPS Lime LLC January 28, 2010 Great article and well written! Very easy to follow and use. Reply 25 jay February 4, 2010 I was able to mount and use the device but after stopping the iscsi service and unmounting the device, I wasnt able to mount it again. Reply 26 jay February 4, 2010 additional: This is how it looks like when I issue fdisk -l Disk /dev/sdn: 143.0 GB, 143034155008 bytes

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 7 of 13

255 heads, 63 sectors/track, 17389 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdn1 1 17389 139677111 83 Linux Disk /dev/sdn1: 143.0 GB, 143029361664 bytes 255 heads, 63 sectors/track, 17388 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdn1 doesnt contain a valid partition table Disk /dev/sdo: 968.0 GB, 968016265216 bytes 255 heads, 63 sectors/track, 117687 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdo1 1 117687 945320796 83 Linux The one with the problem is /dev/sdo1. Im expecting it to be looked like sdn1. (sdo1 and sdn1 are partition of sdo and sdn device). I am using rhel 4 AS, 2.6.9-42ELsmp, iscsitarget-kernel-smp-0.4.12-6_2.6.9_42.EL iscsitarget-0.4.12-6 iscsi-initiator-utils-4.0.3.0-4 Regards, Jay A Reply 27 Chris February 11, 2010 Im having a problem My iscsi volume is 5GB on a RAID5 array. I could find no way to sucessfully partition this so I simply formatted the whole volume. When I do fdisk -l I get Disk /dev/sdb doesnt contain a valid partition table but this doesnt seem to be a major issue. When I start up the server, iscsi finds the target, /dev/sdb is created and then mounted via fstab. I can connect to the volume fine. If I restart iscsi for any reason, I lose the disk it disappears and is re-detected as /dev/sdc instead. I am also unable to unmount it without getting device is busy. Any ideas? Reply 28 Eric February 17, 2010 Hi I have the same problem as Paras Pradhan except my error code is: [root@cent ~]# iscsiadm -m discovery -t sendtargets -p 192.168.2.0 iscsiadm: cannot make connection to 192.168.2.0:3260 (101) iscsiadm: connection to discovery address 192.168.2.0 failed iscsiadm: cannot make connection to 192.168.2.0:3260 (101) iscsiadm: connection to discovery address 192.168.2.0 failed iscsiadm: cannot make connection to 192.168.2.0:3260 (101) iscsiadm: connection to discovery address 192.168.2.0 failed iscsiadm: cannot make connection to 192.168.2.0:3260 (101) iscsiadm: connection to discovery address 192.168.2.0 failed iscsiadm: cannot make connection to 192.168.2.0:3260 (101) iscsiadm: connection to discovery address 192.168.2.0 failed

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 8 of 13

iscsiadm: connection login retries (reopen_max) 5 exceeded I tried service iscsi restart; service iscsid restart and tried the command again but I still am not able to connect to it. Did I configure the vi /etc/iscsi/iscsid.conf correctly? # to CHAP. The default is None. node.session.auth.authmethod = CHAP # To set a CHAP username and password for initiator # authentication by the target(s), uncomment the following lines: node.session.auth.username = [our username goes here] node.session.auth.password = [our password goes here] # To set a CHAP username and password for target(s) # authentication by the initiator, uncomment the following lines: node.session.auth.username_in = [our username goes here] node.session.auth.password_in = [our password goes here] # To enable CHAP authentication for a discovery session to the target # set discovery.sendtargets.auth.authmethod to CHAP. The default is None. #discovery.sendtargets.auth.authmethod = CHAP # To set a discovery session CHAP username and password for the initiator # authentication by the target(s), uncomment the following lines: #discovery.sendtargets.auth.username = username #discovery.sendtargets.auth.password = password # To set a discovery session CHAP username and password for target(s) # authentication by the initiator, uncomment the following lines: #discovery.sendtargets.auth.username_in = username #discovery.sendtargets.auth.password_in = password Thanks, Eric Averitt Reply 29 majk February 19, 2010 hi, i have the same problems like chris and Jay. Anyone has a solution? Regards Majk Reply 30 Vivek Gite February 19, 2010 majk / chris and jay, you are following guide for RHEL / CentOS 5. There is a link at the bottom of the article which is for RHEL/CentOS 4. HTH Reply 31 Chris February 19, 2010 Im using centos 5 It works perfectly 99% of the time but my problem is if I lose connection to the target for any reason, if iscsi is restarted, or if the volume is unmounted, the only way to get it to work properly again is to reboot the server. It doesnt seem as reliable as people say. Reply 32 jay February 22, 2010

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 9 of 13

Hi, I did not use partition anymore. I was able to mount and umount the iscsi and use it for 19 days now w/o a problem. Chris:, Do you really need to restart the server? How about just restarting the iscsi sevices? Rgds, Jay A Reply 33 Chris February 22, 2010 Hi Jay, As I mentioned in my earlier message, if I restart the iscsi service, the device becomes detected as sdc instead of sdb. Reply 34 Chris February 26, 2010 Ive decided to reduce the size of my iscsi targets, change the block size back to 512 and try again. I wasnt happy with being unable to partition the 5TB volume. I now have four iscsi targets to connect to, each around 1.3 TB. I want to ensure that these are connected the same way each time. I see no way in the config file to specify each target it seems to just auto discover. I dont want to auto discover. How can I specify the targets target name or iqn so that it always gets the same device name each time? The device name appears to be dynamically created on boot. What happens if it dicovers one device before another next time it boots? will it apply a different device name to the one before. I need to be able to specify this somehow. On the storage device config I can choose a target name and a CHAP username and password for each target each has their own iqn. I cant work out how to use CHAP authentication to conenct to four seperate targets. The config file only has an option to specify one username and password and there is no way of specifying the target. It doesnt make sense. I need to do the following 1. When the iscsi service is started, connect to four target devices using a different CHAPS username and password for each one. 2. Ensure that each device always has the same device name. If somoene could point me in the direction of a tutorial or docuement that shows specifically how to do this I would be very grateful. Thank you for your time. Reply 35 Chris February 28, 2010 How to make sure multiple targets always connect correctly Ive been looking at this for a couple of days and here are my findings.The above tutorial is great if you have only one target iSCSI volume. If you have multiple targets to connect to, there are a few things to consider. 1. When the targets are discovered, they wont be discovered in the same order you set them up on your storage server. 2. When you reboot the server or restart iSCSI, the targets will not always be assigned the same device names each time. 3. The order in which the targets are discovered by the iscsi service, is not neccessarily the order in which they are assigned device names so dont assume that each discovered node will be assigned /dev/sdb, /dev/sdc, /dev/sdd in turn they wont. So, it is extremely difficult (or impossible) to identify which target volume applies to what device name If you enable all your targets at the same time and discover them all at once. To overcome the above issues you simply need to set up, discover and configure each target volume one at a time then label the partitions and mount them using the label, instead of the device name. Here is how I did it 1. Create the first iSCSI target on your storage server. On some devices you will be able create all of them and set all but one to disabled for now. Im using a Thecus N8800. I have 12TB split into 8 iSCSI volumes. The important thing

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 10 of 13

at this step is to ensure that you only have your first iSCSI target enabled for discovery. 2. Follow the instructions in Step # 1: Configure iSCSI and Step # 2: Discover targets in the main tutorial above. Side note: I am yet to understand the node.session. and discovery.sendtargets. authentication options. On my storage device I have the option to create a CHAP username and password for each target but I dont know how this equates to either node.session. or discovery.sendtargets. or how to set this up in the config file for multiple targets with different usernames. So I currently have the CHAP authentication disabled completely. 3. From fdisk-l note the device name and give it a label
# e2label /dev/sdb1 iscsi001

4. Enable the second iSCSI target on your storage device and run the first step from Step # 2: Discover targets in the above tutorial
# iscsiadm -m discovery -t sendtargets -p 192.168.x.x # /etc/init.d/iscsi restart

5. When you run fdisk-l now, you will see your first target volume has been renamed to /dev/sdc1 and your new one has taken its place as /dev/sdb1. Complete your partioning and formatting of the new volume and then label it
# e2label /dev/sdb1 iscsi002

Of course, the labels will remain, no matter what the device name. So if you read the label
# e2label /dev/sdc1

the response will be iscsi001

# e2label /dev/sdb1

iscsi002 Repeat all the above steps for all your targets so that each one has a device label. Now mount the target volumes using the label instead of the device name
mkdir mkdir mkdir mkdir /mnt/iscsi001; /mnt/iscsi002; /mnt/iscsi003; /mnt/iscsi004;

In /etc/fstab
LABEL=iscsi001 LABEL=iscsi002 LABEL=iscsi003 LABEL=iscsi004 /mnt/iscsi001 /mnt/iscsi002 /mnt/iscsi003 /mnt/iscsi004 ext3 ext3 ext3 ext3 _netdev _netdev _netdev _netdev 0 0 0 0 0 0 0 0

From the command line

mount -L iscsi001 /mnt/iscsi001

Hope this helps anyone else who has the same dilemma :-) Reply 36 Tom July 21, 2010 Thanks for that. The system was changing the order upon restart. Labels work.

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 11 of 13

Reply 37 miahac April 22, 2011 I hope this will solve my problem. When I reboot, the target changes device names so I have to change my mount point i.e. Right now my volume is on /dev/sdk1 but before rebooting it was on /dev/sdn1 so it does not remount from my fstab, and therefore I had to login and mount it (and I change my fstab, but that is really futile). I am concerned that this will not work because you are linking the label to the device name itself unless it is actually adding the label to the volume I have never used e2fs label before. I guess I will find out when I reboot in a year or two. Reply 38 Jane April 13, 2010 I was successful in creating iscsi even used e2label to label the /dev/sdc1. But everytime I reboot the machine it does not mount. I have to logon and ran mount -a Please advise on how to make it mount after every reboot. Seem like it could not find /dev/sdc1 during boot up. Thanks! Reply 39 Andy July 13, 2010 Thanks. helped me get iscsi setup very quickly. to get the ids of the targets: udevinfo -q symlink -n /dev/sd?? I tried adding them in fstab but that stopped the system from booting. I guess it was due to iscsi not being loaded at that point. For my scenario it was perfectly acceptable for me to put the mounts into /etc/rc.local Reply 40 Michael August 27, 2010 Please Help! After doing the Step # 2: Discover targets without errors (I think so?). When is use the fdisk -l command i cant see the new drive from iscsi target. What should i do next? Im Using CentOS 5.3 Server Reply 41 Danix Defcon 5 September 4, 2011 Theres a step missing from these instructions, at least for my case. I actually have to login to the targets before they appear, so you need to do: iscsiadm -m node -T (target) -p (portal) login For example: iscsiadm -m node -T iqn.2011-09.org.foobar.san:my.iscsi.target.01 -p 192.168.1.66 login Reply 42 eduardbc January 13, 2011

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 12 of 13

Nice article and nice comments! But I still have the doubt if its possible to connect to different targets with different passwords! Thanks! Reply 43 Mark February 10, 2011 Is it possible to get the target back to read-write mode so I can umount the target without rebooting? iSCSI shows that the connection is in a running state, but the device is marked read-only so remount doesnt help. Reply 44 Reynold July 6, 2011 Thank you so much Vivek:) Reply 45 Maheswaran August 25, 2011 Thanks a lot. It works in Centos 6 and Fedora 14. Reply Leave a Comment Name * E-mail * Website

You can use these HTML tags and attributes for your code and commands: <strong> <em> <ol> <li> <u> <ul> <blockquote> <pre> <a href="" title=""> Notify me of followup comments via e-mail.
Submit

Tagged as: /etc/fstab, fdisk command, format iscsi volume, iSCSI, iscsi centos, iscsi howto, iscsi initiator, iscsi redhat, iscsi storage, iscsiadm command, mke2fs_command, mkfs.ext3_command, mount iscsi volume, red hat iscsi, red hat linux iscsi, scsi protocol, target

Previous post: Postfix Flush the Mail Queue Next post: How to: Linux Play DivX .avi video codec file Sign up for our daily email newsletter:
Enter your email address

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011

CentOS / Red Hat Linux: Install and manage iSCSI Volume

Page 13 of 13

Search

nixCraft
Jaime 13,473 personnes aiment nixCraft.

Saneet

Llane

Prabakaran

Ranjeet

Prince

Nischay

Sabarish

Vendro

Related Posts

CentOS 4 / Redhat Enterprise Linux 4 iSCSI Installation and Configuration ( iscsi initiators ) Linux tgtadm: Setup iSCSI Target ( SAN ) Can I boot My Linux Server from iSCSI or SAN or NAS network attached storage?

2004-2011 nixCraft. All rights reserved. Cannot be reproduced without written permission. Privacy Policy | Terms of Service | Questions or Comments | Copyright Info | Sitemap

http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

11/09/2011