VMWare,XFS and iSCSI issues! | Unix Linux Forums | UNIX for Advanced & Expert Users

  Go Back    


UNIX for Advanced & Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD.

VMWare,XFS and iSCSI issues!

UNIX for Advanced & Expert Users


Closed Thread    
 
Thread Tools Search this Thread Display Modes
    #1  
Old 12-04-2012
ksfolsom ksfolsom is offline
Registered User
 
Join Date: Dec 2012
Last Activity: 22 January 2013, 10:44 AM EST
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
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 init order in rc3.d so the network is up prior to iscsid running however I have application that trys to start before the mount is available and of course the app fails to start etc.

Any suggestions on the delay etc. would be helpful!
Sponsored Links
    #2  
Old 01-16-2013
cjcox cjcox is offline
Registered User
 
Join Date: May 2005
Last Activity: 29 July 2014, 11:20 AM EDT
Posts: 367
Thanks: 2
Thanked 37 Times in 35 Posts
Wouldn't it fail even with _netdev? Can't you just move the start of the application so it happens after the scripted init mount of the xfs area after the network setup.
Sponsored Links
    #3  
Old 01-18-2013
hicksd8 hicksd8 is offline Forum Advisor  
Registered User
 
Join Date: Feb 2012
Last Activity: 22 August 2014, 7:10 AM EDT
Location: Cornwall, UK
Posts: 791
Thanks: 38
Thanked 148 Times in 133 Posts
I'm not sure that I fully understand your issue here. Perhaps I'm being too simplistic.

You say that you've changed the order of the rc3.d boot order. These are just scripted commands which are executed in ascending numerical order so you can just create another script (eg, S78sleep) containing the command


Code:
 
sleep 60

to halt the boot process for one minute (or whatever value of seconds you choose). This will give processes already launched time to start before any following scripts.

Obviously you would only use the above if you don't care how long it takes to boot up. Otherwise, if booting time is of the essence, you could write a loop to test for a file/process and sleep for a shorter time if not ready to proceed.

Does that help? Or am I missing something?
    #4  
Old 01-22-2013
ksfolsom ksfolsom is offline
Registered User
 
Join Date: Dec 2012
Last Activity: 22 January 2013, 10:44 AM EST
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
I did exactly that but just dropped the sleep in rc.local and it works fine.
Sponsored Links
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
VMware View Client Connection Issues metallica1973 UNIX and Linux Applications 2 02-05-2013 12:17 PM
iscsi network share + xfs neutrino SuSE 0 02-04-2011 11:40 AM
How to change ethernet cable of iscsi initiator (iscsi client)? pankajd UNIX for Dummies Questions & Answers 0 05-24-2010 02:16 PM
[XFS] How to use real-time subvolume Cadi2108 UNIX for Advanced & Expert Users 3 02-26-2010 12:11 PM
Gfs2 vs xfs vs ext4 king_hippo Filesystems, Disks and Memory 12 11-30-2009 04:00 PM



All times are GMT -4. The time now is 11:32 PM.