I've been trying to figure out how to set up a partition on my CentOS serve r as an iscsi target, so I can access it from another CentOS client.I've been reading the manuals and various pages on the web, and nothing is very clear. I just want to be able to create a partition on my server, define it as a target, and then have my client initiator mount it.
View 2 RepliesI want to run ISCSI target on CentOS. Both "scsi-target-utils" and "iscsi-target" can be used.
They seem to have the same function.
Is there any significant difference between them, on performance or stability?
i have installed centOS5. i want to configure iscsitarget. i know that iscsi target is built-in in centOS5. how can i use iscsiadm utility to configure iscsi target. please describe in detailed.
1.) i want to make 4 drives (4Drives OR 4LUNs)in iscsi target each with 5GB space.
2.) please describe and highlight where we mention disk space(5GB)
I am trying to install iscsi-target on centos 5.4 i386. When I go into the iscsi-target directory and type make I get the following error:
[root@cluster-storage iscsitarget-1.4.19]# make
cc: /lib/modules/2.6.18-164.el5/build/include/linux/version.h: Datei oder Verzeichnis nicht gefunden
cc: keine Eingabedateien
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -lt: unary operator expected
make -C usr
make[1]: Entering directory `/opt/iscsitarget-1.4.19/usr' .....
make: *** [kernel] Fehler 2
iSCSI Server, can I change the default port 3260 to other port ?
View 1 Replies View RelatedI want to install iscsi-target package in opensuse 11.1.
Step 1:
linux-7bvl:~ # zypper search iscsitarget
Loading repository data...
[code]....
connecting to my QNAP iSCSI target from Ubuntu (10.04). I've followed the instructions in the QNAP manual, but I something goes wrong when I need to list the nodes. When I enter
[Code]....
was able to install iSCSI target via yum, configured a couple of target LUNs, in fact all the same steps that worked on Fedora 10 appeared identical. However, when I try to start the service the following happens.
[root@Server01 ~]# service iscsi-target start
Starting iSCSI target service: FATAL: Error inserting crc32c_intel (/lib/modules/2.6.29.4-167.fc11.i686.PAE/kernel/arch/x86/crypto/crc32c-intel.ko): No such device
[code]...
I have an Intel NIC supporting iSCSI boot.I successfully installed Karmic Server 64-bit on the iSCSI target.But it won't boot from it.It looks like it can't mount the iSCSI target:
Code:
Gave up waiting for root device. Common problems: ...
and it drops me to a BusyBox shell.
[code]....
The first server I installed installed fine. The second server, installed with the same config, went to "kernel panic not syncing no init found try passing init= option in kernel" error. I tried reinstalling but it keeps going to that error after install reboot. The storage is ISCSI connected via Intel Server Adapter, which allows it to boot from ISCSI. Not sure if that's the cause for the problem, but the first server is connected to the same ISCSI and installed just fine.
Is there a way that I can make sure ISCSI module installs during installation? Although I think it is installed since it's able to copy the files and setup /dev/sda. I just wana make sure that it installs during setup.
I have never done this before but stood up a new Debian (testing) x64 system. It only has 146GB available for RAID1 so I created a 500GB iSCSI LUN on my NAS device on the network and am really confused how I can attach my Debian to the iSCSI LUN I created. Right now the OS is installed all locally on the machine but I would like the iSCSI LUN to be the /home directory for mail storage. Is this possible or do I need to mount the LUN to a newly created folder / mount point that is locally attached?
View 1 Replies View RelatedI seem to get logged into the NetApp filer fine - it shows the session, but I don't get a device. And don't panic - the system is CentOS 5.4, but the system is named OpenVMS (don't ask . . . ) iscsiadm shows me logged into the NetApp and the session is up.
[Code]....
I have an iSCSI device that is large, ~17TB usable, and I've created an XFS file system at the device level. I mount the device no problem and am able to touch and remove files without issue. I start my application and within about 5-10 minutes I start seeing the following entries appear in /var/log/messages
[Code]...
I have a CentOS 5.3 server, running in a VM. I get the iSCSI session to my Buffalo, but the disk doesn't appear.
Sep 29 09:06:29 qaservice iscsid: iscsid shutting down.
Sep 29 09:06:29 qaservice kernel: Loading iSCSI transport class v2.0-871.
Sep 29 09:06:29 qaservice kernel: iscsi: registered transport (tcp)
Sep 29 09:06:29 qaservice kernel: iscsi: registered transport (iser)
[Code].....
Linux 2.6.18-238.9.1.el5
Apache 2.2.3
MySql 5.0.77
PHP 5.3.3
Samba 3.5.4-0.70.el5_6.1
Problem: my server eats up all the memory in the box after a few days. My guess is it has something to do with these processes:
[Code]...
it is not clear to me, by reading different postings/documentations for ntfsclone, what restrictions and/or requirements exist for the target partition (TARGET). Can the TARGET be bigger in size than the SOURCE, or must it be identical? Must the TARGET be formatted as an NTFS filesystem, or must it left unformatted?
View 5 Replies View RelatedI built a CentOS 5 Linux cluster with GFS storage using local RAID volume and share it with gnbd_export/import on two web-servers. Now I need to expand that storage to another servers local volume. I saw the picture in the manual, but I don`t know, how can I create that scheme.
I can use gnbd_export on the second server and gnbd_import on the first. In that case I will have two volumes on the first storage and I can expand volume group, logical volume, etc on it.
What is the correct way to allow two servers to use the same file system on a SAN using iSCSI?Is it GFS on the two servers?
View 3 Replies View RelatedI have a server wich is connected to an iSCSI storage and gets harddisks from this storage. Sometimes I have to add new disks to this server. Everytime I add a disk and make an /etc/init.d/iscsi restart on the server the disks don't have the same device name as before the iscsi restart.
It should be possible to gave the disks persistent names using udev rules. Now I tried to create different rules in "/etc/udev/rules.d/99-static-iscsi-names.rules" e.g.
# /dev/sdc
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -s %p",RESULT=="360a98000503355344c4a576864467877" NAME=="sdc%n"
In "/etc/rc.local" I added "/sbin/start_udev" and in "/etc/scsi_id.config" I added the line "vendor="NETAPP",model="LUN",options=-g"
[Code]...
I have a fairly simple iSCSI setup using two devices, but they have swapped names on different machines. running CentOs 5.3 ia64, and using iscsi-initiator-utils-6.2.0.868-0.18.el5
vm1:
[root@vm1 ~]# fdisk -l
Disk /dev/xvda: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[Code].....
Any way to get iSCSI to mount the devices as consistent device names ?
I'm trying to configure an ISCSI/DRBD high-availability cluster and I'd like to know what is the best option between OpenAIS and Heartbeat. I've seen they both are included in Centos Repos, yet OpenAIS requires installing 2 addition repos to install Pacemaker (EPEL and Clusterlab repos).
View 1 Replies View RelatedWe have a Centos 5.6 server mounting two iSCSI volumes from an HP P2000 storage array. Multipathd is also running, and this has been working well for the few months we have been using it. The two volumes presented to the server were created in LVM, and worked without problem.We had a requirement to reboot the server, and now the iSCSI volumes will no longer mount. From what I can tell, the iSCSI connection is working ok, as I can see the correct sessions, and if I run 'fdisk -l' I can see the iSCSI block devices, but the O/S isn't seeing the filesystems. Any LVM command does not show the volumes at all, and 'vgchange -a y' only lists the local boot volume, not the iSCSI volumes. My concern is that, the output of 'fdisk -l' says 'Disk /dev/xxx doesn't contain a valid partition table' for all the iSCSI devices. Research shows that performing the vgchange -a y command should automatically mount any VG's that aren't showing, but it doesn't work.
There's a lot of data on these iSCSI volumes, and I'm no LVM expert. I've read that some have had problems where LVM starts before iSCSI and things get a bit messed up, but I don't know if this is the case here (I can't tell), but if there's a way of switching this round that might help, I'm prepared to give it a go.There was absolutely no indication there were any problems with these volumes, so corruption is highly unlikely.
My goal is to connect up a bunch of CentOS 5.6 servers to storage array which is running as an SRP target. These servers will be running eventually as Xen hypervisors. I'm using Mellanox Infiniband cards and a Qlogic Infiniband switch.
OFED drivers are already installed as standard. I have done the following.
1. Base install of CentOS 5.6 X86_64
2. Installed the following packages...
openib
ibutils
srptools
infiniband-diags
opensm
[Code]...
It works perfectly and connects to the target immediately with great results. I'd just like this to happen correctly on startup.
To work around the issue I have added the line srp_daemon -e -o into the init script for opensm /etc/init.d/opensmd but it doesnt always start the srp_daemon process. Its rather hit and miss
I'd really like srp_daemon to run as a service with a proper init script but I wouldnt know how to write one. I understand that this issue has been addressed in the RHEL6 srptools package but that doesnt help me because the software I intend to use on these servers specifically requires 5.
What I am trying to do is edit the link target to force ip=xxxx.xxx.xxx string at end. I have a software program which access 4 different servers running the software but with different configs. In xp I can copy links and modify as above to correctly force the program to the various servers.
I have read the various how tos on hard vs sym links which I get. Playing around with hardlinks and sysmlinks (the examples I find) does not seem to be what I need. Feel like this is pretty basic stuff but I am a bit stumped.
Trying to install Centos 5.2.i386 from DVD in text install (I'm assuming I need to do text install as I'm setting up raid arrays)
I have 4x150Gb raptors where I want the following layout:
/dev/sda/
/dev/sda1 100Mb (for /boot in raid 1, 4 disks)
/dev/sda2 1000Mb (for swap, raid 0, 4 disks)
/dev/sda3 4000Mb (for /, raid 5, 4 disks)
[Code].....
In the last attempt I did, sdb,sdc and sdd all had the correct ordering of partitions, but sda looked like above, which means I would need to assemble by boot array partition array as /dev/md0 = /dev/sda3, /dev/sdb1, dev/sdc1, dev/sdd1
Why is the partition numbering moving around as I create them?
3 partitions (in order): Windows 7, CentOS and shared data partition.
I need to increase the size of the Windows 7 partition (c:windowswinsxs seems to be something not easily remedied).
GParted didn't work in moving things around (bad sector) so I wiped out its partition (# 2 out of 3) and I was able to increase the size of the Windows 7 partition (I can reinstall CentOS easily and not much work lost).
Except ... no more grub menu (unsurprising). This incantation does allow me to boot into Windows 7.
Is there any way of rebuilding the grub menu short of reinstalling CentOS (5.5)?
I have a laptop that came with Windows Vista (64-bit) installed. I created a new partition and installed XP (also 64-bit) alongside it.Last night I shrunk my XP partition and created another new partition and installed Linux (CentOS 64-bit) on it. I made an error in judgment and didn't allocate enough space, so I need about 10 more gigs for the Linux partition. It boots up and runs, but I need about 10 more gigs of storage for the files I want to keep on the partition (and yes, they have to be on the partition, I definitely need to know how to do this, not a workaround)I went into Vista and shrunk the XP partition by 10 gigs, so now I have 10 gigs of free, non-partitioned space.
As it stands, when I start up the computer I get the GRUB boot loader. I can boot my Linux install or choose "Other" and be taken to the Vista boot loader. From there I can choose XP or Vista to boot.So, my question is... what is the best way to append the 10 gigs of free space to the Linux partition? Is this something I should do inside of Linux? I have the option to do it in Vista, but the partition shows up as "healthy" but without a file system type.I just don't want to screw up the boot loader, partitions or anything else.This isn't my area of expertise, so if anyone could give me a good suggestion or solid answer
I have an iSCSI target on my Ubuntu 10.04 LTS server that is giving me access to 3 x 2TB volumes. I am using LVM to create 1 big volume and using it as a place for my backup software to write to. Upon initial setup I tested to see if the connection would still be there after a reboot, and it was. After going through the trouble of configuring my backup software (ZManda) and doing a few very large backups I had to reboot my SAN (OpenFiler) for hardware reasons. I took my server down while performing the maintenance and brought it back up only after the SAN work was done. Now, the LVM volume is listed as "not found" when booting.
Using iscsiadm I can see the target but LVM doesn't know of any volumes that exist using those targets. I need to get it back up and running and then troubleshoot the reboot issue.
iscsi-client OS: SLES10SP3i586I configured this sles10sp3 box an iscsi-client via YaST (yast2 iscsi-client), but 'lsscsi' or 'fdisk -l' doesnt show any iscsi-disk
# rcopen-iscsi restart
Closing all iSCSI connections: Logging out of session [sid: 1, target: iqn.2010-03.com.ibm:sn.135026430, portal: 192.168.0.1,3260]
[code]....
I'm trying to increase the size of an iSCSI device. On the LUN side, the provision size has been expanded already. I expanded the size of this device from 15GB to 30GB.
I then rescanned the devices:
[root@ps-dev-nfs ~]# iscsiadm -m node --targetname iqn.2001-05.com.equallogic:0-8a0906-db7938c02-c6a994bda8a4a773-ps-dev-nfs -R
Rescanning session [sid: 1, target: iqn.2001-05.com.equallogic:0-8a0906-db7938c02-c6a994bda8a4a773-ps-dev-nfs, portal: 10.3.2.10,3260]
[Code].....