02-28-2006
thank you for your responses.
So i understand better: the new physical volumes should be at the end of the file system, and the heads must move from the beginning to the end.
Effectively the data are already saved, but there is always the risk of a corrupted backup... Or perhaps if I install 1To more, i move the file system to the new, i verify that all is right and I delete the old file system.
The file system is jfs2, and i have verified, i can extend it
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
1 . Thanks everyone who read the post first.
2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too.
How to view it ?
If I want to view 200-300 ,how can I implement it
3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am quite sure that I am posting a question in the very wrong forum but I have to give a try. It's a question about UNIX theory. I don't have any clue of how to solve this question. If someone could kindly provide some good references or give me the formulas, it will be really... (1 Reply)
Discussion started by: ti_ma
1 Replies
3. UNIX for Dummies Questions & Answers
The /src file is obviously designed to contain source code, so when I download programs, I should put them in /src (because they contain the source files + the executables)? What do most people do with the executables? Do they copy them to /bin, make links to them in /bin, or just leave them in... (4 Replies)
Discussion started by: css136
4 Replies
4. UNIX for Dummies Questions & Answers
I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies
5. Shell Programming and Scripting
Input file
DATA2.2 POSITION_152486.2 COLUMN689699.2
DATA2.2 ROW00000342066 UNIT00000342313
DATA7.2 POSITION_017891.4 COLUMN060361.4
DATA7.2 ROW00000379319 UNIT00000368623
DATA7.2 ROW00000421241 UNIT00000400736
DATA8.1 POSITION_153254.2 COLUMN694986.2
DATA8.1 ROW00000379288... (1 Reply)
Discussion started by: perl_beginner
1 Replies
6. UNIX for Dummies Questions & Answers
Does anyone have any idea of how I can make something like the code below run recursively?
I'll run it on a tree of directories all with different names and all containing a sequence of .dpx files. I've tried to do it using find and exec but can't get it to work right.
What it needs to do is... (4 Replies)
Discussion started by: scribling
4 Replies
7. What is on Your Mind?
Hello,
I have been working as Solaris/Linux Admin since past 8 years. I am looking options for my profile change, but there is some limitation. I worked as 24x7 support for admin, server support, high availability, etc. But been worked on developing side and scripting part.
When I search for Big... (2 Replies)
Discussion started by: nightup2222
2 Replies
8. Solaris
Gents
Actually I have question and i need your support.
I have this NAS file system mounted as /coresys has size of 7 TB
I need to Split this file system into several file systems as mount points I mean how to can I Split it professionally to different NAS mount points how to can I decide... (2 Replies)
Discussion started by: AbuAliiiiiiiiii
2 Replies
LEARN ABOUT HPUX
vgremove
vgremove(1M) vgremove(1M)
NAME
vgremove - remove LVM volume group definition from the system
SYNOPSIS
vg_name ...
Remarks
If a combination of volume groups version 1.0 and 2.0 or higher arguments are supplied, then the arguments might not be processed in the
order they are listed on the command line.
DESCRIPTION
The command removes from the system the last physical volume of the volume group and the definition of the volume group or groups specified
by vg_name .... Since all system knowledge of the volume group and its contents are removed, the volume group can no longer be accessed.
To move a volume group from one system to another, use the command instead (see vgexport(1M)).
Before executing remove all logical volumes residing on the last physical volume by executing (see lvremove(1M)).
Before removing a volume group, two steps are necessary:
1. Remove all the logical volumes belonging to the group by using the command (see lvremove(1M)).
2. Remove all but one physical volume belonging to the volume group by using the command (see vgreduce(1M)).
If there is any physical volume group created under vg_name ..., the physical volume group information is also removed from file
Options and Arguments
recognizes the following option and argument:
For each volume group removed, also
remove its volume group directory and file
vg_name The path name of a volume group.
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)).
EXAMPLES
Remove volume group from the system:
SEE ALSO
lvremove(1M), vgchange(1M), vgreduce(1M).
vgremove(1M)