It’s nothing revolutionary, and Dell chassis are having this for a longer time I think, but Super Micro caught up and kept me a very happy customer of theirs. Actually the company I work for is a customer of theirs, I’m just a System Administrator who happens to be installing a whole bunch of new Super Micro servers.

Bottom line is that the new rails mount in the rack without the usage of any tools or rack bolts/nuts. You can mount them with your bare hands. What’s the big deal with this? You spend almost no time in mounting the rails. Good work Super Micro, and Repon!

The mounting process follows in images. Sorry for the bad photo quality.

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

You can see the above error either by starting “firefox” in your console terminal manually, or by reviewing the file “~/.xsession-errors”, if you are running KDE.

I ran Firefox several times in debug mode via “gdb” and every time the debug output lead me to the wrong direction. Here is a sample full backtrace output:

[New Thread 0xadbfeb70 (LWP 3763)]
[Thread 0xadbfeb70 (LWP 3763) exited]
[New Thread 0xadbfeb70 (LWP 3764)]
[Thread 0xadbfeb70 (LWP 3764) exited]
[New Thread 0xadbfeb70 (LWP 3765)]
[New Thread 0xae3ffb70 (LWP 3766)]
[Thread 0xadbfeb70 (LWP 3765) exited]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Program received signal SIGABRT, Aborted.
0x00227422 in ?? ()
(gdb) bt full
#0  0x00227422 in ?? ()
No symbol table info available.
#1  0x002524d1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
        resultvar = <value optimized out>
        pid = 3575796
        selftid = 3708
#2  0x00255932 in *__GI_abort () at abort.c:92
        act = {__sigaction_handler = {sa_handler = 0x7a3ff4, sa_sigaction = 0x7a3ff4}, sa_mask = {__val = {3221183748, 3086869600, 3221183704, 7933961,
              3221183688, 1154680, 3221183676, 8013772, 0, 3086866344, 5, 0, 1, 3221183640, 0, 3221183716, 1356543, 3577255, 3221183636, 3035204, 1,
              3086869160, 0, 3221183748, 3221183676, 3221183688, 0, 4294967295, 1359583, 3086869160, 3221183680, 4294967295}}, sa_flags = 8011764,
          sa_restorer = 0x14b2ff}
        sigs = {__val = {32, 0 <repeats 31 times>}}
#3  0x001cc4df in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:93
        terminating = true
        t = <value optimized out>
#4  0x001ca415 in __cxxabiv1::__terminate (handler=0x1cc390 <__gnu_cxx::__verbose_terminate_handler()>)
    at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:38
No locals.
#5  0x001ca452 in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48
No locals.
#6  0x001ca591 in __cxa_throw (obj=0xad2f9700, tinfo=0x1f97fc, dest=0x1caaf0 <~bad_alloc>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:83
        header = <value optimized out>
#7  0x001cac0f in operator new (sz=2) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:58
        handler = <value optimized out>
        p = <value optimized out>
#8  0x001caced in operator new[] (sz=2) at ../../../../src/libstdc++-v3/libsupc++/new_opv.cc:32
No locals.
#9  0x012ead5c in gfxSkipChars::TakeFrom (this=0xbfff5f1c, aSkipCharsBuilder=0xbfff6f60) at ../../dist/include/thebes/gfxSkipChars.h:152
No locals.
#10 0x012e48fe in BuildTextRunsScanner::BuildTextRunForFrames (this=0xbfff8320, aTextBuffer=0xbfff7280) at nsTextFrameThebes.cpp:1713
        anySmallcapsStyle = 0
        textBreakPoints = {<nsTArray<int>> = {<nsTArray_base> = {static sEmptyHdr = {mLength = 0, mCapacity = 0, mIsAutoArray = 0},
              mHdr = 0xbfff7150}, <No data fields>},
          mAutoBuf = "\001\000\000\000\062\000\000\200\000\000\000\000\220z\377\277\354x\377\277\065\000\000\000\066\000\000\000\000\000\000\000\b\000\000\000\260q\377\277\254q\377\277\220q\377\277\000\202\066\260\030V\241\265\b@q\267\066\000\000\000\240\321\377\263\270\321\377\263\000\000\000\000\b\000\000\000\001\000\000\000\000\000\000\000\b\000\000\000\b\000\000\000\000\000\000\000\304i\005\255\b\000\000\000$\301 \255\364\017\274\001\240\321\377\263\b\000\000\000\254y\377\277\201E\225\001\354x\377\277\240\321\377\263\000\000\000\000\036\352\216\001\000\000\000\000\200g/\255\220z\377\277xr\377\277\256\371\247\001\000\000\000\000\220z\377\277(;\260\001\000\000\000\000\354x\377\277\254r\377\277\364\017\274\001tr\377\277\002\000\000\000<r\377\277"}
        currentTransformedTextOffset = 1
        finalUserData = 0xad2037cc
        userDataToDestroy = 0x0
        nextBreakIndex = 2904569804
        firstFrame = 0xad2037cc
        builder = {mBuffer = {<nsTArray<unsigned char>> = {<nsTArray_base> = {static sEmptyHdr = {mLength = 0, mCapacity = 0, mIsAutoArray = 0},
                mHdr = 0xbfff6f64}, <No data fields>},
            mAutoBuf = "\002\000\000\000\000\001\000\200\001\001\377\277\223\200\223\001\027m\271\000#\000\000\000\031\201\271\000\364\017\274\001<\000\000\000\000\000\000\000\274p\377\277\347\063\225\001\027m\271\000\324\302\355\267\031\201\271\000\256^\005\b@\300\355\267\240\246z\267\004\000\000\000\364\257\005\b\000@\006\255\000\000\000\255\fp\377\277\064u\005\b@\300\355\267\000\000\002\000\320o\377\277\000\000\000\000\062\000\000\200\000\000\000\000[]\005\b\225\351\216\001\240D\006\255\374\301\355\267 \000\000\000\217\350\216\001$p\377\277\002\000\000\000\274p\377\277\225\351\216\001\f\203\377\277\370\202\377\277,p\377\277\000\000\000\000\f\203\377\277\370\202\377\277lp\377\277\000\000\000\000\370\202\377\277\004\000\000\000\002\000\000\000\364\017\274\001,\203\377\277\000\000\000\000lp\377\277_\256.\001,\203\377\277\000\000\000\000\000\000\000\000\225\351\216\001\004", '\000' <repeats 11 times>"\217, \350\216\001\240\201\37---Type <return> to continue, or q <return> to quit---

After much try-and-error attempts, and also thoughts if my laptop’s memory wasn’t faulty or if the shared libraries on my disk weren’t somehow corrupted, I was finally able to track down the cause of this abnormal behavior:

BUG: The Security Device which the Siemens HiPath SIcurity Card API provided. You can read here why I use it.

The problem started somewhere around Firefox version 3.5.5 and later. If the security device dongle/card is not plugged in your computer, Firefox crashes at random pages.

The resolution
Create a second Firefox profile and install the Security Device only there, leaving the default Firefox profile with no Security Device capabilities. Thus if you want to use your online banking, you would need to close Firefox and then start it using the second profile. It’s not that bad, if you are a personal user like me who performs bank transactions relatively rarely.

The MozillaZine Knowledge Base has an excellent article about Firefox Profile Manager.

Hard disks have a typical block size of 512 bytes. LVM on the other hand creates its block devices with a block size of 4096 bytes. So it’s easy to get confused – even if you know that disks should be tested with blocks of 512 bytes, you shouldn’t test LVM block devices with a 512-bytes but with a 4096-bytes block size.

What happens if you make a write performance test by writing directly on the raw block device and you use the wrong bytes size (bs) option?

If you look at the “iostat” statistics, they will show lots of read requests too, when you are only writing. This is not what is expected when you do only writing.
The problem comes by the fact that when you are not using the proper block size for the raw block device, instead of writing whole blocks, you are writing partial blocks. This is however physically not possible – the block device can only write one whole block at a time. In order to update the data in only a part of a block, this block needs to be read back first, then modified with the new partial data in memory and finally written back as a whole block.

The total performance drop is about 3 times on the systems I tested. I’ve tested this on some hard disks and on an Areca RAID-6 volume.

So what’s the lesson here?

When you do sequential write performance tests with “dd” directly on the raw block device, make sure that you use the proper bytes size option, and verify that during the tests you see only write requests in the “iostat” statistics.

Physical hard disk example:

# Here is a bad example for a hard disk device
dd if=/dev/zero of=/dev/sdb1 bs=256 count=5000000

# Here is the proper usage, because /dev/sda physical block size is 512 bytes
dd if=/dev/zero of=/dev/sdb1 bs=512 count=5000000

LVM block device example:

# Another bad example, this time for an LVM block device
dd if=/dev/zero of=/dev/sdb-vol/test bs=512 count=1000000

# Here is the proper usage, because the LVM block size is 4096 bytes
dd if=/dev/zero of=/dev/sdb-vol/test bs=4k count=1000000

Understanding the “iostat” output during a “dd” test:

Here is what “iostat” displays when you are not using the proper bytes size option (lots of read “r/s” and “rsec/s” requests):

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sdb               0.00  5867.40 3573.20   46.40 28585.60 47310.40 20.97   110.38   30.61   0.28 100.00
sdb1              0.00     0.00    0.00    0.00     0.00     0.00 0.00     0.00    0.00   0.00   0.00
sdb2              0.00  5867.40 3572.80   46.40 28582.40 47310.40 20.97   110.38   30.61   0.28 100.00
dm-2              0.00     0.00 3572.80 5913.80 28582.40 47310.40 8.00 13850.92 1465.43   0.11 100.00

Here is what it should display (no read “r/s” or “rsec/s” requests at all):

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sdb               0.00 16510.00    0.00  128.60     0.00 131686.40 1024.00   107.82  840.32   7.78 100.00
sdb1              0.00     0.00    0.00    0.00     0.00     0.00 0.00     0.00    0.00   0.00   0.00
sdb2              0.00 16510.00    0.00  128.60     0.00 131686.40 1024.00   107.82  840.32   7.78 100.00
dm-2              0.00     0.00    0.00 16640.00     0.00 133120.00 8.00 13674.86  823.73   0.06 100.00

How to be safe?

Fortunately, file systems are smart enough and pay attention to the block size of the block devices they were mounted on. So if you do a “dd” write performance test and write to a file, you should be fine. Though in this case there are some other complications like journaling, commit intervals, barriers, mount options, etc.

• 30% discount for the US ICDSoft site
• 30% discount for the German ICDSoft site
• 30% discount for the European also Germany-based ICDSoft site

No need to thank me, you are welcome…

Hier ist meine bisherige positive Erfahrung mit Deutschen Hosting Firmen:

1. ICDSoft für Webhosting:
   • Vorteile: Tätig seit 1999 mit sehr guten Referenzen von Kunden weltweit, ausgezeichnete Hardware, 15-Minuten-Reaktion des Supports auf technischen Anfragen, tägliche Backups, gute Rabatte für Reseller und Kunden mit mehreren Kontos.
   • Nachteile: Das erste Jahr ist 20% teurer (30% Rabattmöglichkeiten hier). Doch gibt es eine bedingungslose 100-Tage Geld-Zurück-Garantie, deswegen können Sie sich risikofrei in den anspruchsvollen Diensten selbst überzeugen, oder enttäuschen.
2. 1&1 Deutschland für VPS und Dedicated Server:
   • Vorteile: Am Markt seit vielen Jahren, sehr berühmt, bietet alle Typen von Hosting-Diensten. Ich habe selbst einige Male ihre VPS/Dedicated Server Plans benutzt und bin sehr zufrieden mit den Preisen und der Qualität. Support ist verhältnismäßig gut. Software und Hardware sind perfekt.
   • Nachteile: 1&1 Deutschland arbeitet nur mit deutschen Bürgern. Falls Sie aus Bulgarien zum Beispiel sind, dann sind Sie nicht erlaubt, ein Konto bei 1&1 Deutschland zu haben. Webhosting ist zu billig.

Beide Firmen verfügen über Rechenzentren nicht nur in Europa, aber auch in den USA – ICDSoft, 1&1. ICDSoft hat Rechenzentren auch in Hong Kong und Bulgarien, wobei 1&1 – in Großbritannien, Frankreich, Österreich und Spanien.

Natürlich habe ich nicht nur positive, aber auch negative Erfahrung mit Deutschen Hosting Firmen. Ihre Namen nenne ich nicht, aber beschreibe kurz die Probleme:

• Firma A: Ich hatte einen Domain-Namen damit; Support antwortete in 3-4 Tage und sehr oft nur als wir am Telefon gesprochen haben.
• Firma B: Ich hatte ein VPS damit; zu viele Kunden auf einem einzelnen Server, zu alte System-Software, nur telefonisches Support.
• Firma C: Ich habe ein Audit der Sicherheit gemacht, da ein Freund mich sein Konto gegeben hat; in zwei Stunden war ich “root” am Server…

Bitte merken Sie zwei Dinge hier – diese Ratschläge reflektieren meine eigene (begrenzte) Erfahrung mit der Deutschen Markt von Hosting-Diensten. Ich bin ein Angestellter von ICDSoft seit 2003 und das hat ein Einfluss auf meine Meinung – von einer Seite bin ich ein bisschen befangen, aus der anderen Seite siehe ich die Prozesse in der Firma aus einer inneren Perspektive und bin 100% sicher im alles, was ich gesagt habe. Das hier ist meine personale Meinung.

A new type of device-mapper was introduced recently in the Linux kernel 2.6.31 – the request-based device-mapper. According to the Linux Kernel Newbies changelog for 2.6.31, there is a commit which does “Prepare for request based option”.

The issue is actually not in the new request-based DM option, which is to be used only for multipath block devices. The problem is that when you create a regular LVM device on kernels 2.6.31+, the DM device itself has I/O scheduler parameters. So does the underlying block device on top of which you created the LVM. Thus we are having two I/O schedulers in the path from the LVM device to the physical storage.

According to the author of the kernel patches for the request-based DM device, Kiyoshi Ueda, for a bio-based DM device, only the underlying device’s scheduler should affect performance. This is what my tests shown too, therefore there is no discrepancy.

Let me summarize this:

• If you are *not* using multipath block devices in your DM/LVM setup, then only the underlying device’s scheduler (i.e. “/sys/block/sda/queue/scheduler”) takes effect. This applies for the trivial LVM setup which many of us used for years.
• If you are using a multipath DM/LVM setup, then only the DM device’s scheduler (i.e. “/sys/block/dm-0/queue/scheduler”) takes effect.

References:

• Request-based Device-mapper multipath and Dynamic load balancing PDF paper by Kiyoshi Ueda, Jun’ichi Nomura, and Mike Christie. You can also download my copy of this PDF.
• Using Device-Mapper Multipath by RedHat.

In order to have a KVM-Qemu management console, you should start KVM with something like:

-monitor telnet:127.0.0.1:3010,server,nowait,ipv4

See the official documentation of Qemu for more details and also the man page of qemu-kvm (unofficial mirror).

Once you have it set up, you can then telnet to the management console and review the available commands:

famzah@famzahpc:~$ telnet localhost 3010
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

QEMU 0.11.0 monitor - type 'help' for more information
(qemu) help

Changing the ISO image of a virtual CDROM drive is quite easy:

• First review what the current status of the drives is:

  (qemu) info block
  virtio0: type=hd removable=0 file=/dev/sdb-vol/win7 ro=0 drv=host_device encrypted=0
  ide0-cd0: type=cdrom removable=1 locked=0 file=/shared/win7-eval.iso ro=0 drv=raw encrypted=0
  ide1-cd0: type=cdrom removable=1 locked=0 [not inserted]
  

• Then change the mounted ISO image in the CDROM drive on the fly:

  (qemu) change ide1-cd0 /shared/win-virtio-drivers.iso
  

• Double-check that the changes took effect. KVM-Qemu will not issue an error message in case something went wrong (duh!):

  (qemu) info block
  virtio0: type=hd removable=0 file=/dev/sdb-vol/win7 ro=0 drv=host_device encrypted=0
  ide0-cd0: type=cdrom removable=1 locked=0 file=/shared/win7-eval.iso ro=0 drv=raw encrypted=0
  ide1-cd0: type=cdrom removable=1 locked=0 file=/shared/win-virtio-drivers.iso ro=1 drv=raw encrypted=0
  

Use the “help” command to review the other powerful commands which you can use to tune and debug your running KVM guest (“info”, “migrate” and “system_reset” seem like interesting candidates).

Download locations follow:

• Both Virtio network and storage drivers for Windows (4.0M)
• Virtio network drivers for Windows (2.8M)
• Virtio storage drivers for Windows (1.6M)

These are static ISO images, and I’ve built them by downloading the ZIP sources dated 24.09.2009 from the official WindowsGuestDrivers KVM page and then converting them to ISO image files by using K3b.

Note that Virtio provides noticeably faster disk and network access.

Please review the official page of Virtio for sample KVM command line arguments which set up Virtio storage and network devices. You may notice that there is an (undocumented) parameter “boot=on” specified for the “-drive” option. This “boot=on” parameter is vital for the “-drive” option, or else Windows 7 won’t like your drive and won’t install on it.

Note about Virtio storage drives and the Windows 7 installer
I was able to install Windows 7 right from the start by using a Virtio storage drive within the KVM guest. At first the Windows installer didn’t see the Virtio disk at all but there is an option to install additional storage drivers. I installed the Virtio Windows drivers from the above ISO images, the Windows installer detected the Virtio storage disk properly and everything went quite smooth afterwards.

Resources:

• Preview of Redhat 5.4 Windows Virtio Drivers Part 1
• Official WindowsGuestDrivers KVM page. The drivers are provided by the RedHat folks.
• Comprehensive information about KVM and the DOS/Windows family. In German, but you may try Google translate to read it if you don’t read German well.

Contempt HTML list, original

And here is how a designer fellow helped me change it:

Contempt HTML list, modified

The differences are as follows:

• The indentation of the non-first lines in the list paragraph are aligned with the first line.
• The list marker is not the symbol “o” but the original circle symbol provided by browsers.
• The spacing between list paragraphs is a bit bigger, in order to improve the readability.

If you like the modified version better, you need to navigate to Appearance->Edit CSS and add the following CSS code there:

.entry ul li:before,#sidebar ul ul li:before {
	content:"";
}

body .entry ul {
	list-style-position:outside!important;
	list-style-type:circle!important;
	text-indent:0!important;
}

body .entry ul li {
	margin-bottom:13px;
}

You can also read my other post if you like to Make WordPress.com Contempt theme layout wider.

• Купих си онлайн два VIP билета за концерта на Милена по случай 25 години на сцена. Цената им беше 50 лева и са VIP, защото има запазени седящи места за всеки билет.
• Отидох на концерта и започнаха проблемите.
• Само на външния вход пишеше “VIP вход”. След като влезеш вътре, нямаш никаква идея от кои входове влизат притежателите на “VIP” билети.
• С питане, след като два пъти объркахме на коя (не много дълга) опашка да се наредим, най-накрая влязохме през правилния вътрешен вход. Имало отредени сектори, но никъде нямаше табели кой сектор къде се намира физически. Ние бяхме сектор “B”, ред 11, места 4 и 5.
• Намерихме бързо ред 11, имаше достатъчно стюарди. Една дама ни упъти към нашия ред, но се оказа, че има проблем – други хора, с билети за същия ред и същите места вече се бяха настанили там. И нямаха намерение да се местят. Разбираемо.
• След кратко суетене се оказа, че билетите за този ред са дублирани. Часът е около 19:00.
• Вече настана истински смут, надигна се и леко недоволство. Една агресивна жена безцеремонно обяви, че има дискова херния и не може да стои права. На концерта на Мадона също имало някакъв проблем с билетите и стояла права, сега нямала никакво намерение да стои права. Скара се с охраната, вдигна врява и я настаниха на ред 12, където все още имаше няколко свободни места.
• Концертът започна. Ние чакаме прави да се разберем какво правим. Гледам, че има доста свободни места в “ложата”.
• Дойде Светослав Седлоев, мениджър в Тикетпро. Вече е 19:30.
• Светослав Седлоев ни предложи да ни вземе билетите и да се разберем след концерта на касата как ще ни обезщети. Взема ни билетите и ни даде някакви билети-бланки на Тикетпро.
• В 19:55 стюардите ни предложиха да седнем на друг ред, където имало достатъчно свободни места.
• Останахме там където бяхме и се изкефихме на концерта, беше жесток!
• След концерта потърсих г-н Седлоев на касата – такава обаче вече нямаше, всичко беше събрано и от Тикетпро нямаше и помен.

Предположих, че може би е имал предвид онази, другата каса. Затова писах до office@ticketpro.bg, с молба да ме свържат с него. Ето какво си разменихме по е-мейл с него:

Иван Захариев:
Здравейте,

бихте ли ме свързали със Светослав Седлоев по е-мейл?
С него имаме започнат разговор от концерта на Милена във връзка с дублираните билети.

Благодаря.

---

Светослав Седлоев:
Здравейте!
Радвам се, че успяхте да се свържете с мен. Ще ви помоля да ми дадете телефон за връзка, за да ви се обадя и да намерим решение на конфузната ситуация от съботната вечер.

---

Иван Захариев:
Skype или е-мейл е по-добре, съжалявам за упорството по този въпрос, но предпочитам каквото си говорим да го имам черно на бяло.

Какви са опциите за решение на ситуацията според Вас?

---

Светослав Седлоев:
При въвеждането на редовете, запазени за ВИП Зоната е допусната техническа грешка и ред 19 е бил въведен от системния администратор под номер 11. Така всички клиенти закупили билет за ред 19 са получили билет с отпечатан ред 11 на него. От там се е получил и дублажът.
Това, което мога да направя е да Ви вьрна доплатената от Вас сума за ВИП зона (20 лв. на билет), или да Ви предложа билети за следващ концерт по ваш избор, който СМЕ ще организира в зала Универсиада.

---

Иван Захариев:
От това следва ли, че за ред 19 всъщност не са отпечатани никакви билети, т.е. по време на концерта ред 19 е бил празен?

---

Светослав Седлоев:
Става въпрос за ред 19, секция В, от страната на входа, на който се срещнахме.
В момента в който открихме причината и успях да достигна повторно до мястото (около 45 мин. след началото на концерта) на три четвърти от 19 ред имаше свободни места, които можеха да се ползват за настаняване на хората с дублирани билети и където успяхме да настаним част от тях.
За съжаление не можах да ви открия в тълпата, за което повторно моля за извинение.

---

Иван Захариев:
Приемам извинението.

Всъщност Ваши колеги успяха да ме намерят по време на концерта, в 19:55.

Компенсацията няма да я коментирам; само ще дам като пример едно средно-статистическо заведение в Щатите – ако намериш боклук в храната или просто не ти харесва, няма вариант да ти върнат парите само за част от това, което не си изял Сравнението ми може и да не е на място, но някакси веднага точно това ми хрумна. Както и да е.

Последен въпрос и Ви оставям да вършите някаква по-полезна работа: Кой поставя указателните табели пред и в залата? Примерно на входа пишеше “VIP вход”, но нямаше никакви други табели – кой сектор на къде е и т.н.

Чие задължение беше това?

П.П. Предполагам нямате нищо против да публикувам разговора ни в Интернет пространството? Ще Ви дам линк, за да можете да коментирате лично, ако имате желание.

---

Светослав Седлоев:
Това е задължение на охранителната фирма, която изгражда огражденията пред и в залата, и на тикетинг компанията, която трябва да постави указателните табели.
Поради факта, че промотърът за първи път изисква да се отцепва част от трибуните за ВИП Зона, без самите трибуни да са пригодени за това (с отделен, независим вход към тази зона) нямаше как да канализираме и отделим потока на гостите с ВИП билети. За това местата с номера бяха отцепени с предупредитена лента с надписи “ВИП Зона” вътре в самата зала и охраната и стюардите бяха концентрирани около нея. По този начин гарантирахме,че до зоната ще може да се стигне от всички подстъпи (двата входа на партера и двата на първи етаж), без да се образуват опашки.

Не мога да ви забранявам да публикувате каквото и да било и не искам да бягам от отговорност. Напротив, мисля, че дискусията е полезна и основателните критики, които търпим ще ни помогнат да подобрим обслужването си за в бъдеще.

Оставам на Ваше разположение.

А аз оставям на всеки да си прави изводи за бизнеса в България на база фактите, които съм предоставил.