Hello,

I am rather new to Linux, but know enough to get most things done. However, I have a problem I don't know how to do.

I need to know how to mount a file system containing data. Rather a BCV SAN LUN. or Business Continuity Volume used for Disaster Recovery. Such as the primary R1 LUN is replicated to the secondary R2 LUN, this is done via SRDF/A - then a DR occurs and a sync-split is performed and a BCV LUN containing the time sync image of the R2 LUN is created to be presented to the DR server. The DR server OS is RedHat Linux on Power, equivelant RedHat Linux for IBM p-series platform.

I know how to create a file system from an empty SAN LUNs but the BCV I cannot seem to mount successfully or view what is on it after I mount it.
What I have done, which I don't think is correct.

fdisk -l
pvcreate /dev/sdb /dev/sdc
vgcreate EMCdata /dev/sdb
vgextend EMCdata /dev/sdc
lvcreate –l 100%VG –n lvOracle EMCdata
mke2fs -j /dev/EMCdata/lvOracle
mkdir /oracle
edit /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/md2 / ext3 defaults 1 1
/dev/md0 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/md1 swap swap defaults 0 0
/dev/EMCdata/lvOracle /oracle ext3 defaults 0 2
mount -all


when I do this, there is no data on the file system. there is data on it, or being replicated and the BCV is sync-split.

thanks so much in advance. I don't know what to do?

Well, silly me.
knowing the BCV is the cloned R2 image of a replicated file system, it is presented already as an etc3 file system, under LVM, with physical volume, volume groups, logical volumes already defined and declared. it is as simple as updating the /etc/fstab with the logical volumes and mount points and mounting the file systems. for instance.
[root@ASPIBMDR1B oracle]# fdisk -l

Disk /dev/sda: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1 8001 41 PPC PReP Boot
/dev/sda2 2 14 104422+ 83 Linux
/dev/sda3 15 13054 104743800 8e Linux LVM

Disk /dev/sdb: 72.4 GB, 72406794240 bytes
255 heads, 63 sectors/track, 8802 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 36.2 GB, 36203397120 bytes
64 heads, 32 sectors/track, 34526 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/dm-2: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-2 doesn't contain a valid partition table

My BCV disks listed above.
[root@ASPIBMDR1B oracle]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
100986280 7621976 88234476 8% /
/dev/sda2 101105 14103 81781 15% /boot
none 6148356 0 6148356 0% /dev/shm

all's good...
[root@ASPIBMDR1B oracle]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 VolGroup00 lvm2 a- 99.88G 96.00M
/dev/sdb EMCData lvm2 a- 67.43G 0
/dev/sdc EMCData lvm2 a- 33.71G 1.15G
[root@ASPIBMDR1B oracle]# pvscan
PV /dev/sdb VG EMCData lvm2 [67.43 GB / 0 free]
PV /dev/sdc VG EMCData lvm2 [33.71 GB / 1.15 GB free]
PV /dev/sda3 VG VolGroup00 lvm2 [99.88 GB / 96.00 MB free]
Total: 3 [201.02 GB] / in use: 3 [201.02 GB] / in no VG: 0 [0 ]
[root@ASPIBMDR1B oracle]# pvdisplay
--- Physical volume ---
PV Name /dev/sdb
VG Name EMCData
PV Size 67.43 GB / not usable 512.00 KB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 17263
Free PE 0
Allocated PE 17263
PV UUID 53lDWK-8Fte-rpo3-L4kH-nRRH-2eX7-e5kK8X

--- Physical volume ---
PV Name /dev/sdc
VG Name EMCData
PV Size 33.72 GB / not usable 2.25 MB
Allocatable yes
PE Size (KByte) 4096
Total PE 8631
Free PE 294
Allocated PE 8337
PV UUID 6cNiSj-jPSC-fqCf-RmoS-pglG-aYSa-AHiPZD

--- Physical volume ---
PV Name /dev/sda3
VG Name VolGroup00
PV Size 99.89 GB / not usable 16.87 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 3196
Free PE 3
Allocated PE 3193
PV UUID YUFIwj-rMCS-WLBl-o7VU-S4e0-Itp2-xOWfF7

