We recently loaded UDB V8.1. We created an LVM using reiserfs as a single minidisk in
the server and a mount point of /opt/IBM/db2/V8.1:
/dev/vg6/lv1 1023964 300632 723332 30% /opt/IBM/db2/V8.1
We are hoping to use this as a single UDB reference in all our LINZ servers.
On a second server I defined a link to the first servers 107 disk RR.
,USER LZSD003T xxxxxx 512M 2020M G 64
, INCLUDE LINXDFLT
, LINK LZSS001A 0107 0107 RR
, MDISK 0100 3390 31 285 VLX049
, MDISK 0101 3390 2270 1290 VLX056
, MDISK 0102 3390 4441 430 VLX057
, MDISK 0103 3390 6719 290 VLX059
, MDISK 0104 3390 9116 800 VLX05B
, MDISK 0105 3390 7537 500 VLX05C
, MDISK 0191 3390 3461 30 VLX047
When we start the second server he sees the LV and recognizes it but when we mount it
we get the following errors:
lzsd003t:~ # mount /dev/vg6/lv1 /opt/IBM/db2/V8.1
mount: block device /dev/vg6/lv1 is write-protected, mounting read-only
mount: you must specify the filesystem type
lzsd003t:~ # mount /dev/vg6/lv1 /opt/IBM/db2/V8.1 -t reiserfs
mount: block device /dev/vg6/lv1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/vg6/lv1,
or too many mounted file systems
My mesages file says the following:
Feb 5 17:32:09 lzsd003t kernel: reiserfs: checking transaction log (device 3a:04) ...
Feb 5 17:32:09 lzsd003t kernel: clm-2076: device is readonly, unable to replay log
Feb 5 17:32:09 lzsd003t kernel: Replay Failure, unable to mount
Feb 5 17:32:09 lzsd003t kernel: reiserfs_read_super: unable to initialize journal
space
Feb 5 17:33:47 lzsd003t kernel: reiserfs: checking transaction log (device 3a:04) ...
Feb 5 17:33:47 lzsd003t kernel: clm-2076: device is readonly, unable to replay log
Feb 5 17:33:47 lzsd003t kernel: Replay Failure, unable to mount
Feb 5 17:33:47 lzsd003t kernel: reiserfs_read_super: unable to initialize journal
space
Is this something I should be able to do or am I barking up the wrong tree.
I would hate to have to install UDB on every instance.
Thanks for any help.
