topic Re: Problem with creating new file systems in Operating System - HP-UX

Problem with creating new file systems

Vipin Singhal — Wed, 07 Dec 2005 13:17:58 GMT

hi,
I have created new PV,VG,LV...
when I was creating file systems...
this is the error after creating two file systems:

# newfs -F vxfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_dat01
version 5 layout
26214400 sectors, 26214400 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles supported
26214400 data blocks, 26191352 free data blocks
800 allocation units of 32768 blocks, 32768 data blocks

# newfs -F vxfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_idx01
version 5 layout
10485760 sectors, 10485760 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles supported
10485760 data blocks, 10466672 free data blocks
320 allocation units of 32768 blocks, 32768 data blocks

# newfs -F vxfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_rbs01
version 5 layout
8388608 sectors, 8388608 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles supported
8388608 data blocks, 8370048 free data blocks
256 allocation units of 32768 blocks, 32768 data blocks
vxfs mkfs: read failure at block 8388607
vxfs mkfs: vxfs: I/O error

# newfs -F vxfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_rbs01
version 5 layout
8388608 sectors, 8388608 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles supported
8388608 data blocks, 8370048 free data blocks
256 allocation units of 32768 blocks, 32768 data blocks
vxfs mkfs: read failure at block 8388607
vxfs mkfs: vxfs: I/O error

# newfs -F vxfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_redoA
vxfs mkfs: read of lvm record failed

# newfs -F vxfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_redoA
vxfs mkfs: read of lvm record failed

Please suggest what to do?
Thanks
Vipin

Re: Problem with creating new file systems

Geoff Wild — Wed, 07 Dec 2005 13:22:04 GMT

Please post a vgdisplay -v /dev/vg75

Looks like you may have a bad disk...

Do lvdisplay -v /dev/vg75/rASPL_db_ORASPLD_data_rbs01 |more
to see which disks are in that lvol...and the others...then do a dd:

dd if=/dev/dsk/cXtXdX of=/dev/null

where cXtXdX is the device of the disk...

If that is okay - then the disk should be fine - if it fails - then the disk should be replaced...

Rgds...Geoff

Re: Problem with creating new file systems

Vipin Singhal — Wed, 07 Dec 2005 13:23:10 GMT

I tried with this one but still same problem:

# newfs -o largefiles /dev/vg75/rASPL_db_ORASPLD_data_rbs01
newfs: /etc/default/fs is used for determining the file system type
version 5 layout
8388608 sectors, 8388608 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles supported
8388608 data blocks, 8370048 free data blocks
256 allocation units of 32768 blocks, 32768 data blocks
vxfs mkfs: read failure at block 8388607
vxfs mkfs: vxfs: I/O error

# newfs -F vxfs /dev/vg75/rASPL_db_ORASPLD_data_redoA
vxfs mkfs: read of lvm record failed

Re: Problem with creating new file systems

Vipin Singhal — Wed, 07 Dec 2005 13:35:44 GMT

# vgdisplay -v /dev/vg75
VG Name /dev/vg75
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 9727
VGDA 6
PE Size (Mbytes) 4
Total PE 29178
Alloc PE 21504
Free PE 7674
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg75/ASPL_db_ORASPLD_data_dat01
LV Status available/syncd
LV Size (Mbytes) 25600
Current LE 6400
Allocated PE 6400
Used PV 1

LV Name /dev/vg75/ASPL_db_ORASPLD_data_idx01
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 2560
Allocated PE 2560
Used PV 1

LV Name /dev/vg75/ASPL_db_ORASPLD_data_rbs01
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 2048
Allocated PE 2048
Used PV 2

LV Name /dev/vg75/ASPL_db_ORASPLD_data_redoA
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 768
Allocated PE 768
Used PV 1

LV Name /dev/vg75/ASPL_db_ORASPLD_data_redoB
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 768
Allocated PE 768
Used PV 1

LV Name /dev/vg75/ASPL_db_ORASPLD_data_tmp01
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 2560
Allocated PE 2560
Used PV 1

LV Name /dev/vg75/ASPL_db_ORASPLD_archive
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 2560
Allocated PE 2560
Used PV 1

LV Name /dev/vg75/ASPL_db_ORASPLD_backup
LV Status available/syncd
LV Size (Mbytes) 15360
Current LE 3840
Allocated PE 3840
Used PV 2

