Comments (0)

By admin, March 16, 2011 10:24 pm

今天看到的一段新聞﹐這樣的事情看來只會在中國大陸發生﹐可憐的小牛Gallardo和中國人。看見沒有﹐拿著傢伙的工人砸著的時候竟帶有詭異的笑容﹐令我不寒而慄﹐難道中國人真的有根深蒂固的“小農”基因﹖I am not sure what Jeremy of Top Gear would say if he ever came across this news.

据车主介绍，2010年11月29日，这辆购入不久的跑车，就在青岛出现了发动机不打火的故障。车主与该公司青岛销售店联系后，车由青岛销售店委托的维修服务商安排的拖车运至指定的维修店。没想到的是，运至维修店后，不但发动机故障没有得到解决，车辆保险杠和底盘也受损断裂。

经多次维权仍不能圆满解决，车主决定砸毁这辆兰博基尼。昨日下午3：15，在青岛一灯具城门口，车主雇人将这辆价值300万的兰博基尼盖拉多跑车，砸得面目全非。

Comments (0)

By admin, March 15, 2011 5:43 pm

今天是我在香港討論區網球版的兩週年紀念。

在過去的兩年裡﹐跟超過120位朋友切磋過﹐他們幾乎都有自己的秘技和不同的打法﹐從他們的身上我學到了很多寶貴的經驗如冷靜的頭腦﹑完善的計劃﹑堅人的毅力﹑爆炸的力量等﹐這都使我本身的技術比兩年前有明顯的提昇﹐謝謝你們的參與令到每次的球聚都令人留連忘返。

希望今後的日子有更多的朋友和我一齊來享受Happy Tennis。

Some interesting statistics:

Courts Booked: ~180場
Tennis Balls: 60罐
Restring: 4次

Comments (0)

By admin, March 13, 2011 9:46 pm

After watching the demo of VMware vCenter Operations, I would say it’s just another monitoring and diagnostic tool besides the leading two: vfoglight from Vizioncore and Veeam Monitor from Veeam, nothing really special, but it does present the trouble ones in an intuitive way by using color icons.

Personally, I found Veeam Monitor Free Edition is already more than enough to identify the problem and find out where the latency is, the key is to look at the lowest or deepest layer, in other words, into VM itself, as the problematic VM is the most fundamental element causing the contention on Resorucs pool, ESX Host, vCenter, etc.

Then I ask myself why would VMware release such product while there are already two great products in the market? Well, I will leave this question to you in the comment.

Update Apr 5

I’ve tried the Free Xangati for ESX and don’t like it, it’s not as intuitive as Veeam Monitor.

Comments (6)

By admin, March 9, 2011 10:29 pm

Originally I thought we are going to have a small footprint and easy managed software finally arrived from Dell, but I was wrong totally.

After spending hours and hours of trying to install DMC 2.0 on Physical and VM, both failed multiple times, I finally gave up. It was a buggy software and not to mention the size of it (over 1GB) and the bunch of crap modules it’s trying to load to your server (there are more than 80 stages during the installation).

I would strongly recommend everyone with a common sense to avoid using this product even it’s free of charge. Simply because it’s way over complicated and the pre-requirement can make anyone big headache, took over 1 hour to install on latest hardware server and finally failed during installation!

I would rather use PRTG as the tool for my monitoring purpose and I was hoping DMC can do me only one thing (hardware failure alert), now I will skip it forever and never look back, I will depend on vCenter’s hardware monitoring and iDRAC’s alert to help me to achieve the same goal.

Bye Bye DMC 2.0, the crappiest software I’ve ever encountered since MS Commerce Server back then.

Comments (0)

By admin, March 8, 2011 8:28 pm

What a nice looking 1960s car from Alfa Romeo! Coming soon from Autoart!

Comments (0)

By admin, March 5, 2011 5:15 pm

It’s a common question: “Are there any BIOS settings Dell recommends for VMware ESX/vSphere?” Primarily, Dell recommends reading and following VMware’s best practices. The latest revision (as of this posting) can be found in their article “Performance Best Practices for VMware vSphere™ 4.1”. Here are a list of additional points of interest specifically regarding Dell PowerEdge servers:

• Hardware-Assisted Virtualization: As the VMware best practices state, this technology provides hardware-assisted CPU and MMU virtualization.
  In the Dell PowerEdge BIOS, this is known as “Virtualization Technology” under the “Processor Settings” screen. Depending upon server model, this may be Disabled by default. In order to utilize these technologies, Dell recommends setting this to Enabled.
