New disk shows 27% full

[Jason_309]

I had a disk fail and then replaced. The old disk only had some files that were not in use. When the new disk wa put in a bdf shows that it is 27% full?

[James R. Ferguson]

Hi Jason:

Well, assuming that the replaced filesystem(s) are the same sizes as those before the failure, how much change in utilization are you seeing?

Are you sure that you have restored all of your files?

What backup and restore utilities did you use? Did you optimize sparse files during an 'frecover'?

Regards!

...JRF...

[Jason_309]

The disks are the same size. I did not recover any data that was on the old disk. It was not needed.

[Jason_309]

when i run a #ff /dev/vg02/lvol4 i get the following


vxfs ff: file system on /dev/vg02/lvol4 has structural damage

[Steven E. Protter]

Shalom Jason,

Assuming you did not restore any files.

Is possible the disk was re-manufactured and had data on it. That is a serious no-no, but it would not be the first time I heard of it.

The LVM shows information on the disk because it has informaiton left over before the crash.

try removing logical volumes (that should be fun)

vgreduce the disk out of the volume group

pvcreate -f

rebuild your logical volumes with lvcreate

restore the data.

Personally I'd open a hardware case, validate they did in fact ship you a disk with data and have hp replace it.

SEP

[Jason_309]

Thank you for your quick responses. I will contact HP.

Will doing the vgreduce on that lvol effect anything else on the vg?

[Bill Hassell]

How did you replace the disk? Is this a mirrored system? There are specific steps to replace a bad disk, very different for mirrored verrsus unmirrored. DO not use vgreduce until you know how the disk is used in the volume group. Start with pvdisplay -v to see what extents are in use. Normally, mounted filesystems will crash if a disk is swapped on a non-mirrored volume group.

[Jason_309]

This disk is not mirrored.
The HP guy had me do a vgdisplay after he pulled it out and i got an error that said it could not locate the device,

then he put the new disk in and i verified it could be seen with a ioscan,

then he had me do a vgrestore to that disk
#vgrestore -n /dev/vg02 /dev/rdsk/c7t9do

Than a vgchange -a y dev/vg02

than a vgsync /dev/vg02

[Bill Hassell]

The vgsync command is only for mirrored disks. Now bdf does not show disks, it shows logical volumes that are on one or more physical disks. If the disk was not mirrored then your system would likely crash if the disk was pulled out and replaced without a shutdown. The vgcfgrestore put the volume definitions onto the new disk but nothing else. Now if you did a reboot after restoring this disk, then fstab would mount all the lvols. Is vg02 one large lvol with one filesystem? It would be incredibly difficult to find a replacement disk that had a usable directory that matched the old disk's definitions. Perhaps this disk is part of a a large lvol that spans multiple disks. It still isn't clear what you have in vg02. Post the results:

vgdisplay -v vg02
pvdisplay -v /dev/rdsk/c7t9do

[Jason_309]

# vgdisplay -v vg02
--- Volume groups ---
VG Name /dev/vg02
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 12
Act PV 12
Max PE per PV 17501
VGDA 24
PE Size (Mbytes) 4
Total PE 209988
Alloc PE 131072
Free PE 78916
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg02/lvol1
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol2
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol3
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol4
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol5
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol6
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol7
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1

LV Name /dev/vg02/lvol8
LV Status available/syncd
LV Size (Mbytes) 65536
Current LE 16384
Allocated PE 16384
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c5t0d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c5t1d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c5t2d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c5t3d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c5t4d0
PV Status available
Total PE 17499
Free PE 17499
Autoswitch On

PV Name /dev/dsk/c5t5d0
PV Status available
Total PE 17499
Free PE 17499
Autoswitch On

PV Name /dev/dsk/c7t8d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c7t9d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c7t10d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c7t11d0
PV Status available
Total PE 17499
Free PE 1115
Autoswitch On

PV Name /dev/dsk/c7t12d0
PV Status available
Total PE 17499
Free PE 17499
Autoswitch On

PV Name /dev/dsk/c7t13d0
PV Status available
Total PE 17499
Free PE 17499
Autoswitch On




# pvdisplay -v /dev/rdsk/c7t9d0
pvdisplay: Physical volume "/dev/rdsk/c7t9d0" is not a block special file.
Usage: pvdisplay
[-v]
[-b BlockList]
PhysicalVolumePath...

[Bill Hassell · Accepted solution]

The pvdisplay failed because it has the rdsk and not the dsk directory. That's OK, you can run it locally as it will be very lengthy:

pvdisplay -v /dev/dsk/c7t9d0

The vg02 volume has 12 physical disks with 8 logical volumes spread across those disks. The lvols are similar in size but there's no way to see which lvols are on the replaced disk without the pvdisplay output. It will tell which lvols were trashed by the replacement disk. Any lvol listed in the above pvdisplay command will have to be replaced. Now this is tricky, especially if production (useful) data exists on some of those lvols. A backup might work for an lvol that is only partially on the replaced disk, But all the lvols that are assigned to the replacement disk will need to be unmounted, have newfs run on them, then remounted and the data restored. This is the reason to use mirroring on all disks.

[Jason_309]

There is only one lvol on the replaced disk. It is /dev/vg02/lvol4.

[Bill Hassell]

Excellent. Apparently lvolw was laid out to match the physical disk. In that case, just umount that filesystem, run newfs on it and remount. It will now be empty.

[Jason_309]

Thank you. I will try this.

[Jason_309]

Bill this worked. Thank you very much..

[Jason_309]

Thanks for the help.