battenberg is back (in jellicoe)

| | Comments (0)
nothing changes on your end;  on my end I need to make sure that I re-label the hardware.   The server that was going to be jellicoe now houses the disks that were battenberg.  


The whole thing is up and running and looking good.

[lsc@battenberg auto]$ cat /proc/cpuinfo; cat /proc/mdstat
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 45
model name    :        Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
stepping    : 7
cpu MHz        : 2000.000
cache size    : 20480 KB
physical id    : 0
siblings    : 1
core id        : 0
cpu cores    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu tsc msr pae cx8 apic mtrr cmov pat clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc pni vmx est ssse3 cx16 sse4_1 sse4_2 popcnt lahf_lm
bogomips    : 5005.93
clflush size    : 64
cache_alignment    : 64
address sizes    : 46 bits physical, 48 bits virtual
power management:

Personalities : [raid1] [raid10]
md1 : active raid10 sdh2[1] sdg2[0] sdf2[7] sde2[6] sdd2[5] sdc2[4] sdb2[3] sda2[2]
      7772118016 blocks 256K chunks 2 near-copies [8/8] [UUUUUUUU]
     
md0 : active raid1 sdh1[6] sdg1[0] sdf1[7] sde1[1] sdd1[2] sdc1[3] sdb1[4] sda1[5]
      10482304 blocks [8/8] [UUUUUUUU]
     
unused devices: <none>

Leave a comment

About this Entry

This page contains a single entry by luke published on July 4, 2014 9:20 PM.

letting battenberg rebuild was the previous entry in this blog.

data recovery update on the KVM (formerly tile networks) guest. Alternate title: Frozen Peas revisited. is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.