[root@ASPIBMDR1B oracle]# vgs
VG #PV #LV #SN Attr VSize VFree
EMCData 2 2 0 wz--n- 101.15G 1.15G
VolGroup00 1 2 0 wz--n- 99.88G 96.00M
[root@ASPIBMDR1B oracle]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "EMCData" using metadata type lvm2
Found volume group "VolGroup00" using metadata type lvm2
[root@ASPIBMDR1B oracle]# vgdisplay
--- Volume group ---
VG Name EMCData
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 2
Act PV 2
VG Size 101.15 GB
PE Size 4.00 MB
Total PE 25894
Alloc PE / Size 25600 / 100.00 GB
Free PE / Size 294 / 1.15 GB
VG UUID aEZXKp-dcgW-JtMn-gxvP-iiGz-o8zY-f9OAes

--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 99.88 GB
PE Size 32.00 MB
Total PE 3196
Alloc PE / Size 3193 / 99.78 GB
Free PE / Size 3 / 96.00 MB
VG UUID 9dSrlh-Pmmf-zP2W-aLqE-to2A-vHx1-pRbdXR
-----
[root@ASPIBMDR1B oracle]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
lvOracle EMCData -wi-ao 70.00G
lvUser EMCData -wi-ao 30.00G
LogVol00 VolGroup00 -wi-ao 97.84G
LogVol01 VolGroup00 -wi-ao 1.94G
[root@ASPIBMDR1B oracle]# lvscan
ACTIVE '/dev/EMCData/lvUser' [30.00 GB] inherit
ACTIVE '/dev/EMCData/lvOracle' [70.00 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol00' [97.84 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
[root@ASPIBMDR1B oracle]# lvdisplay
--- Logical volume ---
LV Name /dev/EMCData/lvUser
VG Name EMCData
LV UUID ChhRBw-Pp8k-ZOcf-f0mb-Knbg-emIw-OAPqh9
LV Write Access read/write
LV Status available
# open 1
LV Size 30.00 GB
Current LE 7680
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:2

--- Logical volume ---
LV Name /dev/EMCData/lvOracle
VG Name EMCData
LV UUID 7a2Ice-iuWB-uw9o-37uQ-dOjm-ouQ3-22Mgev
LV Write Access read/write
LV Status available
# open 1
LV Size 70.00 GB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors 0
Block device 253:3

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID dXHPUM-1p46-AbRD-wmy8-Oq8Y-qcOk-i3DPd1
LV Write Access read/write
LV Status available
# open 1
LV Size 97.84 GB
Current LE 3131
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID hVV1TC-7r9B-sIF6-0SBL-2sXh-7jmP-DR9g4d
LV Write Access read/write
LV Status available
# open 1
LV Size 1.94 GB
Current LE 62
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:1

AS CAN BE SEEN FROM ABOVE - THE LVM ALREADY HAS KNOWLEDGE OF THE FILESYSTEM ON THE PRESENTED DISKS.

SO I JUST ADDED to the FSTAB file
[root@ASPIBMDR1B /]# cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/EMCData/lvOracle /oracle ext3 defaults 1 2
/dev/EMCData/lvUser /user ext3 defaults 1 2

and performed a
mount -all
[root@ASPIBMDR1B /]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
100986280 7621976 88234476 8% /
/dev/sda2 101105 14103 81781 15% /boot
none 6148356 0 6148356 0% /dev/shm
/dev/mapper/EMCData-lvOracle
72248648 59387556 9191076 87% /oracle
/dev/mapper/EMCData-lvUser
30963708 115764 29275080 1% /user

WALA LIKE MAGIC...
[root@ASPIBMDR1B /]# cd /oracle
[root@ASPIBMDR1B oracle]# ls
10201_database_lin_ppc.cpio.gz BNYMETF0 dba HTF00000 p4767801 TD000000
10g BOIS0000 display_sequences.ksh lost+found p5337014 tmp
admin bport display_sequences.sql MBMUAT00 PRC00000 TOM08030
AMEXPROD CAPI0000 download MTPUAT00 SCRIPTS UNICAT80
arch check_sequences.ksh flash_recovery_area oradata SEIUK000 UNICAT8X
BBAY0000 CS000000 GAM00000 oraInventory SEIUS000 UNICATS0

WHEN DR IS DONE YOU MUST UNMOUNT THE SYSTEMS AND POSSIBLY COMMENT OUT THE FSTAB ENTRIES.. So when a shutdown and boot take place the mounting filesystems will not get confused...

Thanks - I feel so silly - it is so simple - not like Veritas or other software products. I should have known this , oh well - life's a learning experience.

I hope this will help someone that may have the same questions and have seen the whole import /export procedure under other systems. that's where my confusion came in.