Thanks Peter.
Just two more questions please:
1. Free Hog partition[6]?
Should I select this as a partition from which I am taking away space, that is
s5
2. If I adjust s4 (increase) and s5 (decrease) partition size, then Enter table
name to save it, then I have to Label the disk to load this modified partition
table. But, If I label will it deletes data from all partitions or just the one
which I am adjusting, that is s4 and s5? I want to keep other partition
untouched, except s4 and s5.
Without labeling the disk, it wouldn't load s4 and s5 partition change, right?
But then it may deletes data from other partition.
Screen capture:
Specify disk (enter its number): 0
selecting c1t0d0: loan01
[disk formatted]
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> part
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> print
Volume: loan01
Current partition table (original):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 1417 1.95GB (1418/0/0) 4096602
1 swap wu 1418 - 7225 8.00GB (5808/0/0) 16779312
2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 7226 - 7296 100.16MB (71/0/0) 205119
4 unassigned wm 7297 - 8714 1.95GB (1418/0/0) 4096602
5 unassigned wm 8715 - 21074 17.03GB (12360/0/0) 35708040
6 usr wm 21075 - 22492 1.95GB (1418/0/0) 4096602
7 unassigned wm 22493 - 24619 2.93GB (2127/0/0) 6144903
partition> mod
Select partitioning base:
0. Current partition table (original)
1. All Free Hog
Choose base (enter number) [0]?
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 1417 1.95GB (1418/0/0) 4096602
1 swap wu 1418 - 7225 8.00GB (5808/0/0) 16779312
2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 7226 - 7296 100.16MB (71/0/0) 205119
4 unassigned wm 7297 - 8714 1.95GB (1418/0/0) 4096602
5 unassigned wm 8715 - 21074 17.03GB (12360/0/0) 35708040
6 usr wm 21075 - 22492 1.95GB (1418/0/0) 4096602
7 unassigned wm 22493 - 24619 2.93GB (2127/0/0) 6144903
Do you wish to continue creating a new partition
table based on above table[yes]?
Free Hog partition[6]?
Enter size of partition '0' [4096602b, 1418c, 2000.29mb, 1.95gb]: 4096602b
Enter size of partition '1' [16779312b, 5808c, 8193.02mb, 8.00gb]: 16779312b
Enter size of partition '3' [205119b, 71c, 100.16mb, 0.10gb]: 205119b
Enter size of partition '4' [4096602b, 1418c, 2000.29mb, 1.95gb]: 8193204b
Enter size of partition '5' [35708040b, 12360c, 17435.57mb, 17.03gb]: 31611438b
Enter size of partition '7' [6144903b, 2127c, 3000.44mb, 2.93gb]: 6144903b
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 1417 1.95GB (1418/0/0) 4096602
1 swap wu 1418 - 7225 8.00GB (5808/0/0) 16779312
2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 7226 - 7296 100.16MB (71/0/0) 205119
4 unassigned wm 7297 - 10132 3.91GB (2836/0/0) 8193204
5 unassigned wm 10133 - 21074 15.07GB (10942/0/0) 31611438
6 usr wm 21075 - 22492 1.95GB (1418/0/0) 4096602
7 unassigned wm 22493 - 24619 2.93GB (2127/0/0) 6144903
Okay to make this the current partition table[yes]? y
Enter table name (remember quotes): mod_logs_part
Ready to label disk, continue? y
partition> part
`part' is not expected.
partition> ?
Expecting one of the following: (abbreviations ok):
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> print
Volume: loan01
Current partition table (mod_logs_part):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 1417 1.95GB (1418/0/0) 4096602
1 swap wu 1418 - 7225 8.00GB (5808/0/0) 16779312
2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 7226 - 7296 100.16MB (71/0/0) 205119
4 unassigned wm 7297 - 10132 3.91GB (2836/0/0) 8193204
5 unassigned wm 10133 - 21074 15.07GB (10942/0/0) 31611438
6 usr wm 21075 - 22492 1.95GB (1418/0/0) 4096602
7 unassigned wm 22493 - 24619 2.93GB (2127/0/0) 6144903
partition>
Regards,
Pravin
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Kirkov
Sent: Monday, December 27, 2004 2:03 AM
To: Solaris-Users mailing list
Subject: Re[4]: [Solaris-Users] RE: expand a disk slice by taking
somespacefrom the unused slice
Hello Pravin,
Friday, December 24, 2004, 11:01:19 AM, you wrote:
[cut]
>> bring the system to single user mode, so no one is using and noone is
>> logging: init S
PPKGH> 1. As long as all applications that uses /logs been
PPKGH> stopped, is it still necessary to run this procedure in single
PPKGH> user mode? The reason I am asking is, I will test this
PPKGH> procedure in the Lab first and then I need to apply it to the
PPKGH> Customer site remotely.
Probably you don't need to bring system to single user mode in that case.
But it's always a good idea to do such operations in Single user.
>> Now you have to grow the FSes format, then edit slice table and
>> enlarge s4 on both drives ( c1t0d0s4 and c1t1d0s4 ) after that
>> growfs both FSes.
PPKGH> 2. Here I will be enlarging s4 at the cost of reducing
PPKGH> s5, which is fine since it is unused. After updating the
PPKGH> partition table for s4 and s5, should I need to run growfs as
PPKGH> follows (note that df -k output for /logs is: /dev/md/dsk/d4
PPKGH> 1983119 29304 1894322 2% /logs)
PPKGH> growfs -M /logs /dev/rdsk/d4
PPKGH> growfs -M /logs /dev/dsk/d4
PPKGH> What exactly FSes meant for?
FSes= FileSystems , sorry that I don't explained it.
At this stage you do not have metadevice /dev/dsk/d4 defined, so
commands like these will not work.
Growfs should be:
growfs /dev/rdsk/c0t0d0s4
growfs /dev/rdsk/c0t1d0s4
As you are expanding the two slices that later will become submirrors
of your mirror.
PPKGH> Happy Holidays!
Happy Holidays to you too!
PPKGH> Regards,
PPKGH> Pravin
--
Peter Kirkov
Support Engineer
________________________________________________
ACT Sofia
Tzarigradsko shosse blvd. 7km
BIC-IZOT, Office 710-714 Tel: +359-2-9718354
1113 Sofia - Bulgaria Fax: +359-2-9718343
mobile: +359-889-919638
mailto:[EMAIL PROTECTED]
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users
