06-19-2015
Why we are using storage snaps instead of zfs snaps
The reasons are numerous and lengthly, but the TL,DR is infrastructure and DR.
With reference to your reboot comment: This is a zpool with exported datasets to a non-global zone. You can't export the zpool unless the dataset isn't being used (i.e. the zone with the dataset assigned is offline) and thus the requirement for the zone reboot.
I'm looking into replacating the functionality of time-slider with scripts and crons.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I need to increase a veritas filesystem I have currently mounted on a Solaris 10 server. We can resize the LUN on the NetApp filer no problem. What I need to know is what do I do next on the Solaris 10 server I have so that it will see the increase in size. Do I run 'devfsadm' to... (3 Replies)
Discussion started by: gwhelan
3 Replies
2. Solaris
Hi,
I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies
3. Solaris
I had a pool which was exported and due to some issues on my SAN i was never able to import it again. Can anyone tell me how can i destroy the exported pool to free up the LUN. I tried to create a new pool on the same pool but it gives me following error
# zpool create emcpool4 emcpower0c... (0 Replies)
Discussion started by: fugitive
0 Replies
4. Solaris
I am not seeing anyway to remove a LUN from a Zpool...
Am I missing something? or do i have to destroy the zpool and recreate it? (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
5. Solaris
Hi All,
I am trying to read zpool.cache file to find out pool information like pool name, devices it uses and all properties.
File seems to be in packed format.I am not sure how to unpack it.
But from opensolaris code base we can see that they have used libz for uncompromising this file, but... (0 Replies)
Discussion started by: shailesh_111
0 Replies
6. AIX
Hello,
It's been a while since I've done AIX..., but I'm planning
a new TSM on AIX disk-only backup solution.
I'm planning to make an AIX volume group out of 40 luns of 1 TB.
I'm planning to create one big file system on here.
The purpose for this is to use this as a device class FILE for... (5 Replies)
Discussion started by: smashingpumpkin
5 Replies
7. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
8. Solaris
Hello,
Does anyone know how I can tell what disk are being not being used by a zpool?
For example in Veritas Volume manager, I can run a "vxdisk list" and disks that are marked as "online invalid" are disk that are not used.
I'm looking for a similar command in ZFS which will easily show... (5 Replies)
Discussion started by: robertinoau
5 Replies
9. Red Hat
Hi,
I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is :
node 1 shows the shared iscsi lun as sdc
node 2 shows the same as sdg (changes on reboots)
Due to this (i guess) i get i/o error & i can not read files created by... (0 Replies)
Discussion started by: heman96
0 Replies
10. Linux
Hi
I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o
GNU/Linux
I have first run the df -h and got the following:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_outsystemdb-lv_root
50G 2.7G 45G ... (3 Replies)
Discussion started by: fretagi
3 Replies
LEARN ABOUT NETBSD
iscsi-target
ISCSI-TARGET(8) BSD System Manager's Manual ISCSI-TARGET(8)
NAME
iscsi-target -- service remote iSCSI requests
SYNOPSIS
iscsi-target [-46DV] [-b block length] [-f configuration file] [-p port number] [-s maximum number of sessions] [-t target name]
[-v verbose arg]
DESCRIPTION
iscsi-target is the server for iSCSI requests from iSCSI initiators. iscsi-target listens for discovery and login requests on the required
port, and responds to those requests appropriately.
Options and operands available for iscsi-target:
-4 iscsi-target will listen for IPv4 connections, and respond back using IPv4. This is the default address family.
-6 iscsi-target will listen for IPv6 connections, and respond back using IPv6.
-b blocksize
Specify the underlying block size for iSCSI storage which will be served. The possible sizes are: 512, 1024, 2048, and 4096 bytes,
with the default being 512 bytes.
-D When this option is specified, iscsi-target will not detach itself from the controlling tty, and will not become a daemon. This can
be useful for debugging purposes.
-f configfile
Use the named file as the configuration file. The default file can be found in /etc/iscsi/targets. See targets(5) for more informa-
tion.
-p port number
Use the port number provided as the argument as the port on which to listen for iSCSI service requests from initiators.
-s maximum number of sessions
Allow the maximum number of sessions to be initiated when connecting to the target.
-t filename
The target name (as it appears to the iSCSI initiator) can be specified using this flag.
-V iscsi-target will print the utility name and version number, and the address for bug reports, and then exit.
-v argument
The amount of information shown can be varied by using this command. Possible values of argument are net to show network-related
information, iscsi to show iSCSI protocol-related information, scsi to show SCSI protocol information, and all to show information
from all of the above arguments.
FILES
/etc/iscsi/targets the list of exported storage
/var/run/iscsi-target.pid the PID of the currently running iscsi-target
SEE ALSO
targets(5)
HISTORY
The iscsi-target utility first appeared in NetBSD 4.0.
BSD
May 27, 2006 BSD