8 More Discussions You Might Find Interesting
1. Linux
I need boot any images from iSCSI and I'd like to boot from linux console of a previous LiveCD booted. Is possible, without gpxe, ipxe firmware or similar? With a simple iSCSI initiator for example? (1 Reply)
Discussion started by: spark2k06
1 Replies
2. HP-UX
Hi
Please can someone give me a hint on this, when I list the targets, I see two o them:
#iscsiutil -p
Operational Target Information
------------------------------
Target # 1
-----------
Target Name : iqn.1992-08.com.netapp:sn.142241859
Target Alias ... (2 Replies)
Discussion started by: fretagi
2 Replies
3. HP-UX
Hi,
I wanted to configure new iscsi port on HPUX system, i added the target port address and configured it, once done, went to array side and searched for that host iqn number , but was nt able to find the same, came to host, then when i ran "iscsiutil -pVS" command it gave me below result
... (0 Replies)
Discussion started by: Vinay Kumar D
0 Replies
4. UNIX for Advanced & Expert Users
I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got
fdisk: "Error in ioctl DKIOCSMBOOT"
Details --
According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (1 Reply)
Discussion started by: ctafret
1 Replies
5. Solaris
I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got
fdisk: "Error in ioctl DKIOCSMBOOT"
Details --
According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (0 Replies)
Discussion started by: ctafret
0 Replies
6. UNIX for Advanced & Expert Users
I'm using Bacula as my backup system, with full backups going to an LTO2 tape drive, while differentials and incrementals go to a disk array on my main server, babylon4. The tape drive is currently attached to a separate machine, because babylon4 does not have a SCSI controller, nor a free PCI-X... (0 Replies)
Discussion started by: Phil Stracchino
0 Replies
7. Solaris
Hi all
iscsiadm / iscsitadm.
Ive created two devices on a host.
# iscsitadm list target
Target: 1-disk0
iSCSI Name: iqn.1986-03.com.sun:02:f105ddf3-52a4-ed7a-9590-c3d354b8fc32.1-disk0
Connections: 1
Target: 1-disk1
iSCSI Name:... (0 Replies)
Discussion started by: sbk1972
0 Replies
8. Solaris
Hello!
I have several disks discovered using iscsi protocol.
There disks are represented in OS like c2txd0 .
logs:
Is it possible to change drive path, for example, from c2t6d0 to c2t7d0?
It's important for me because I have to install oracle RAC on RAW devices.
NIck (0 Replies)
Discussion started by: skelet
0 Replies
allocate(1) allocate(1)
NAME
allocate - device allocation
SYNOPSIS
allocate [-s] [-U uname] device
allocate [-s] [-U uname] -g dev-type
allocate [-s] [-U uname] -F device
The allocate utility manages the ownership of devices through its allocation mechanism. It ensures that each device is used by only one
qualified user at a time.
The device argument specifies the device to be manipulated. To preserve the integrity of the device's owner, the allocate operation is exe-
cuted on all the device special files associated with that device.
The argument dev-type is the device type to be operated on and can only be used with the -g option.
The default allocate operation allocates the device special files associated with device to the uid of the current process.
If the -F option is specified, the device cleaning program is executed when allocation is performed. This cleaning program is found in
/etc/security/lib. The name of this program is found in the device_allocate(4) entry for the device in the dev-exec field.
Only authorized users may allocate a device. The required authorizations are specified in device_allocate(4).
The following options are supported:
-g dev-type Allocates a non-allocated device with a device-type matching dev-type.
-s Silent. Suppresses any diagnostic output.
-F device Reallocates the device allocated to another user. This option is often used with -U to reallocate a specific device to a
specific user. Only a user with the solaris.device.revoke authorization is permitted to use this option.
-U uname Uses the user ID uname instead of the user ID of the current process when performing the allocate operation. Only a user
with the solaris.device.revoke authorization is permitted to use this option.
The following exit values are returned:
non--zero An error occurred.
/etc/security/device_allocate
/etc/security/device_maps
/etc/security/dev/*
/etc/security/lib/*
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
deallocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5)
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for
more information.
/etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment.
28 Mar 2005 allocate(1)