07-02-2012
This User Gave Thanks to fpmurphy For This Post:
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, This is my first post and I hope I can present my questions the right way. I am going to be asked to create logical volumes for a Hitachi SAN device on a New HP 11 server. Currently, They are running their data on a EMC (prod server). They are looking to convert the data and filesystems over to... (3 Replies)
Discussion started by: Uni-dev
3 Replies
2. AIX
Hi All,
I have these config on my old ssa.
Vg4 22GB (pps 256)
Vg2 88GB (pps 128)
Vg3 22GB (pps 256)
Vg8 88GB (pps 128)
Vg13 106GB (pps 32)
Vg12 106GB (pps 32)
Vg10 54GB (pps 64)
Vg11 54GB (pps 64)
When I create a lun on my san do I need to specify the same pps. If yes,... (1 Reply)
Discussion started by: itik
1 Replies
3. Solaris
I am looking for the number of luns a server is seeing or mapped to. My guess is /kernel/drv/lpfc.conf or qla2xxx.conf will tell me. Am I on the right track? Thanks. Y4Net. (4 Replies)
Discussion started by: Y4Net
4 Replies
4. Filesystems, Disks and Memory
Hi
Iīm new to san and lunīs
I see the disks, but are not able to mount them
bash-3.00# mountall
checking ufs filesystems
/dev/rdsk/c3t5006016930601F86d0s6: I/O error
Can't open /dev/rdsk/c3t5006016930601F86d0s6: I/O error
/dev/rdsk/c3t5006016930601F86d0s6: CAN'T CHECK FILE SYSTEM.... (1 Reply)
Discussion started by: ludvig
1 Replies
5. AIX
Hi team,
2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612154910 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612154910 P H dac0 ... (4 Replies)
Discussion started by: kkeng808
4 Replies
6. Linux
Hi,
I have presented a new 70GB LUN to my RedHat Linux VM server. How do I rescan for the new LUN?
Thanks,
Sparcman:confused: (2 Replies)
Discussion started by: sparcman
2 Replies
7. Red Hat
Hi guys I have been asked for the following:
SMI Oracle database PTP10 Oracle 10g RAC on usdfslprac4 and usdfslprac5 Linux boxes is reaching its space limit. It is just 20 GB away from being completely out of disk space. And then database will stop working and SMI system hence will be impacted.... (0 Replies)
Discussion started by: 300zxmuro
0 Replies
8. Solaris
how to create luns plzzzzzz (1 Reply)
Discussion started by: nsusheelgoud
1 Replies
9. Red Hat
In Solaris the administrator has to update /kernel/drv/sd.conf file to tell the sd driver to scan for a broader range of scsi devices.
Can someone please tell me what file needs to be update in Redhat Linux 5 for the same.
Second part of the question is WWN for HBA's can be found (atleast in my... (1 Reply)
Discussion started by: Tirmazi
1 Replies
10. Hardware
Hello Experts,
I have few doubts on RAID 5 with LUNs carved as STRIPE and CONCAT
RAID 5 = STRIPE + Parity mirroring
I would like to know if the LUNs carved are CONCATE from RAID 5 disk array. Are the I/Os are spread accross the disks within the RAID 5 Array? And if I do carve STRIPED... (1 Reply)
Discussion started by: sybadm
1 Replies
CTLD(8) BSD System Manager's Manual CTLD(8)
NAME
ctld -- CAM Target Layer / iSCSI target daemon
SYNOPSIS
ctld [-d] [-f config-file]
DESCRIPTION
The ctld daemon is responsible for managing the CAM Target Layer configuration, accepting incoming iSCSI connections, performing authentica-
tion and passing connections to the kernel part of the native iSCSI target.
Upon startup, the ctld daemon parses the configuration file and exits, if it encounters any errors. Then it compares the configuration with
the kernel list of LUNs managed by previously running ctld instances, removes LUNs no longer existing in the configuration file, and creates
new LUNs as necessary. After that it listens for the incoming iSCSI connections, performs authentication, and, if successful, passes the
connections to the kernel part of CTL iSCSI target, which handles it from that point.
When it receives a SIGHUP signal, the ctld reloads its configuration and applies the changes to the kernel. Changes are applied in a way
that avoids unnecessary disruptions; for example removing one LUN does not affect other LUNs.
When exiting gracefully, the ctld daemon removes LUNs it managed and forcibly disconnects all the clients. Otherwise - for example, when
killed with SIGKILL - LUNs stay configured and clients remain connected.
To perform administrative actions that apply to already connected sessions, such as forcing termination, use ctladm(8).
The following options are available:
-f config-file
Specifies the name of the configuration file. The default is /etc/ctl.conf.
-d Debug mode. The server sends verbose debug output to standard error, and does not put itself in the background. The server will
also not fork and will exit after processing one connection. This option is only intended for debugging the target.
FILES
/etc/ctl.conf The configuration file for ctld. The file format and configuration options are described in ctl.conf(5).
/var/run/ctld.pid The default location of the ctld PID file.
EXIT STATUS
The ctld utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
ctl(4), ctl.conf(5), ctladm(8)
HISTORY
The ctld command appeared in FreeBSD 10.0.
AUTHORS
The ctld was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.
BSD
November 9, 2014 BSD