• Intel® Turbo Boost Technology and Hyper-Threading Technology: These technologies, known as “Turbo Mode” and “Logical Processor” respectively in the Dell BIOS under the “Processor Settings” screen, are recommended by VMware to be Enabled for applicable processors; this is the Dell factory default setting.
• Non-Uniform Memory Access (NUMA): VMware states that in most cases, disabling “Node Interleaving” (which enables NUMA) provides the best performance, as the VMware kernel scheduler is NUMA-aware and optimizes memory accesses to the processor it belongs to. This is the Dell factory default.
• Power Management: VMware states “For the highest performance, potentially at the expense of higher power consumption, set any BIOS power-saving options to high-performance mode.” In the Dell BIOS, this is accomplished by setting “Power Management” to Maximum Performance.
• Integrated Devices: VMware states “Disable from within the BIOS any unneeded devices, such as serial and USB ports.” These devices can be turned off under the “Integrated Devices” screen within the Dell BIOS.
• C1E: VMware recommends disabling the C1E halt state for multi-threaded, I/O latency sensitive workloads. This option is Enabled by default, and may be set to Disabled under the “Processor Settings” screen of the Dell BIOS. (I will keep the default to Enabled as I want to save more power in my data center and be enviornmental friendly)
• Processor Prefetchers: Certain processor architectures may have additional options under the “Processor Settings” screen, such as Hardware Prefetcher, Adjacent Cache Line Prefetch, DCU Streamer Prefetcher, Data Reuse, DRAM Prefetcher, etc. The default settings for these options is Enabled, and in general, Dell does not recommend disabling them, as they typically improve performance. However, for very random, memory-intensive workloads, you can try disabling these settings to evaluate whether that may increase performance of your virtualized workloads.

Finally, in order to take the advantage of ESX 4.1 Power Management feature in vCenter to show up, you need to change the setting in BIOS Power Management to “OS Control”.

Comments (3)

By admin, March 4, 2011 10:18 am

今天在MC論壇看到ENZOBOY寫的﹐分析得還真不錯。

就如最近大家都提到的關于zonda r的螺絲問提，以及最近伯陵近乎偏執得對照真車每個細節改他的ky enzo讓我突然想到，模型的細節到底該怎么看待﹕

現在模型厂商的工藝越來越好，模型的細節就越來越多，當然收藏者對模型的細節追求也更孜孜不倦，模型的鉚釘，線管，拆卸功能和零件數量的增加，尤其在老車上更加明顯的體現，大家都在追求cmc exoto的精度，后者更是想讓模型真正成為小比例汽車，不少厂家如aa也在提高自己的工藝，從量產版的veyron 到mclaren f1 和zonda r 的推出，讓人看到aa向cmc靠近的步伐。

但是在瘋狂追求細節的同時，我冷靜下來拿著自己的為數不多的能稱為結构派的模型和真車作起了對比，其實很多細節當初另我看的欣喜甚至激動，但是在和照片的對比下發現 有些更本就是模型商為了迎合顧客而夸大的細節，很多線，鉚釘之類的零件在縮小了12倍甚至18倍的情況下，如果不是故意看應該是不會注意到的，但是在很多模型上卻是能夠成為吸引人的地方，這有時使自己這個細節追求者感到矛盾，一方面我是喜歡這些細節的，一方面他們可能又是錯誤的。

其實很多模型在制作過程中也因為工藝問題在細節作了妥協，由于真車和人的比例關系，很多鉸鏈和固定方式根本就無法在模型上體現，這也就是為什么出現了狗腿，和龜車。畢竟比例模型不能把車體材料厚度和車窗厚度以及油漆厚度都那樣縮小，很多真車可行的打開方式和打開角度放到模型上就會出問題。

有時想想模型也該肩負，不能無畏的增加零件數，一些不必要的零件和管線省略可能更好。過分突出的細節會另車看上去更臃腫，在視覺感受上反而和真車背道而馳。

舉些比例過大 或者 厂家由于工藝放棄的一些例子﹕

1. pagani zonda r 這個例子大家都知道，懸挂和尾翼上的過分大的鉚釘降低了這款車的整體分數，如果尾翼是固定的 只是做出几個鉚釘的型 懸挂的螺釘用其他方式做，模型离真車的感覺更靠近。
2. cmc 和 exoto的 156 f1 這款車是這兩個品牌中數一數2工藝的模型，但是仔細看 剎車卡鉗上的剎車銅線，放大18倍就是過分的大了，exoto則為了體現細節 把一些零件做的過分大了 導致為了容下并體現這些零件 而把有些零件和車架部分做得夸大。
3. gmp Ferrari p4 這款車很漂亮 但是車子尾部和周身的鉚釘顯然是比真車更大了，還有由于材料問題導致的，過粗的剎車導管，使車的轉向變的艱難。
4. bbr ky 的法拉利系列，不論是f430 f458（試作開門版）還是bbr 的enzo 引擎蓋打開后前沿都是高于車頂的，其實也就是傳統說的狗腿，只是外形經過處理，更好看些，由于法拉利的車尾鉸鏈采用的類似家里們框鉸鏈，所以真車裝嵌時需要打開時在內部固定，因此bbr只得采用狗腿方式。
5. tamiya / kyosho 1/12 enzo 同樣是和bbr一樣的鉸鏈問題，法拉利的鉸鏈方式導致了 ky在把bbr的模型放大后依然采用類狗腿方式，導致影響門的開合。而同樣的問題 tamiya似乎用了更聰明 但也是更冒險的方式，他自己制作出一個鏈接方式，引擎蓋可以以和真車几乎相同的方式打開，但是因為材料厚度限制的原因，雖然勉強做到了和真車一致，但是打開到極限并用撐杆撐起后，其實門是被彎曲的，所以后來很多玩家表示引擎蓋變形嚴重。
6. aa ky bbr tamiya 等一些模型的開閉机關 很多中高端模型會為了將模型的一些可動部件做出來，在底盤出設置一個按鈕，但是很多時候就因為這些按鈕讓模型感覺更差。bbr 的 f430 enzo ,ky的r8 f40 ,aa的cgt 以及tamiya 門內側多余的圓柱型部件，每次拍照都覺得相當礙眼。

Comments (0)

By admin, March 2, 2011 12:36 pm

As usual, I would suggest to wait another 1-2 months before upgrading your EQL firmware since the latest firmware may always contain bugs.

Since none of the followings applies to my enviornment, so I will just skip this update completely.

Issues Corrected in this version (v5.0.4) are described below:

• Contention for internal resources could cause a controller failover to occur.

• In rare circumstances, after a communication problem between group members, a PS6000, PS6500, PS6010, or PS6510 member may become unresponsive or experience a controller failover.

• In some cases, a controller failover may occur during a drive firmware update that takes place while the array is in a period of low activity.

• Drives may be incorrectly marked as failed. (happened mostly in PS4000 series)

• An invalid authentication failure may occur when using a RADIUS

• A hardware failure on the primary controller during a firmware update may inhibit failover to the secondary controller. server for CHAP authentication.

• Out-of-order network packets received by the array may cause retransmits.

• The array may not be able to clone a snapshot if the following scenario occurs: the parent volume was replicated to another group, the remote copy was promoted, and the changes were subsequently copied back to the original group using the Fast Failback process.

• Cannot clone snapshots of volumes with replicas that were promoted and subsequently failed back.

• Replication sometimes cannot be completed due to a problem with communication between the replication partners.

• In some cases, replication of a large amount of data may cause a shortage of internal resources, causing the GUI to become unresponsive.

• A network error may cause a failback operation to be unable to complete successfully, with the system issuing a “Replication partner cannot be reached” error.

• Exhausting the delegated space during replication may require that the in-process replica be cancelled in order to permit the volume to continue replicating as expected.

• A group running V5.0 firmware might be unable to perform management functions due to a lack of resources if a group running V3.3 firmware is replicating data to it.

• A restart of an internal management process could result in drives temporarily going offline in PS6010 and PS6510 systems.

Comments (0)

By admin, February 26, 2011 9:35 pm

I’ve encountered a problem when installing Windows Server 2008 R2 SP1 today and found the reason and solution pretty easy. It was due to Veeam B&R v5.0 automatically Disabled automount for SAN mode and W2K8 R2 SP1 requires automount to be enabled.

Solution:

1. Disconnect all active iSCSI connections and REMOVE the Target Portal from iSCSI favourite tab. 

2. From command prompt, issue the followings:
> diskpart
> automount enable

3. Reboot the server then go ahead and upgrade your W2K8 R2 with SP1, it will take about 50 minutes to complete, yes, it did take that long even on latest powerful server.

4. Then issue the following AFTER reboot:
> diskpart
> automount disable

5. Reboot the last time and then re-establish all previous iSCSI connections as usual.