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
ISCSID(8) System Manager's Manual ISCSID(8)
NAME
iscsid - establish iSCSI connections
SYNOPSIS
iscsid [ -b bindingfile ] [ -d ] [ -f configfile ] [ -l basedir ] [ -m mode ] [ -n ]
DESCRIPTION
iscsid establishes connections with iSCSI targets defined in /etc/iscsi.conf.
Once the Linux iSCSI driver is activated, a discovery process for iSCSI storage devices will proceed as follows:
- The iSCSI daemon requests available iSCSI targets from the iSCSI target, and passes the information discovered to the iSCSI kernel
module.
- The iSCSI kernel module establishes connections to the targets.
- Linux queries targets for device information.
- Linux creates a mapping from SCSI device nodes to iSCSI targets.
iscsid should be started after networking is configured and stopped after all iSCSI devices have been unmounted.
Warning: Data corruption can occur if you do not unmount iSCSI devices before disabling network interfaces!
DEVICE NAMES
Because Linux assigns SCSI device nodes dynamically whenever a SCSI logical unit is detected, the mapping from device nodes (e.g /dev/sda,
/dev/sdb) to iSCSI targets and logical units may vary.
Variations in process scheduling and network delay may result in iSCSI targets being mapped to different SCSI device nodes every time the
driver is started. Because of this variability, configuring applications or operating system utilities to use the standard SCSI device
nodes to access iSCSI devices may result in SCSI commands being sent to the wrong target or logical unit.
To provide a more reliable namespace, the iSCSI driver will scan the system to determine the mapping from SCSI device nodes to iSCSI tar-
gets, and then create a tree of directories and symbolic links under /dev/iscsi to make it easier to use a particular iSCSI target's logi-
cal units.
TARGET BINDINGS
The iSCSI driver automatically maintains a bindings file /var/iscsi/bindings. This file contains persistent bindings to ensure that the
same iSCSI bus and target id number are used for every iSCSI session to a particular iSCSI TargetName, no matter how many times the driver
is restarted.
This feature ensures that the SCSI numbers in the device symlinks described above will always map to the same iSCSI target.
Note that because of the way Linux dynamically allocates SCSI device nodes as SCSI devices are found, the driver does not and can not
ensure that any particular SCSI device node (e.g. /dev/sda) will always map to the same iSCSI TargetName. The symlinks described in the
section on Device Names are intended to provide a persistent device mapping for use by applications and fstab files, and should be used
instead of direct references to particular SCSI device nodes.
If the bindings file grows too large, lines for targets that no longer exist may be manually removed by editing the file. Manual editing
should not normally be needed, since the driver can maintain up to 65535 different bindings.
OPTIONS
-b bindingfile
Specify an alternative bindings file instead of /var/iscsi/bindings, which is the default.
-d Turns on debug mode. Each occurence of -d will increment the debug level by one. The default is zero (off).
-f configfile
Specify an alternative configuration file instead of /etc/iscsi.conf, which is the default.
-l basedir
Specify the base directory under which to build a tree of directories containing symlinks to SCSI device nodes, in a manner similar
to the devfs Linux kernel option. Using these symlinks hides variations in the mapping from SCSI device nodes to SCSI device id
numbers.
-m mode
Specify the directory permission mode (in octal) to use when creating directories.
-n Avoid auto-backgrounding.
-v Print version and exit.
SIGNALS
iscsid reacts to a set of signals. You may easily send a signal to iscsid using the following:
kill -SIGNAL `cat /var/run/iscsid.pid`
SIGTERM
The daemon and all of it's children will die.
SIGHUP sent to the main daemon process will restart all discovery processes and reprobe LUNs on all targets. iscsid and all of it's chil-
dren will die after shutting down all of the kernel's iSCSI sessions.
SIGCHLD
Wait for children.
NOTES
The iSCSI Driver for Linux provides IP access to a maximum of sixteen remote SCSI targets. Each target will be probed for up to 256 LUNs,
until the Linux kernel's limit of SCSI devices has been reached.
The iSCSI drivers, README files, and example configuration files are available on the Linux-iSCSI homepage at:
http://linux-iscsi.sourceforge.com/ <http://linux-iscsi.sourceforge.com/>
FILES
/etc/iscsi.conf
target address and LUN configuration
/var/run/iscsi.pid
the process id of the running daemon
/var/iscsi/bindings
persistent bus and target id bindings for iSCSI TargetNames
/proc/scsi/iscsi
information about iSCSI devices
/dev/iscsi
a directory tree containing symlinks to iSCSI device nodes.
SEE ALSO
iscsi.conf(5)
$Revision: 1.8 $ $Date: 2002/09/20 19:27:32 $ ISCSID(8)