I have just purchased a new server running RHELS R6 from a well known supplier. The OS came pre-installed so I (as a previous almost identical server) just finished off the install. I have just been extending one of the partitions and noticed an overlap.
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 4.0G 342M 3.5G 9% /
tmpfs 24G 88K 24G 1% /dev/shm
/dev/sda3 194M 30M 155M 17% /boot
/dev/mapper/VolGroup00-LogVol03 3.0G 69M 2.8G 3% /tmp
/dev/mapper/VolGroup00-LogVol02 6.0G 1.9G 3.8G 34% /usr
/dev/mapper/VolGroup00-LogVol04 7.9G 3.5G 4.1G 47% /var
/dev/mapper/VolGroup00-LogVol05 1.1T 143M 1.1T 1% /home
--- Physical volume ---
PV Name /dev/sda5
VG Name VolGroup00
PV Size 1.36 TiB / not usable 31.00 MiB
Allocatable yes
PE Size 32.00 MiB
Total PE 44493
Free PE 6533
Allocated PE 37960
PV UUID tAcWCr-RqFc-PqKu-Ij4I-clZE-ny13-W5y5KU
On doing an FDISK...
Code:
Disk /dev/sda: 1498.7 GB, 1498675150848 bytes
255 heads, 63 sectors/track, 182203 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa0000000
Device Boot Start End Blocks Id System
/dev/sda1 1 15 120456 de **** Utility
/dev/sda2 16 668 5245222+ 83 Linux
/dev/sda3 * 669 694 204800 83 LinuxPartition 3 does not end on cylinder boundary.
/dev/sda4 694 182204 1457979392 5 Extended
/dev/sda5 694 182204 1457978368 8e Linux LVM
I was about to commission this My experience is Solaris but looking at the make up here I believe the only way to correct this will be to rebuild because /tmp. /usr, /var and root are all on Volume Group 00?
Cheers.
It isn't an overlap. The default fdisk behaviour is to have partitions end on the cylinder boundary (a pretty old concept), while newer versions can have it end at any sector boundary. Try this, enter fdisk (not just fdisk -l), hit u to change the units displayed, and then p to print the partition table. If you still see an overlap, there's really something wrong.
Example from one of my machines:
Code:
Command (m for help): p
Disk /dev/sda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x975a2ea3
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 10012 80314816 8e Linux LVM
Partition 2 does not end on cylinder boundary.
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders, total 160836480 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x975a2ea3
Device Boot Start End Blocks Id System
/dev/sda1 2048 206847 102400 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 206848 160836479 80314816 8e Linux LVM
Partition 2 does not end on cylinder boundary.
Command (m for help):
I can't help but wonder if this wasn't imaged with some ghostlike tool and the hardware was ever so slightly different than between image/target...
Doesn't matter anymore for the same reason disks don't have cylinders anymore: Everything's LBA. As far as the disk bus is concerned, you have sector 0, 1, .... 160836479 all in a row with no deeper organization, the drive handles head positioning for you. Which makes copying one drive to another a piece of cake as long as the destination's equal to or larger in size.
These 2 Users Gave Thanks to Corona688 For This Post:
It isn't an overlap. The default fdisk behaviour is to have partitions end on the cylinder boundary (a pretty old concept), while newer versions can have it end at any sector boundary. Try this, enter fdisk (not just fdisk -l), hit u to change the units displayed, and then p to print the partition table. If you still see an overlap, there's really something wrong.
I am educated
Code:
Disk /dev/sda: 1498.7 GB, 1498675150848 bytes
255 heads, 63 sectors/track, 182203 cylinders, total 2927099904 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa0000000
Device Boot Start End Blocks Id System
/dev/sda1 63 240974 120456 de ****Utility
/dev/sda2 240975 10731419 5245222+ 83 Linux
/dev/sda3 * 10731520 11141119 204800 83 Linux
Partition 3 does not end on cylinder boundary.
/dev/sda4 11141120 2927099903 1457979392 5 Extended
/dev/sda5 11143168 2927099903 1457978368 8e Linux LVM
Command (m for help):
Doesn't matter anymore for the same reason disks don't have cylinders anymore: Everything's LBA. As far as the disk bus is concerned, you have sector 0, 1, .... 160836479 all in a row with no deeper organization, the drive handles head positioning for you. Which makes copying one drive to another a piece of cake as long as the destination's equal to or larger in size.
I was implying the target was smaller, I should have made that clear.
Hi Help,
I am trying to find a overlap zone by compraing th etwo files which is printed below.
File-1 is ---
1011 234
2967 787
235 900
435 654
File 2 is ---
1211 456
595 678
546 678
2967 787
I would like to have a o/p which just read 2967 787,'comm' doesn't seem to do the... (5 Replies)
Hello All,
I have a Red Hat Linux 5.9 Server installed with one hard disk & 2 Partitions created on it as follows,
/boot - Linux Partition & another is
LVM - One VG & under that 5-6 Logical volumes(var,opt,home etc).
Here my requirement is to take out 1GB of space from LVM ( Any logical... (5 Replies)
Hi,
I want to overlap two files based on two columns in each files. Here I'm overlapping the first two columns of the first file with columns 3 &4 of the second file (Bolded) to get the common lines.
File1
ESR1 1 15 ggtga
ESR1 7 18 tgcagt
FOXA1 3 10 gtgat
FOXA1 10 20 tgacc
File2... (1 Reply)
Hi all,
New to this forum as well as the world of Veritas Volume Manager. My client is using VxVM 3.2. We just changed one of the disk which is under veritas control. I used the appropriate options in vxdiskadm to replace this failed disk. Now when I am trying to unrelocate subdisks back to the... (0 Replies)
Based on input1 specific key (column1, 4 and 5) take the values (column 2 and 3) overlap with input2. And Specify names based on output.
input1
a1 100 200 E1 ABC
a1 300 400 E2 ABC
a1 500 600 E3 ABC
a2 100 200 E1 CDE
a2 300 400 E2 ... (2 Replies)
for every specific $1,$2 check the values ($2,$3) of their E ot I of input1 and overlap with input2.
Specify names based on output.
#######
if middle value is missing name them "SE"
if first value is missing name them "AFE"
if last value is missing name them "ALE"
if 2 middle values are... (1 Reply)
Hello
I've got a script that creates multiple processes, in ksh, to bcp out 6 tables at a time. In the script, we write messages to the log to show our progress; most of the time, the log messages are nice and neat with one per line, like they should be. But every once in awhile, at random, the... (2 Replies)
Hi everyone,
I posted this earlier, but the idea changed since then and I figured it would make more sense if I repost with a clearer idea in hopes someone can help me out.
I have two lists of data in file1 and file 2
file1 (tab separated - column1 column2 column 3)
1 91625106 ... (1 Reply)
I've created a partition with GNU Parted, how do I mount the partition?
The manual information at http://www.gnu.org/software/parted/manual/parted.html is good, but I am sure about how I mount the partition afterwards.
Thanks,
--Todd (1 Reply)
08-31-2011
My experience is Solaris but looking at the make up here I believe the only way to correct this will be to rebuild because /tmp. /usr, /var and root are all on Volume Group 00?