--- Physical volumes ---
PV Name /dev/dsk/c23t4d1
PV Status available
Total PE 9726
Free PE 0
Autoswitch On

PV Name /dev/dsk/c26t4d3
PV Status unavailable
Total PE 9726
Free PE 0
Autoswitch On

PV Name /dev/dsk/c29t4d3
PV Status available
Total PE 9726
Free PE 7674
Autoswitch On

Re: Problem with creating new file systems

Vipin Singhal — Wed, 07 Dec 2005 13:41:14 GMT

#lvdisplay -v /dev/vg75/rASPL_db_ORASPLD_data_rbs01 |more

--- Logical volumes ---
LV Name /dev/vg75/ASPL_db_ORASPLD_data_rbs01
VG Name /dev/vg75
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 8192
Current LE 2048
Allocated PE 2048
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c23t4d1 766 766
/dev/dsk/c26t4d3 1282 1282

Re: Problem with creating new file systems

Geoff Wild — Wed, 07 Dec 2005 13:44:03 GMT

Okay - test those disks:

diskinfo /dev/rdsk/c23t4d1

diskinfo /dev/rdsk/c26t4d3

diskinfo /dev/rdsk/c29t4d3

Then dd:

dd if=/dev/dsk/c23t4d1 of=/dev/null

dd if=/dev/dsk/c26t4d3 of=/dev/null

dd if=/dev/dsk/c29t4d3 of=/dev/null

Rgds...Geoff

Re: Problem with creating new file systems

Vipin Singhal — Wed, 07 Dec 2005 14:00:14 GMT

# diskinfo /dev/rdsk/c23t4d1
SCSI describe of /dev/rdsk/c23t4d1:
vendor: DGC
product id: CX700WDR10
type: direct access
size: 39845888 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c26t4d3
SCSI describe of /dev/rdsk/c26t4d3:
vendor: DGC
product id: CX700WDR10
type: direct access
size: 39845888 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c29t4d3
SCSI describe of /dev/rdsk/c29t4d3:
vendor: DGC
product id: CX700WDR10
type: direct access
size: 39845888 Kbytes
bytes per sector: 512

when i am giving this command:
# dd if=/dev/dsk/c29t4d3 of=/dev/null
it is taking too much time...still in process..

Re: Problem with creating new file systems

Pete Randall — Wed, 07 Dec 2005 14:09:15 GMT

When you do your dd command, add a block size to it or it will take forever. It can still take quite a long time but without a blocksize it probably won't finish until tomorrow sometime.

# dd if=/dev/dsk/c29t4d3 of=/dev/null bs=1024k

Pete

Re: Problem with creating new file systems

Robert-Jan Goossens — Wed, 07 Dec 2005 14:12:52 GMT

Vipin,

Check this LUN on your san.

PV Name /dev/dsk/c26t4d3
PV Status unavailable
Total PE 9726
Free PE 0
Autoswitch On

Regards,
Robert-Jan

Re: Problem with creating new file systems

Vipin Singhal — Wed, 07 Dec 2005 14:23:33 GMT

Should i run these commands again now:

vgchange -a n vg75
vgexport vg75
mkdir /dev/vg75
mknod /dev/vg75/group c 64 0x2f0000
pvcreate -f /dev/rdsk/c23t4d1
pvcreate -f /dev/rdsk/c26t4d3
pvcreate -f /dev/rdsk/c29t4d3
vgcreate /dev/vg75 /dev/dsk/c23t4d1
vgextend /dev/vg75 /dev/dsk/c26t4d3 /dev/dsk/c29t4d3

then lvcreate and newfs......

Re: Problem with creating new file systems

Pete Randall — Wed, 07 Dec 2005 14:27:49 GMT

Unless you got errors when you ran those commands the first time, I really don't see any point to starting all over again. No harm, either, but let's see if somebody can't figure this out.

Pete

Re: Problem with creating new file systems

Steven E. Protter — Wed, 07 Dec 2005 14:40:41 GMT

Shalom Vipin,

I think you should run cstm/mstm/xstm and run excercize each drive involved.

You may have a problem with LUN configuration or the actual disks.

Its a good next step.

SEP