iscsi network share + xfs


 
Thread Tools Search this Thread
Operating Systems Linux SuSE iscsi network share + xfs
# 1  
Old 02-04-2011
iscsi network share + xfs

Hello,

we got a MD3000i used as a network share between two servers (say A and B). The problem we are facing is that file/directories created by server A are not visible on server B (and viceversa). It's not a problem with permission (chmod 777 doesn't help).

The MD3000i was at first used ony with server A. We then added server B. All files/directories added "before B" were readable from both A and .

Here are some details:

MD3000i

Read cache: Enabled
Write cache: Enabled
Write cache without batteries: Disabled
Write cache with mirroring: Disabled
Flush write cache after (in seconds): 10.00
Dynamic cache read prefetch: Enabled


XFS filesystem.

On server A we have (from /etc/fstab)

/dev/disk/by-id/scsi-36a4badb000443c1c000003a04bf628a4-part1 /storage xfs noauto,nofail 0 0

Could be a problem with a combination of cache and xfs barriers?

---------- Post updated at 05:40 PM ---------- Previous update was at 02:28 PM ----------

Ok, solved.
filesystem xfs doesn't support clustering.Smilie

We need to use lock-aware fiesystem as OCFS, GFS or something.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

Best solution for a network share?

This is in a CentOS 6 environment, our developer needs to be able to specify a relative path to a shared folder so that four machines can all point to the same shared directory, so I need to know the easiest way to do this in a native Linux environment. I've already created the directory on the... (2 Replies)
Discussion started by: xdawg
2 Replies

2. UNIX for Advanced & Expert Users

VMWare,XFS and iSCSI issues!

I have a RHEL6 VM that requires the use of remote storage using iSCSI and XFS for the mount point. Here's the issue: With XFS you can't use the _netdev option for your mount point (pause for network) so my mount point doesn't mount properly because the network isn't up yet. I've moved the... (3 Replies)
Discussion started by: ksfolsom
3 Replies

3. Solaris

Windows network share visible to Solaris 9 host and vice versa

Hi, I have a Windows server running WinSVR 2008R2 with a network share configured \\hostname\JSS_Share I would like to be able to mount this share on a Solaris host running Solaris 9. I would also like to mount a directory on the Solaris host and make it visible to the Windows server. The idea... (1 Reply)
Discussion started by: jamba1
1 Replies

4. Solaris

How can I setup a NFS server to share with a whole network?

I have a solaris 10 system that is setup as a NFS server. The NFS clients have DHCP running. How do I setup the server, so that it allows mounts for any machine on the network? (3 Replies)
Discussion started by: krishania
3 Replies

5. UNIX for Dummies Questions & Answers

How to change ethernet cable of iscsi initiator (iscsi client)?

how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies

6. UNIX for Advanced & Expert Users

[XFS] How to use real-time subvolume

Hi! I created filesystem XFS on partition hda8 with subvolume real-time on partition hda5: mkfs.xfs -r rtdev=/dev/hda5 /dev/hda8 and i mounted it: mount -t xfs -o rtdev=/dev/hda5 /dev/hda8 /xfs But I don't know how can I use this partition hda5 with subvolume real-time. I don't know how to... (3 Replies)
Discussion started by: Cadi2108
3 Replies

7. Filesystems, Disks and Memory

Gfs2 vs xfs vs ext4

Looking for suggestions as to which filesystem to go with. I currently use gfs2 on hosts with 3.4tb useable. I understand gfs2 is being left behind but xfs and ext4 are not quite certified completely on CentOS 5.2. I have email storage hosts that have a decent i/o requirement and 12TB usable after... (12 Replies)
Discussion started by: king_hippo
12 Replies

8. UNIX for Dummies Questions & Answers

Linux Server Network Settings - Share Directory Structure

Hello Unix Gurus Who I Hope Reads This, I have quasi-inherited control over a Linux cluster at a university research lab. The post-doc that set it up is gone, and the person in charge of administering the cluster doesn't know a ton about Linux. Amongst other things, I want to use the cluster... (0 Replies)
Discussion started by: mbl
0 Replies

9. UNIX for Dummies Questions & Answers

output of file from several machines written to network share, then emailed to group.

I have a script on all the machines on my network that lists how many updates are available for each machine, and then outputs the answer to a file called updates.txt the output shows the hostname and the number of updates, like: computer_A 7 I want all these machines to output the data to... (1 Reply)
Discussion started by: glev2005
1 Replies
Login or Register to Ask a Question
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)