03-01-2018
Creating metadevices
Hi
I am new to SVM, but I would like to configure it in one of my servers. The setup is as follows: I have one server running solaris 10 , and is connected to a NetApp via iSCSI protocol. This is how I intend to do it:
Ask the NetApp admin, to provide me with 3 LUNs of 100G each, them use the format comand.
This is where I am stuck.
After creating disk devices such us c0t1d0s6 , c0t2d0s6 and c0t3d0s6, I have to create state database using metadb followed by cereating a metadevice using metainit d0 comand. Is this the right procedure?
9 More Discussions You Might Find Interesting
1. Programming
hi everyone
i have a doubt about ".so" files.
what is the need of ".so" files.
why we use ".so" files.
where we can use ".so" files.
how can i create ".so" files.
can u tell me a good example please
thank you (6 Replies)
Discussion started by: ramesh.jella
6 Replies
2. Shell Programming and Scripting
Hi,
Can someone help me with creating a bash shell script.
I need to create a script that gets a positive number n as an argument.
The script must create n directories in the current directory with names like map_1, map_2 etcetera. Each directory must be contained within its predecessor. So... (7 Replies)
Discussion started by: I-1
7 Replies
3. Solaris
Hi Guys.
I have the follow disk mappig....
My doubt is that the filesystem root is in mirroring. I can see this in the configuration but , I dont know exactly if this in mirroring mean disk in RAID.
In short: Watching the configuration...Can I said if the filesystem / is in Raid?
... (3 Replies)
Discussion started by: aggadtech08
3 Replies
4. Solaris
Hi
I am having a problem creating my live upgrade environment.
Here is the error I get:
root@server:/# lucreate -c SOL10_18May -n SOL10_19May -z /lu_excludelist -m /:dev/md/dsk/d0:ufs -m /var:/dev/md/dsk/d4:ufs -m /export/home:/dev/md/dsk/d6:ufs -m -:/dev/md/dsk/d3:swap -C... (0 Replies)
Discussion started by: notreallyhere
0 Replies
5. Solaris
Hi all,
I recently started exploring Solaris 10.
I am testing metadevices now.
I have been reading about the state databases here: 6.State Database (Overview) (Solaris Volume Manager Administration Guide) - Sun Microsystems
So I created 3 metadbs on 2 slices (6 in total; c1t1d0s3... (3 Replies)
Discussion started by: deadeyes
3 Replies
6. Solaris
Hi Guys,
We have an issue,
all metadb's on system was deleted and the system was rebooted.
the system is currented mounted in single-user mode . its a x86 server.
the volumes under SVM is as follows.
/
/var and
/usr
please suggest
Please use code tags <- click the... (1 Reply)
Discussion started by: karthick.sh
1 Replies
7. Solaris
Hi ,
We are facing an issue on one of our solaris x86 server,
After changing the hostname and a orderly reboot , all metadevices shows offline.
please let us know the steps to restore back all metadevices to working state with this new hostname (3 Replies)
Discussion started by: karthick.sh
3 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Here is what I am supposed to do, word for word from my assignment page:
1. Create/modify and print a... (2 Replies)
Discussion started by: Jagst3r21
2 Replies
9. SCO
Also, in my tinkering around I was able to get SCO installed on a VM, using VM Workstation version 12.5 in a Windows 7 Pro-64 computer. I chose the VM Workstation 8.x compatibility model for my VM, an IDE hard drive at 0:0 and an IDE CD Rom at 1:0 using the physical drive of the computer. Using the... (3 Replies)
Discussion started by: jgt
3 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