Sponsored Content
Top Forums UNIX for Advanced & Expert Users Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)? Post 302460765 by radoulov on Thursday 7th of October 2010 01:52:26 PM
Old 10-07-2010
Please read the rules!
No duplicate posting!
Continue here.

Thank you!
 

9 More Discussions You Might Find Interesting

1. BSD

Mount Fat32,ext3

Hello All, How can i mount ext3 and Fat partition in FreeBSD 6.0 (0 Replies)
Discussion started by: jaibw
0 Replies

2. Solaris

How can I mount a ufs filesystem on a solaris 10 sparc onto a Linux server

Hi there, I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server. *I have re-compiled the linux kernel t support ufs fstype with ro mount support. filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies

3. Solaris

Solaris 10 10/08 sparc + iSCSI

hi, I have installed Solaris 10 10/08 on sparc machine. I would like to configure iSCSI on that to mount SAN Volumes. Is there any need to install any additional patches for iSCSI to work. Thanks, Prashant. (4 Replies)
Discussion started by: prashantbhushan
4 Replies

4. Solaris

Iscsi - target + initiator on the same host.

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

5. UNIX for Advanced & Expert Users

LTO2 tape drive as iSCSI target

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

6. Solaris

Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

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

7. HP-UX

After adding new iscsi target port, still the session state of that target port is showing offline

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

8. HP-UX

Unable to delete iscsi target

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

9. Linux

How to boot iSCSI target from console 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
ISCSI(4)						   BSD Kernel Interfaces Manual 						  ISCSI(4)

NAME
iscsi -- iSCSI initiator SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file: device iscsi Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): iscsi_load="YES" DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar- get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol. SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: kern.iscsi.ping_timeout The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time the session gets forcibly restarted. kern.iscsi.iscsid_timeout The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry. kern.iscsi.login_timeout The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry. kern.iscsi.maxtags The maximum number of outstanding IO requests. kern.iscsi.fail_on_disconnection Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished. SEE ALSO
iscsi.conf(5), iscsictl(8), iscsid(8) HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0. AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation. BSD
September 11, 2014 BSD
All times are GMT -4. The time now is 05:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy