de inicializacao, timeout e outras. [root@node1]# service o2cb configureConfiguring the O2CB driver.This will configure the on-boot properties of the O2CB driver.The following questions will determine whether the driver is loaded onboot. The current values will be shown in brackets ('[]'). Hitting<ENTER> without typing an answer will keep that current value. Ctrl-Cwill abort. Load O2CB driver on boot (y/n) [n]: yCluster stack backing O2CB [o2cb]:Cluster to start on boot (Enter "none" to clear) [ocfs2]:Specify heartbeat dead threshold (>=7) [31]:Specify network idle timeout in ms (>=5000) [30000]:Specify network keepalive delay in ms (>=1000) [2000]:Specify network reconnect delay in ms (>=2000) [2000]:Writing O2CB configuration: OKLoading filesystem "configfs": OKMounting configfs filesystem at /sys/kernel/config: OKLoading stack plugin "o2cb": OKLoading filesystem "ocfs2_dlmfs": OKCreating directory '/dlm': OKMounting ocfs2_dlmfs filesystem at /dlm: OKSetting cluster stack "o2cb": OKRegistering O2CB cluster "ocfs2": OKSetting O2CB cluster timeouts : OK Para verificar o status do ovfs2 execute o comando abaixo: [root@SER018020121 ~]# service o2cb statusDriver for "configfs": LoadedFilesystem "configfs": MountedStack glue driver: LoadedStack plugin "o2cb": LoadedDriver for "ocfs2_dlmfs": LoadedFilesystem "ocfs2_dlmfs": MountedChecking O2CB cluster "ocfs2": Online Heartbeat dead threshold: 31 Network idle timeout: 30000 Network keepalive delay: 2000 Network reconnect delay: 2000 Heartbeat mode: LocalChecking O2CB heartbeat: Not active Para configurar o servico do ocfs2 no boot: # chkconfig o2cb on# chkconfig ocfs2 on Esses parametros de kernel devem ser alterados: # sysctl kernel.panic = 30# sysctl kernel.panic_on_oops = 1 Certo ate aqui o ocfs ja esta pronto para ser usado, vamos as LUNs agora, crie as particoes nas luns com fdisk caso nao esteja familiarizado com o fdisk veja o seguinte artigo Depois formate as novas particoes em um no para ocfs2 : mkfs.ocfs2 -b 4K -C 128K -N 4 -L database /dev/... [root@node1]# mkfs.ocfs2 -b 4K -C 128K -N 4 -L database /dev/emcpowerv1mkfs.ocfs2 1.8.0Cluster stack: classic o2cbLabel: databaseFeatures: sparse extended-slotmap backup-super unwritten inline-data strict-journal-super xattr indexed-dirs refcount discontig-bgBlock size: 4096 (12 bits)Cluster size: 131072 (17 bits)Volume size: 327604502528 (2499424 clusters) (79981568 blocks)Cluster groups: 78 (tail covers 15712 clusters, rest cover 32256 clusters)Extent allocator size: 83886080 (20 groups)Journal size: 268435456Node slots: 4Creating bitmaps: doneInitializing superblock: doneWriting system files: doneWriting superblock: doneWriting backup superblock: 5 block(s)Formatting Journals: doneGrowing extent allocator: doneFormatting slot map: doneFormatting quota files: doneWriting lost+found: donemkfs.ocfs2 successful Com particao formatada vamos agora criar os pontos de montagem(em todos os nos participantes do ocfs2) mkdir -p /u02/ Vamos agora montar o disco com as luns formatadas(em todos os nos ): [root@node1]# mount -t ocfs2 /dev/emcpowerv1 -o datavolume /u02/[root@node2]# mount -t ocfs2 /dev/emcpowerv1 -o datavolume /u02/ Vamos verificar se deu certo: [root@node1]# df h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 208G 82G 116G 42% //dev/sda1 99M 23M 71M 25% /boottmpfs 7.9G 277M 7.6G 4% /dev/shm/dev/emcpowerv1 306G 1.9G 304G 1% /u02 Beleza deu certo, agora executamos o partprobe nos demais nos para que as informacoes de particao sejam atualizadas Agora para que no proximo boot os diretorios sejam montados automaticamente vamos editar o arquivo de particoes do linux o fstab , adicione a seguinte entrada no fstab em todos os nos: /dev/emcpowerv1 /u02/ ocfs2 _netdev,datavolume,nointr 0 0 Pronto, seu ocfs2 esta pronto para