HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Legacy
- >
- Storage Software
- >
- WAIT Problem in SSSU
Storage Software
1829023
Members
2782
Online
109986
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2009 02:40 AM
02-26-2009 02:40 AM
WAIT Problem in SSSU
Hi,
I have the following script for sssu to create a container and then create and present a snapclone to a host. The commands and the script work fine, if the command arguments are executed singularly, but if run in sequence produce an error regarding the fact that the container is not yet big enough for the snap to take place.
I dont seem to be able to use WAIT_FOR_COMPLETION in the line which creates the container (should I be able to use this as a valid argument?)
Also I have tried to use the SET OPTION COMMAND_DELAY=10, but this doesnt seem to have a positive impact either.
please take a look and share your opinion on my best way forward
thanks
I have the following script for sssu to create a container and then create and present a snapclone to a host. The commands and the script work fine, if the command arguments are executed singularly, but if run in sequence produce an error regarding the fact that the container is not yet big enough for the snap to take place.
I dont seem to be able to use WAIT_FOR_COMPLETION in the line which creates the container (should I be able to use this as a valid argument?)
Also I have tried to use the SET OPTION COMMAND_DELAY=10, but this doesnt seem to have a positive impact either.
please take a look and share your opinion on my best way forward
thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2009 09:13 AM
02-27-2009 09:13 AM
Re: WAIT Problem in SSSU
Normally, creating the container with the Add Container command is a One Time thing. The whole idea of containers is being able to reserve disk group storage to reduce or eliminate disk group leveling. It *is* a little odd that there is no WAIT option for the Add Container command. As it stands, you will need to have two separate SSSU sessions, the first to create the container, and once it is done, a second to create the snapclone and present the LUN. I would assume, going forward, that when you are ready, you would convert the snapclone vdisk back into its container form, and then redo the second part and re-snap the clone.
You could have a third session that would LS "\Virtual Disks\hostgroup\host\host_cont" FULL XML, and then parse the output from SSSU to determine if the container is ready. If not, wait a minute or two, and check again.
Secondly, you can put most (all?) of the SSSU commands into a single text file and then simply
/usr/local/src/sssu_sles9_x86 "FILE sssu-commands.txt"
or, any combination of that and passing arguments in from the bash shell.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
You could have a third session that would LS "\Virtual Disks\hostgroup\host\host_cont" FULL XML, and then parse the output from SSSU to determine if the container is ready. If not, wait a minute or two, and check again.
Secondly, you can put most (all?) of the SSSU commands into a single text file and then simply
/usr/local/src/sssu_sles9_x86 "FILE sssu-commands.txt"
or, any combination of that and passing arguments in from the bash shell.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP