1. The scenario
On my box I’ve two disks from two differents Storage Disk.
Using multipath I’ve this disks
/dev/dm-15 from Storage Disk A (in use)
/dev/dm-28 from Storage Disk B (not in use yet.)
I’ve the Volume Group with name vg_gfs00 on /dev/dm-15
I’ve the Logical Volume with name lv00 on the Volume Group VG_GFS
Looking my outputs pvs, vgs and lvs
PVS output
# pvs
PV VG Fmt Attr PSize PFree
/dev/dm-15 vg_gfs00 lvm2 a- 278,98G 39,95G
/dev/sda3 rootvg lvm2 a- 131,47G 86,19G
VGS output
# vgs
VG #PV #LV #SN Attr VSize VFree
rootvg 1 11 0 wz--n- 131,47G 86,19G
vg_gfs00all 8 7 0 wz--n- 278,98G 39,95G
LVS output
# lvs
LV VG Attr LSize
homelv rootvg -wi-ao 512,00M
optlv rootvg -wi-ao 1,00G
rootlv rootvg -wi-ao 1,00G
tmplv rootvg -wi-ao 2,00G
usrlv rootvg -wi-ao 4,00G
varloglv rootvg -wi-ao 8,00G
varlv rootvg -wi-ao 4,00G
lv00 vg_gfs00 -wi-ao 239,03G
2. Objective
Implement a mirror on filesystems for high availbility if my Storage Disk A or B crashs.
3. Implementing
a. Make a PV on new disk (/dev/dm-28)
# pvcreate /dev/dm-28
b. Add new volume on the vg_gfs00
# vgextend vg_gfs00 /dev/dm-28
c. Make a mirror on Logical Volume
# lvconvert -m1 vg_gfs00/lv00 /dev/dm-28
vg_gfs00/lv00: Converted: 17,1%
vg_gfs00/lv00: Converted: 34,1%
vg_gfs00/lv00: Converted: 51,0%
vg_gfs00/lv00: Converted: 68,4%
vg_gfs00/lv00: Converted: 85,5%
vg_gfs00/lv00: Converted: 100,0%
Note: If your LV are in more PVs you can specify all PVs
Sample:
# lvs -a -o +devices | grep lv00
lv00 vg_gfs00 -wi-ao 10,00G /dev/dm-15(0)
lv00 vg_gfs00 -wi-ao 10,00G /dev/dm-16(123490)
In this case dm-15 and dm-16 are on my Storage Disk A, I need two disks on the Storage Disk B, sample dm-28 and dm-29.
For convert I use this
# lvconvert -m1 vg_gfs00/lv00 /dev/dm-28 /dev/dm-29
d. Checking Mirror with lvs -a -o +devices
# lvs -a -o +devices | grep vl00
lv00 vg_gfs00 mwi-ao 10,00G lv00_mlog 100,00 lv00_mimage_0(0),lv00_mimage_1(0)
[lv00_mimage_0] vg_gfs00 iwi-ao 10,00G /dev/dm-15(10242)
[lv00_mimage_1] vg_gfs00 iwi-ao 10,00G /dev/dm-28(14086)
Looking details:
lv00 is a lv00_mlog and have a 100% of sync to lv00_mimage_0 and lv00_image1.
The lv00_mimage_0 is stored on /dev/dm-15
The lv00_mimage_1 is stored on /dev/dm-28
Looking with a simple lvs
# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
homelv rootvg -wi-ao 512,00M
optlv rootvg -wi-ao 1,00G
rootlv rootvg -wi-ao 1,00G
tmplv rootvg -wi-ao 2,00G
usrlv rootvg -wi-ao 4,00G
varloglv rootvg -wi-ao 8,00G
varlv rootvg -wi-ao 4,00G
lv00 vg_gfs00 -wi-ao 239,03G lv00_mlog 100,00
If the lv00_mlog is not 100% you have a problem with one of disks.
4. Documentation:
* http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Cluster_Logical_Volume_Manager/
- 2.3.3. Mirrored Logical Volumes
- 4.4.1.3. Creating Mirrored Volumes
- 6.3. Recovering from LVM Mirror Failure
1 – Creating the Volume Group
# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 rootvg lvm2 a- 62.75G 38.97G
/dev/dm-10 lvm2 -- 70.00G 70.00G
/dev/dm-13 lvm2 -- 70.00G 70.00G
/dev/dm-14 lvm2 -- 70.00G 70.00G
/dev/dm-9 lvm2 -- 70.00G 70.00G
# vgcreate vg_cluster00 /dev/dm-10 /dev/dm-13 /dev/dm-14 /dev/dm-9
Volume group "vg_cluster00" successfully created
# pvs
PV VG Fmt Attr PSize PFree
/dev/dm-10 vg_cluster00 lvm2 a- 70.00G 70.00G
/dev/dm-13 vg_cluster00 lvm2 a- 70.00G 70.00G
/dev/dm-14 vg_cluster00 lvm2 a- 70.00G 70.00G
/dev/dm-9 vg_cluster00 lvm2 a- 70.00G 70.00G
/dev/sda3 rootvg lvm2 a- 62.75G 38.97G
# vgs
VG #PV #LV #SN Attr VSize VFree
rootvg 1 9 0 wz--n- 62.75G 38.97G
vg_cluster00 4 0 0 wz--n- 279.98G 279.98G
2 – Creating the Logical Volumes
# vcreate -L180G vg_cluster00 -n lvuserapp
3 – Making the Cluster
Particulary I like system-config-cluster
This is my simple /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster alias="CLUSTER00" config_version="23" name="CLUSTER00">
<fence_daemon post_fail_delay="0" post_join_delay="3"/>
<clusternodes>
<clusternode name="node001" nodeid="1" votes="1">
<fence>
<method name="1"/>
</fence>
</clusternode>
<clusternode name="node003" nodeid="3" votes="1">
<fence>
<method name="1"/>
</fence>
</clusternode>
<clusternode name="node004" nodeid="4" votes="1">
<fence>
<method name="1"/>
</fence>
</clusternode>
<clusternode name="node002" nodeid="2" votes="1">
<fence>
<method name="1"/>
</fence>
</clusternode>
</clusternodes>
<fencedevices/>
</cluster>
4 – making gfs2 filesystems
# mkfs -t gfs2 -p lock_dlm -t CLUSTER00:lvuserapp -j 8 /dev/vg_cluster00/lvuserapp
5 – mounting GFS2 filesystems
Put on the /etc/fstab file
/dev/vg_cluster00/lvuserapp /home/userapp gfs2 defaults 0 0
6 – Start the cluster services
Note: For complete startup start the service on all nodes.
service cman start
service rgmanager start
7 – Check the nodes
# cman_tool nodes
Node Sts Inc Joined Name
1 M 196 2009-04-09 11:57:16 node001
2 M 216 2009-04-09 11:57:32 node002
3 M 212 2009-04-09 11:58:02 node003
4 M 214 2009-04-09 11:58:32 node004
8 – mounting the filesystems
Mount filesystems on all nodes
# mount /home/userapp
9 – testing the read/write files on nodes
# touch /home/userapp/teste.txt
Check on all servers if this file exist.
Sources:
- http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Logical_Volume_Manager/index.html
- http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/index.html
- http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Global_File_System_2/index.html
Looking my adapters I found fcs0 in diagnose state
# lsdev -Cc adapter
ent0 Available 21-08 IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
ent1 Available 1A-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)
ent2 Available 14-08 Gigabit Ethernet-SX PCI Adapter (14100401)
ent3 Available 37-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)
ent4 Available 27-08 Gigabit Ethernet-SX PCI Adapter (14100401)
ent5 Available 3A-08 Gigabit Ethernet-SX PCI Adapter (14100401)
fcs0 Diagnose 2A-08 FC Adapter
fda0 Available 01-D1 Standard I/O Diskette Adapter
mg20 Available 2D-08 GXT130P Graphics Adapter
ppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adapter
sa0 Available 01-S1 Standard I/O Serial Port
sa1 Available 01-S2 Standard I/O Serial Port
sa2 Available 01-S3 Standard I/O Serial Port
sa3 Available 01-S4 Standard I/O Serial Port
scsi0 Available 11-08 Wide/Ultra-2 SCSI I/O Controller
scsi1 Available 11-09 Wide/Ultra-2 SCSI I/O Controller
scsi2 Available 17-08 Wide/Fast-20 SCSI I/O Controller
sioka0 Available 01-K1-00 Keyboard Adapter
siokma0 Available 01-K1 Keyboard/Mouse Adapter
sioma0 Available 01-K1-01 Mouse Adapter
# lsdev -C | grep fsc0
fcs0 Diagnose 2A-08 FC Adapter
Run the ucfgdiag to change this state
# /etc/methods/ucfgdiag -l fcs0
Looking devices
# lsdev -Cc adapter
ent0 Available 21-08 IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
ent1 Available 1A-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)
ent2 Available 14-08 Gigabit Ethernet-SX PCI Adapter (14100401)
ent3 Available 37-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)
ent4 Available 27-08 Gigabit Ethernet-SX PCI Adapter (14100401)
ent5 Available 3A-08 Gigabit Ethernet-SX PCI Adapter (14100401)
fcs0 Defined 2A-08 FC Adapter
fda0 Available 01-D1 Standard I/O Diskette Adapter
mg20 Available 2D-08 GXT130P Graphics Adapter
ppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adapter
sa0 Available 01-S1 Standard I/O Serial Port
sa1 Available 01-S2 Standard I/O Serial Port
sa2 Available 01-S3 Standard I/O Serial Port
sa3 Available 01-S4 Standard I/O Serial Port
scsi0 Available 11-08 Wide/Ultra-2 SCSI I/O Controller
scsi1 Available 11-09 Wide/Ultra-2 SCSI I/O Controller
scsi2 Available 17-08 Wide/Fast-20 SCSI I/O Controller
sioka0 Available 01-K1-00 Keyboard Adapter
siokma0 Available 01-K1 Keyboard/Mouse Adapter
sioma0 Available 01-K1-01 Mouse Adapter
# lsdev -C | grep fsc0
fcs0 Defined 2A-08 FC Adapter
Now, I can remove device and your childs for new discover.
ATENTION: This command remove all child and device
# rmdev -dl fcs0 -R
fcnet0 deleted
fscsi0 deleted
fcs0 deleted
For new discover run cfgmgr
# cfgmgr -v
O problema
Após adquirir um smartphone Motorola modelo Q11 tive problemas de conectividade com meu roteador wireless do fabricante D-Link modelo DI-524.
Pesquisando na Internet encontrei mais relatos sobre o mesmo problema.
1. É preciso ler os 3 primeiros posts
http://www.plusgsm.com.br/forums/showthread.php?t=104926
2. Veja o comentário numero #9 deste preview
http://zumo.uol.com.br/2008/10/18/preview-motorola-moto-q11/
3. Veja o comentário numero #1 deste review
http://seidimobile.com.br/2009/02/27/review-motorola-moto-q11/
As respostas de ambos os fabricantes
Após obviamente falar com ambos os fabricantes, D-Link e Motorola, recebo a seguinte resposta (obviamente a mais fácil)
Motorola: “Informamos que o aparelho não possui restrição para roteadores. Ressaltamos que é necessário inserir os dados da configuração de rede para que possa ter o acesso.”
D-Link: “É necessário contactar o fabricante do aparelho celular”
Tudo bem, não sei de quem é o problema mas deveriam se esforçar o mínimo possível.
Solução parcial do problema
Por que parcial? Porque a velocidade ainda continua uma porcaria.
Dica: Abra um chamado telefonico na Motorola e na D-Link para o problema, isso ajuda a resolvermos o problema.
Fazendo uma análise do problema identifiquei que o roteador D-Link não consegue entregar o endereço IP ao celular, ou obviamente, o celular não consegue receber o endereço IP. Cheguei a verificar que nos logs do roteador o mesmo realizava a tentativa de conexão.
Sendo assim, entrei novamente em contato com a Motorola afim de saber se é possível colocar um IP estático na configuração de rede do Wi-Fi, novamente recebo uma resposta evasiva.
Pesquisando na Internet por uma forma de colocar IP estático no Windows Mobile 6.1 encontrei este software http://www.freewarepocketpc.net/ppc-download-wifi-profiles-v0-0-2.html
Também instalei um software que pudesse realizar testes como ping. Para isso instalei este aqui http://tools.enterprisemobile.com/iputil/
Crie dois profiles com o WifiProfiles.
Um deixando o endereço IP estático e outro deixando o uso do DHCP.
Quando for utilizar o roteador wireless DI-524 aplique o profile IP estático, quando for usar demais roteadores aplique o profile DHCP
Você pode fazer testes de ping com o EN IP Utility
Installing IBM lin_tape on Linux (Red Hat Enterprise Linux)
Steps for install lin_tape and lin_taped
1. Download the lin_tape source and lin_taped from ftp://ftp.software.ibm.com/storage/devdrvr/Linux/lin_tape_source-lin_taped/
lin_tape-X.YY.Z-W.src.rpm.bin
lin_taped-X.YY.Z-rhel[V].arch.rpm.bin
Samples for version 1.20.0-1
lin_tape-1.20.0-1.src.rpm.bin
lin_taped-1.20.0-rhel4.x86_64.rpm.bin
2. Rebuild lin_tape rpm source
# rpmbuild --rebuild lin_tape-X.YY.Z-W.src.rpm.bin
First you need rpm2cpio
Use
# mkdir /tmp/package
# cp package.rpm /tmp/package
# cd /tmp/package
# rpm2cpio package.rpm | cpio -idv
Posted by Wordmobi
Inglish (português mais abaixo)
The package basesystem contains no files
# rpm -ql basesystem
(contains no files)
But your discription is very clean:
Basesystem defines the components of a basic Red Hat Linux system (for
example, the package installation order to use during bootstrapping).
Basesystem should be the first package installed on a system and it
should never be removed.
You can check Install Date from this package
# rpm -qi basesystem
Name : basesystem Relocations: (not relocatable)
Version : 8.0 Vendor: Red Hat, Inc.
Release : 4 Build Date: Wed 22 Sep 2004 07:01:44 PM BRT
Install Date: Sat 17 Jan 2009 05:28:37 PM BRST Build Host: tweety.build.redhat.com
Group : System Environment/Base Source RPM: basesystem-8.0-4.src.rpm
Size : 0 License: public domain
Signature : DSA/SHA1, Wed 05 Jan 2005 09:03:37 PM BRST, Key ID 219180cddb42a60e
Packager : Red Hat, Inc.
Summary : The skeleton package which defines a simple Red Hat Linux system.
Description :
Basesystem defines the components of a basic Red Hat Linux system (for
example, the package installation order to use during bootstrapping).
Basesystem should be the first package installed on a system and it
should never be removed.
Português
Checando a data de instalação do Sistema Operacional Linux (Red Hat) – Não oficial, mas utilizavel
O pacote basesystem não contem arquivos
# rpm -ql basesystem
(contains no files)
Mas usa descrição é muito simples:
Basesystem defines the components of a basic Red Hat Linux system (for
example, the package installation order to use during bootstrapping).
Basesystem should be the first package installed on a system and it
should never be removed.
Você pode checar a data de instalação a partir deste pacote
# rpm -qi basesystem
Name : basesystem Relocations: (not relocatable)
Version : 8.0 Vendor: Red Hat, Inc.
Release : 4 Build Date: Wed 22 Sep 2004 07:01:44 PM BRT
Install Date: Sat 17 Jan 2009 05:28:37 PM BRST Build Host: tweety.build.redhat.com
Group : System Environment/Base Source RPM: basesystem-8.0-4.src.rpm
Size : 0 License: public domain
Signature : DSA/SHA1, Wed 05 Jan 2005 09:03:37 PM BRST, Key ID 219180cddb42a60e
Packager : Red Hat, Inc.
Summary : The skeleton package which defines a simple Red Hat Linux system.
Description :
Basesystem defines the components of a basic Red Hat Linux system (for
example, the package installation order to use during bootstrapping).
Basesystem should be the first package installed on a system and it
should never be removed.
For Volume Group data redistribution in the disks (strip) uses reorgvg command.
# reorgvg myvg
This command need a few times. Rum in background.
# nohup reorgvg myvg &
Posted by Wordmobi
This post show installation of MegaCli (ServeRAID MR 10 k SAS/SATA Controller client) and two basic commands
1. Installation
Get ServeRAID CD and extract the file MegaCli-X.XX.XX-Y.i386.rpm.
Install using the rpm command
# rpm -ivh rpms/MegaCli-3.00.07-1.i386.rpm
Preparing... ########################################### [100%]
1:MegaCli ########################################### [100%]
Listing the installed files with rpm command
# rpm -ql MegaCli
/opt/MegaRAID/MegaCli/MegaCli
/opt/MegaRAID/MegaCli/MegaCli64
2. Basic commands
Continue Reading »
-
Unix, AIX, Linux, Storage Disk, Storage Area Network (SAN), HMC, Blade Center, IBM, TI, SysAdmin, Computação e Pessoal
Unix & Storage Disk Administrator at IBM Brazil.
Note: All information and opinions in this blog / website are purely personal and do not reflect any opinions or information from IBM.
Nota: Todas as informações e opniões neste blog/website são meramente pessoais e não refletem quaisquer opniões ou informações da IBM.
Fast Blog (Pessoal)
