Login or Register to Ask a Question and Join Our Community


SuSE

iscsi network share + xfs

Login to Discuss or Reply to this Discussion in Our Community

 
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

LEARN ABOUT FREEBSD

iscontrol

ISCONTROL(8)						    BSD System Manager's Manual 					      ISCONTROL(8)

NAME

     iscontrol -- login/negotiator/control for an iSCSI initiator session

SYNOPSIS

     iscontrol [-dv] [-c file [-n nickname]] [-p pidfile] [-t target] [variable=value]

DESCRIPTION

     This command, along with its kernel counterpart iscsi_initiator(4), is obsolete.  Users are advised to use iscsictl(8) instead.

     Internet SCSI (iSCSI) is a network protocol standard, that allows the use of the SCSI protocol over TCP/IP networks, the iscontrol program is
     the userland side of an iSCSI session, see iscsi_initiator(4).  It has 2 modes of operation, if -d (discovery session) is specified, it will
     print out the target names returned by the target and exit.  In the second mode, it will, after a successful login/negotiation, run in daemon
     mode, monitoring the connection, and will try to reconnect in case of a network/target failure.  It will terminate/logout the session when a
     SIGHUP signal is received.  The flags are as follows:

     -c file	     a file containing configuration key-options, see iscsi.conf(5).

     -d 	     do a discovery session and exit.

     -n nickname     if -c file is specified, then search for the block named nickname in that file, see iscsi.conf(5).

     -p pidfile      will write the process ID of the session to the specified pidfile

     -t target	     the target's IP address or name.

     -v 	     verbose mode.

     variable=value  see iscsi.conf(5) for the complete list of variables/options and their possible values.

EXAMPLES

	   iscontrol -dt myiscsitarget

     will start a discovery session with the target and print to stdout the list of available targetnames/targetadresses.  Note: this listing does
     not necessarily mean availability, since depending on the target configuration, a discovery session might not need login/access permission,
     but a full session certainly does.

	   iscontrol -c /etc/iscsi.conf -n myiscsi

     will read options from /etc/iscsi.conf, use the targetaddress found in the block nicknamed myiscsi, login and negotiate whatever options are
     specified, and start an iscsi-session.

SEE ALSO

     da(4), iscsi_initiator(4), sa(4), iscsi.conf(5), camcontrol(8), iscsictl(8)

STANDARDS

     RFC 3720

BUGS

     iscontrol should probably load the iscsi_initiator module if needed.
     Not all functions/specifications have been implemented yet, noticeably missing are the Task Management Functions.	The error recovery, though
     not fully compliant does a brave effort to recover from network disconnects.

BSD
								  October 9, 2014							       BSD