Blackberry Services Netmask
Recently I’ve deployed some Blackberry Enterprise Server, this link is useful for firewalls policy deploy
Blackberry Services Netmask Read More »
Recently I’ve deployed some Blackberry Enterprise Server, this link is useful for firewalls policy deploy
Blackberry Services Netmask Read More »
[root@pbx01.mil1.wide-net.org ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
1779856 1553320 138068 92% /
/dev/vda1 101086 40798 55069 43% /boot
tmpfs 513060 0 513060 0% /dev/shm
[root@pbx01.mil1.wide-net.org ~]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
[root@pbx01.mil1.wide-net.org ~]# fdisk /dev/vda
vda vda1 vda2
[root@pbx01.mil1.wide-net.org ~]# fdisk /dev/vda
Command (m for help): p
Disk /dev/vda: 4219 MB, 4219469824 bytes
255 heads, 63 sectors/track, 512 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/vda1 * 1 13 104391 83 Linux
/dev/vda2 14 382 2963992+ 8e Linux LVM
Command (m for help): d
Partition number (1-4): 2
Command (m for help): p
Disk /dev/vda: 4219 MB, 4219469824 bytes
255 heads, 63 sectors/track, 512 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/vda1 * 1 13 104391 83 Linux
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (14-512, default 14):
Using default value 14
Last cylinder or +size or +sizeM or +sizeK (14-512, default 512):
Using default value 512
Command (m for help): p
Disk /dev/vda: 4219 MB, 4219469824 bytes
255 heads, 63 sectors/track, 512 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/vda1 * 1 13 104391 83 Linux
/dev/vda2 14 512 4008217+ 83 Linux
Command (m for help): t
Partition number (1-4): 2
Hex code (type L to list codes): 8e
Changed system type of partition 2 to 8e (Linux LVM)
Command (m for help): p
Disk /dev/vda: 4219 MB, 4219469824 bytes
255 heads, 63 sectors/track, 512 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/vda1 * 1 13 104391 83 Linux
/dev/vda2 14 512 4008217+ 8e Linux LVM
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
[root@pbx01.mil1.wide-net.org ~]# reboot
Broadcast message from root (pts/0) (Sat Sep 15 23:36:59 2012):
The system is going down for reboot NOW!
[root@pbx01.mil1.wide-net.org ~]# Connection to pbx01.mil1.wide-net.org closed by remote host.
Connection to pbx01.mil1.wide-net.org closed.
[leo@thinkleo3 ~]$
[root@pbx01.mil1.wide-net.org ~]# pvdisplay
--- Physical volume ---
PV Name /dev/vda2
VG Name VolGroup00
PV Size 2.83 GB / not usable 14.52 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 90
Free PE 26
Allocated PE 64
PV UUID 3KFfOG-kfJZ-hNtT-0vo5-Lpzk-4iMR-rMmLzH
[root@pbx01.mil1.wide-net.org ~]# pvresize /dev/vda2
Physical volume "/dev/vda2" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
[root@pbx01.mil1.wide-net.org ~]# pvdisplay
--- Physical volume ---
PV Name /dev/vda2
VG Name VolGroup00
PV Size 3.82 GB / not usable 10.09 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 122
Free PE 58
Allocated PE 64
PV UUID 3KFfOG-kfJZ-hNtT-0vo5-Lpzk-4iMR-rMmLzH
[root@pbx01.mil1.wide-net.org ~]# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID f134eo-A1TY-mj72-g16E-oBnl-fnNM-4hULDC
LV Write Access read/write
LV Status available
# open 1
LV Size 1.75 GB
Current LE 56
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID 1gNpNl-ypNO-bj4a-Gsyb-eGnS-UcFh-Rbocfj
LV Write Access read/write
LV Status available
# open 1
LV Size 256.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:1
[root@pbx01.mil1.wide-net.org ~]# lvresize /dev/VolGroup00/LogVol00 -l +1
Extending logical volume LogVol00 to 3.59 GB
Insufficient free space: 1 extents needed, but only 0 available
[root@pbx01.mil1.wide-net.org ~]# resize2fs /dev/VolGroup00/LogVol00
resize2fs 1.39 (29-May-2006)
Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required
Performing an on-line resize of /dev/VolGroup00/LogVol00 to 933888 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 933888 blocks long.
[root@pbx01.mil1.wide-net.org ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
3.5G 1.5G 1.8G 46% /
/dev/vda1 99M 40M 54M 43% /boot
tmpfs 502M 0 502M 0% /dev/shm
[root@pbx01.mil1.wide-net.org ~]# reboot
Broadcast message from root (pts/0) (Sat Sep 15 23:43:32 2012):
The system is going down for reboot NOW!
[root@pbx01.mil1.wide-net.org ~]#
Linux – KVM Guest LVM Disk Resize Read More »
For really strange combination of events, I need this tables of error codes from Tivoli Productivity Center – Storage resource agent.
Return code | Explanation |
---|---|
1 | There is a problem uninstalling the Data agent or Fabric agent. For more information about what caused the uninstallation to fail, check the uninstallation logs for the Data agent or Fabric agent. |
2 | Command not valid. |
3 | Option provided is not valid. |
5 | Argument is not valid. |
6 | Missing value for argument (e.g. -installLoc <Value>, where <Value> is missing). |
7 | Missing localized string in message file. |
8 | Probe is running. |
9 | Failed to open file for write. |
10 | Failed to close file. |
11 | Logfile not specified. |
19 | Failed in tracing. |
21 | Cannot spawn a probe because it is busy. |
30 | This is an internal error in initializing tracing. Save the error message and error log and contact your service representative for assistance in resolving the error. |
32 | Invalid socket. |
33 | Start service failed. |
34 | Registry entry not found. |
35 | Deployment of the agent failed, error creating startup scripts. |
36 | File does not exist. |
40 | Missing upgrade files. |
41 | Failed to extract files in upgrade process. |
42 | Failed to stop probe in upgrade process. |
43 | Failed to stop Agent. |
44 | Failed to start Agent. |
45 | Agent Registration to server failed. |
46 | File extraction needs more space. |
47 | Failed to open archive file. |
48 | Agent did not start after upgrade. |
49 | Installation directory not valid at upgrade time. |
50 | Probe is running. |
51 | Data file not found. |
52 | Exit code not in the output file. |
53 | Failed to send job status. |
54 | Failed to copy certificate files. |
55 | Failed to create directory. |
56 | Failed to remove directory. |
57 | Exec command failed. |
58 | Conversion of wide character failed. |
59 | Installation directory not valid. |
60 | Server name not defined. |
61 | Error in removing entries from configuration file. |
62 | Failed to stop probe at uninstall time. |
63 | Failed to remove registry entry at uninstall time. |
64 | Failed to remove service entry at uninstall time. |
65 | Failed to stop service at uninstall time. |
66 | Specified server name is not valid. |
67 | There is an error installing the Storage Resource agent as part of the migration process. For more information about what caused the installation to fail, check the installation logs for the Storage Resource agent. |
71 | Failed to spawn process. |
73 | Failed to spawn probe process. |
101 | Failed to create lock at installation time. |
102 | Failed to stop probe at re-installation time. |
103 | Failed to stop agent at re-installation time. |
104 | Failed to create registry at installation time. |
105 | Failed to extract files at installation time. |
106 | Failed to create entries in configuration file at installation time. |
107 | Failed to stop service at re-installation time. |
108 | Service already exists. |
109 | Failed to create service. |
110 | Failed to start service. |
111 | Probe failed at installation time. |
112 | Creation of daemon failed. |
113 | Installation of GUID failed. |
114 | Commtype parameter is not valid. |
115 | Specified port is in use. |
116 | Installation/Upgrade does not have enough space. |
117 | Installation in progress. |
118 | Cannot get server name from Server. |
119 | Installation location is not empty. |
120 | Missing parameter Server Name. |
121 | Missing parameter Server Port. |
123 | Missing parameter Server IP. |
124 | Missing parameter Agent Port. |
125 | Missing parameter Installation location. |
127 | Deployment from Windows to Linux failed. |
130 | Failed to send probe results. |
131 | Failed to initialize Agent. |
133 | Missing port number for Service. |
134 | Get data file stat failed. |
135 | Get data file read failed. |
137 | Failed to send data to server. |
138 | Failed to receive data from server. |
139 | Full path not specified for copy file. |
140 | Create file failed in copy file function. |
141 | Write file failed in copy file function. |
142 | Open file failed in copy file function. |
143 | Read file failed in copy file function. |
145 | UCS conversion failed. |
146 | Server connection failed. |
148 | Failed to create zip file. |
149 | Failed to unzip file. |
160 | Failed to send scan results. |
161 | Failed to send TSM status results. |
164 | Failed to validate user. |
165 | Job file was not found. |
166 | Job was not stopped. |
168 | Not enough free space available while copying file from server. |
169 | Multipath driver not found. |
170 | Multipath device not found. |
171 | Multipath policy is not supported. |
172 | Only Round Robin policy is supported for Multipath DM driver. |
TPC – Storage Resource agent error code Read More »