10 More Discussions You Might Find Interesting
1. AIX
Hi All,
Recently I came to know my / root file system is getting full because of application directory /siebel/
I have one option.
1) Down the application , take full backup
2)change the filesystem ownership
2)copy the contents into that filesystem
cp -pr /siebel/* /siebelfs/*
3)Inform... (9 Replies)
Discussion started by: Thala
9 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I need to mount an nfs filesystem as below.
xxx.xx.xx.xxx:/media/nss/Rocky Catherine/logs
For the above as there is space in between the name, hoping it will not mount, if i give it with double quotes as below will it work?
mount "xxx.xx.xx.xxx:/media/nss/Rocky... (2 Replies)
Discussion started by: Rockyc3400
2 Replies
3. Shell Programming and Scripting
Could anyone help me please as I am stuck up.
I want to mount /home/dun/maitree location of server A in server B to location /home/dun/tibco .Both server A and server B are Linux machine .The problem is that /home/dun/tibco of server B has some files and directory in it so after doing this... (1 Reply)
Discussion started by: maitree
1 Replies
4. Solaris
Hi techies,
I am pretty new to Solaris. So the qstn might be a silly one.
I had a local disk with Solaris installed.
I have done ufsdump to a SAN disk and after that s3 and s7 slices are giving the following error : "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY."
I had the following... (4 Replies)
Discussion started by: manojsomanath
4 Replies
5. Red Hat
i am new to linux i want to know how to create ntfs partition and mount all windows drives in linux
please help me (2 Replies)
Discussion started by: arunkmohan18
2 Replies
6. Filesystems, Disks and Memory
Hello,
In a shared storage environment is their anything to stop being able to mount the same filesystem on two hosts by accident, a flag being set or something on the storage?
If it did happen would one of the hosts panic? (2 Replies)
Discussion started by: Actuator
2 Replies
7. Shell Programming and Scripting
I have a free software project I'm working on that provides portable versions of Linux applications capable of being carried around on removable media, with settings and documents traveling along.
While developing the portable launcher, I fell into a problem: FAT32 partitions do not support... (2 Replies)
Discussion started by: dkulchenko
2 Replies
8. Solaris
Hi all,
I have a question regarding filesystem mounting.
I have one Sun box(V240) and a NAS on a network. Sun machine shows the following output of df -k command.
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 11094316 8509226 2474147 78% ... (2 Replies)
Discussion started by: prashantchavan
2 Replies
9. Red Hat
I'm currently running dual boot Linux & Windows. Linux is Fedora core 3. I've downloaded and installed the rmp that was needed so that I could mount a NTFS filesystem. But when I go to mount the filesystem I'm still getting error's stating it does not support the NTFS filesystem.
Also the... (9 Replies)
Discussion started by: woofie
9 Replies
10. BSD
I get error that I have to rund fsck manually on my filesystem, but when I go to run fsck on filesystem ad1s1e I get an error that says can't open device not configured so fsck won't rund on that filesystem. I am only booting up in single user mode. I noticed when I look in the fstab file the... (1 Reply)
Discussion started by: rbizzell
1 Replies
ISCSI-INITIATOR(8) BSD System Manager's Manual ISCSI-INITIATOR(8)
NAME
iscsi-initiator -- refuse-based iSCSI initiator
SYNOPSIS
iscsi-initiator [-46bcDfVv] [-a authentication-type] [-d digest-type] [-h target-hostname] [-p target-port-number] [-t target-number]
[-u username] mount_point
DESCRIPTION
The iscsi-initiator utility can be used to access an iSCSI target, such as iscsi-target(8), to access block storage which has been exported.
Information pertaining to the target is displayed underneath the mount point, along with the device corresponding to the storage which the
target exports.
The various arguments are as follows:
-4 Use an IPv4 connection to the target.
-6 Use an IPv6 connection to the target.
-a authentication-type
Use the specified authentication type when communicating with the target. The possible values are chap, kerberos, srp or none. The
default value is none.
-b Show the storage as a block device.
-c Show the storage as a character device.
-d digest-type
Use the specified digest type when communicating with the target. The possible values are header, data, both, all or none. The
default value is none.
-D List the LUNs on the specified target and exit (i.e. do discovery only)
-f Show the storage as a regular file.
-h hostname
Connect to the iSCSI target running on the host specified as the argument.
-p port-number
Connect to the iSCSI target running on the port specified as the argument. The default value is 3260.
-t target
Connect to the number of the iSCSI target running as the argument.
-u username
Use the specified user's credentials when logging in to the iSCSI target. There is no default.
-V Print out the version number and then exit.
-v Be verbose in operation.
The refuse(3) library is used to provide the file system features.
The mandatory parameter is the local mount point.
This iSCSI initiator presents a view of the targets underneath the mount point. Firstly, it creates a directory tree with the hostname of
the target, and, in that directory, a virtual directory is created for each target name exported by the iSCSI target program. Within that
virtual target directory, symbolic links exist for the hostname (for convenience), a textual representation of the IP address, the iSCSI tar-
get product name, the iSCSI target IQN, the iSCSI target vendor and version number. One other directory entry is presented in the virtual
target directory, relating to the storage presented by the iSCSI target. This can be in the form of a regular file, which is also the
default, a block device or a character device.
Please note that the iscsi-initiator utility needs the ``puffs'' kernel module loaded via modload(8) to operate.
EXAMPLES
# ./iscsi-initiator -u agc -h iscsi-target0.alistaircrooks.co.uk /mnt
# ls -al /mnt/target0
total 576
drwxr-xr-x 2 agc agc 512 May 11 22:24 .
drwxr-xr-x 2 agc agc 512 May 11 22:24 ..
lrw-r--r-- 1 agc agc 39 May 11 22:24 hostname -> iscsi-target0.alistaircrooks.co.uk
lrw-r--r-- 1 agc agc 14 May 11 22:24 ip -> 172.16.135.130
lrw-r--r-- 1 agc agc 16 May 11 22:24 product -> NetBSD iSCSI
-rw-r--r-- 1 agc agc 104857600 May 11 22:24 storage
lrw-r--r-- 1 agc agc 43 May 11 22:24 targetname -> iqn.1994-04.org.netbsd.iscsi-target:target0
lrw-r--r-- 1 agc agc 8 May 11 22:24 vendor -> NetBSD
lrw-r--r-- 1 agc agc 4 May 11 22:24 version -> 0
#
SEE ALSO
puffs(3), refuse(3), iscsi-target(8)
HISTORY
The iscsi-initiator utility first appeared in NetBSD 6.0. An earlier version called iscsifs was available in NetBSD 5.0 in source format
only.
AUTHORS
The iscsi-initiator utility was written by Alistair Crooks <agc@NetBSD.org>.
BUGS
iscsi-initiator currently only supports a CHAP challenge length of 16 octets. Other initiators support up to 1024 and thus it is expected
that most targets will also support such lengths. This means that CHAP compatibility with other targets apart from iscsi-target(8) is likely
to be poor. To workaround this, please use authentication type none by not specifying a username with the -u option.
BSD
February 22, 2011 BSD