- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: determine status of vgmove
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО01-28-2013 11:45 AM
тАО01-28-2013 11:45 AM
determine status of vgmove
I am migrating to new storage (from older EVA to newer EVA) using vgmove. I have some fairly large filesystems to move (800GB). When moving the first one, the vgmove had been running for two days. It seemed "hung", so I killed the process. But when I checked, the vgmove appeared to have been successful. The new pv now had all the pe's and the old pv had 0 allocated pe's. I finished the job by "vgreduce'ing" and everything was fine. I am now vgmove'ing another vg to new storage. Is there a way to check on the status of the vgmove (without having to just let it run and kill it after two days)?
- Tags:
- vgmove
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-28-2013 11:51 PM
тАО01-28-2013 11:51 PM
Re: determine status of vgmove
Exactly how did you run the vgmove command? Did you run it in the background, e.g. by adding and "&" to the command line?
If you did that, the command would still be associated with the terminal session and if it attempted to output anything to the terminal, it would be held suspended until you used the "fg" command, so that it could present its output to you. This is how the standard shell job control works.
The vgmove command might have actually completed its job successfully and only hung because it could not output its "job complete" message at the very end.
You could avoid this by running the backgrounded command with the "nohup" prefix command, i.e. instead of running:
vgmove <parameters> &
you would run:
nohup vgmove <parameters> &
The "nohup" command achieves two things:
- it makes the command immune to SIGHUP, so you can leave the command running while logging out of your terminal session
- it redirects the command's standard input from /dev/null and standard output & error to a file named "nohup.out", so the command will not need to hang if it requests input or attempts to produce any output. Any output is also saved so that you can examine it later.
- Tags:
- nohup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2013 06:34 AM
тАО01-29-2013 06:34 AM
Re: determine status of vgmove
Thanks for that input, but I ran the vgmove in the "foreground"/interactively. The command I used was "vgmove -f diskmap.txt /dev/vgname". I didn't use "&" or "nohup".