My Yearly VPS had been suspended because the data transfer was used up.
I had send ticket to fibervolt, Two weeks have passed ,no reply.
And the HDD has a problem, the speed has been very slow, less than 1MB / S.
@WhiteLabelHosting [email protected]:~# dd if=/dev/zero of=test bs=64k count=4k oflag=dsync
272+0 records in
272+0 records out
17825792 bytes (18 MB) copied, 58.972 s, 302 kB/s
[email protected]:~# dd if=/dev/zero of=test bs=64k count=4k oflag=dsync
2714+0 records in
2714+0 records out
177864704 bytes (178 MB) copied, 198.897 s, 894 kB/s
This is my previous test results.
My name is Alex Bateman and I am a co-founder of http://www.fibervolt.com/. The situation that happened with sunsea has been brought to my attention and I agree it is totally unacceptable. I find it ludicrous that it took 2 weeks to get a support response and I profusely apologize. I am working with the support department to make sure an oversight like this does not happen again. To make up for your inconvenience please email me personally at abateman[at]fibervolt.com so proper compensation can be made.
Regarding the HDD issue – As of now there are no apparent technical issues with Fiber Volt’s HDD speeds but I have technicians looking into the issue to make sure everything is running up to par.
I would also like to clarify the HDD speeds. When sunsea ran the HDD speed tests, our servers may have been experiencing some technical issues. We have executed numerous tests and our HDD speeds are now running up to their proper specifications as shown below.
[email protected]*****:~# dd if=/dev/zero of=test bs=64k count=4k conv=fdatasync
4096+0 records in
4096+0 records out
268435456 bytes (268 MB) copied, 4.7742 seconds, 56.2 MB/s
Comments
+1
Sounds like the node has just been abandoned and left to fend for itself.
@WhiteLabelHosting
[email protected]:~# dd if=/dev/zero of=test bs=64k count=4k oflag=dsync
272+0 records in
272+0 records out
17825792 bytes (18 MB) copied, 58.972 s, 302 kB/s
[email protected]:~# dd if=/dev/zero of=test bs=64k count=4k oflag=dsync
2714+0 records in
2714+0 records out
177864704 bytes (178 MB) copied, 198.897 s, 894 kB/s
This is my previous test results.
:O!
0_o
drop the oflag=dsync and use conv=fdatasync as everyone else
@rds100 Now has been suspended ! Can't test.
And use conv=fdatasync not fully reflect the hard drive performance, right?
Well, most people use conv=fdatasync when doing HDD speedtests, so it is easier to compare results when people are using the same test.
@rds100 The HDD speed is not important, important is when to restore my machine.
Hope not Dead Pool !
I only used 3 months.
Heh, some of us have lose several yearly ones... n_n
But good luck
@yomero Can not be so ah, my VPS can not be used after six months!
Hello,
My name is Alex Bateman and I am a co-founder of http://www.fibervolt.com/. The situation that happened with sunsea has been brought to my attention and I agree it is totally unacceptable. I find it ludicrous that it took 2 weeks to get a support response and I profusely apologize. I am working with the support department to make sure an oversight like this does not happen again. To make up for your inconvenience please email me personally at abateman[at]fibervolt.com so proper compensation can be made.
Regarding the HDD issue – As of now there are no apparent technical issues with Fiber Volt’s HDD speeds but I have technicians looking into the issue to make sure everything is running up to par.
I would also like to clarify the HDD speeds. When sunsea ran the HDD speed tests, our servers may have been experiencing some technical issues. We have executed numerous tests and our HDD speeds are now running up to their proper specifications as shown below.
[email protected]*****:~# dd if=/dev/zero of=test bs=64k count=4k conv=fdatasync
4096+0 records in
4096+0 records out
268435456 bytes (268 MB) copied, 4.7742 seconds, 56.2 MB/s
Again, I do sincerely apologize.