пятница, 3 апреля 2015 г.

mdadm failed device

vvelichko:~# mdadm -Q --detail /dev/md1
/dev/md1:
        Version : 1.2
  Creation Time : Thu Oct 11 20:35:01 2012
     Raid Level : raid1
     Array Size : 488255296 (465.64 GiB 499.97 GB)
  Used Dev Size : 488255296 (465.64 GiB 499.97 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Fri Apr  3 19:23:00 2015
          State : active, degraded
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

           Name : vvelichko:1  (local to host vvelichko)
           UUID : 62682c99:dff5af61:58b9452d:08a77070
         Events : 20230880

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       0        0        1      removed

       2       8       33        -      spare   /dev/sdc1

В этих ваших интернетах написаны тонны непотребной херни, вплоть до ручной миграции данных с массива. Суть в строке "Total Devices : 2"

vvelichko:~# mdadm --grow --raid-devices=3 /dev/md1

ребилд запуститься автоматически:

vvelichko:~# mdadm -Q --detail /dev/md1
/dev/md1:
        Version : 1.2
  Creation Time : Thu Oct 11 20:35:01 2012
     Raid Level : raid1
     Array Size : 488255296 (465.64 GiB 499.97 GB)
  Used Dev Size : 488255296 (465.64 GiB 499.97 GB)
   Raid Devices : 3
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Fri Apr  3 19:29:26 2015
          State : clean, degraded, recovering
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

 Rebuild Status : 0% complete

           Name : vvelichko:1  (local to host vvelichko)
           UUID : 62682c99:dff5af61:58b9452d:08a77070
         Events : 20231187

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       2       8       33        1      spare rebuilding   /dev/sdc1
       2       0        0        2      removed


среда, 1 апреля 2015 г.

netbackup timezone

проверка:

backup2:~ # strings /usr/openv/java/jre/lib/zi/ZoneInfoMappings | head -2
javazm
tzdata2013b


для обновления нужен Java SE TZUpdater Downloads

распаковать TZUpdater в /tmp

backup2:/tmp # cd /usr/openv/java/jre/bin

backup2:/usr/openv/java/jre/bin # ./java -jar /tmp/tzupdater-2.0.0-2015a/tzupdater.jar -u -v
java.home: /usr/openv/java/jre
java.vendor: Oracle Corporation
java.version: 1.7.0_25
JRE tzdata version: tzdata2013b
tzupdater tool would update with tzdata version: tzdata2015a
Extracting files... done.
Renaming /usr/openv/java/jre/lib/zi to /usr/openv/java/jre/lib/zi.tzdata2013b
Renaming /usr/openv/java/jre/lib/zi.tzdata2015a to /usr/openv/java/jre/lib/zi
Validating for : tzdata2015a
done.
JRE updated to version : tzdata2015a


проверка:
backup2:/usr/openv/java/jre/bin # ./java -jar /tmp/tzupdater-2.0.0-2015a/tzupdater.jar -V
tzupdater version 2.0.0-b03
JRE tzdata version: tzdata2015a
tzupdater tool would update with tzdata version: tzdata2015a



PS
Oracle как обычно желает всем добра:
Support customers can download a TZUpdater tool for older versions through My Oracle Support. See Note 1412103.2 

PPS
что б два раза не вставать:


Adjusting the time zone in the NetBackup-Java console

Use the following procedure in the NetBackup-Java console to adjust the time zone or to use daylight savings time.
To adjust the time zone in the NetBackup-Java console
  1. In the NetBackup Administration Console, or in the Backup, Archive, and Restore client dialog box, select File > Adjust Application Time Zone.
  2. Select the Standard tab.
  3. Clear the Use custom time zone check box.
  4. Select the time zone.
  5. For daylight savings time, select Use daylight savings time.
  6. To have administrative capabilities and to apply the settings to the current session and all future sessions, select Save as default time zone.
  7. Click OK.