What Are You Doing Right Now
-
Wondering why clicking the return to last place button on this thread never take me anywhere near the last place I looked at.
Definitely appears that some work to still do on really long threads and their management.
-
@Dashrender said:
Wondering why clicking the return to last place button on this thread never take me anywhere near the last place I looked at.
Definitely appears that some work to still do on really long threads and their management.
Hmm, it works generally fine for me. The only time I have this issue is when I am at a different computer.
-
@coliver said:
@Dashrender said:
Wondering why clicking the return to last place button on this thread never take me anywhere near the last place I looked at.
Definitely appears that some work to still do on really long threads and their management.
Hmm, it works generally fine for me. The only time I have this issue is when I am at a different computer.
This makes me wonder - is it cookie based or logged on server side cached info based?
-
@Dashrender said:
@coliver said:
@Dashrender said:
Wondering why clicking the return to last place button on this thread never take me anywhere near the last place I looked at.
Definitely appears that some work to still do on really long threads and their management.
Hmm, it works generally fine for me. The only time I have this issue is when I am at a different computer.
This makes me wonder - is it cookie based or logged on server side cached info based?
I assume it is cookie/local cache based. When clearing your browsing history the last viewed things reset.
-
<redacted>
-
It's local. Last viewed place is always different on my different devices.
-
Good morning. Finally getting rolling around here. Was kept up late playing Broken Age. That game is pretty awesome.
-
Going to be a long day here. As needed support customer has CryptoWall....
-
@Minion-Queen Yuck. Have fun with that
-
@Minion-Queen said:
Going to be a long day here. As needed support customer has CryptoWall....
Thankfully a customer that calls us in to clean up for their internal IT, not one that uses us for managed services. Not our server, not our accounts, not our compromise
-
-
I need a place to collect all of these horror stories of the inverted pyramid with a SAN killing people. The number of times that firmware takes out the magic "dual controller" SAN is unbelievable...
http://community.spiceworks.com/topic/1028886-dell-md3200i-firmware-issue
-
@scottalanmiller said:
I need a place to collect all of these horror stories of the inverted pyramid with a SAN killing people. The number of times that firmware takes out the magic "dual controller" SAN is unbelievable...
http://community.spiceworks.com/topic/1028886-dell-md3200i-firmware-issue
Haha... when we deploy our VNXe-3300 dual-controller wonder-box (we were told it would do everything up-to but not including slice and toast bread) at my last job we were testing it out and the first thing I did was update it to the newest firmware... the firmware was applied correctly to one controller but not the other and without both the entire unit refused to work. Thankfully we weren't in production or that would have been a fun 24 hours... To EMC's credit we received the replacement controller at 6AM the next morning.
-
In my mind, a single storage device, no matter how many controllers, power supplies, or motherboards it has in the same chasis is still a NAS.
If somebody tries to sell me a SAN, it will be at least 2 devices mirrored using the network.
-
@coliver said:
@scottalanmiller said:
I need a place to collect all of these horror stories of the inverted pyramid with a SAN killing people. The number of times that firmware takes out the magic "dual controller" SAN is unbelievable...
http://community.spiceworks.com/topic/1028886-dell-md3200i-firmware-issue
Haha... when we deploy our VNXe-3300 dual-controller wonder-box (we were told it would do everything up-to but not including slice and toast bread) at my last job we were testing it out and the first thing I did was update it to the newest firmware... the firmware was applied correctly to one controller but not the other and without both the entire unit refused to work. Thankfully we weren't in production or that would have been a fun 24 hours... To EMC's credit we received the replacement controller at 6AM the next morning.
6am was how many hours later for a "never fail" system that failed on the most basic task?
-
@dafyre said:
In my mind, a single storage device, no matter how many controllers, power supplies, or motherboards it has in the same chasis is still a NAS.
If somebody tries to sell me a SAN, it will be at least 2 devices mirrored using the network.
No, that is completely the wrong use of NAS and SAN. Neither mean anything related to this at all. SAN means block storage, NAS means file storage. Neither implies anything beyond that. A USB external SATA drive is a SAN. And there are NAS that are huge clusters. SAN never implies "good" or "better than", there is nothing like that in the name.
SAN can be less than a NAS because a NAS requires a computer and a SAN only requires a NIC, but it is only that a SAN can be lower than a NAS because a NAS can't go that low. But if you are feeling that the term SAN implies some kind of reliability, you have been set up to be very mislead.
-
@scottalanmiller said:
@coliver said:
@scottalanmiller said:
I need a place to collect all of these horror stories of the inverted pyramid with a SAN killing people. The number of times that firmware takes out the magic "dual controller" SAN is unbelievable...
http://community.spiceworks.com/topic/1028886-dell-md3200i-firmware-issue
Haha... when we deploy our VNXe-3300 dual-controller wonder-box (we were told it would do everything up-to but not including slice and toast bread) at my last job we were testing it out and the first thing I did was update it to the newest firmware... the firmware was applied correctly to one controller but not the other and without both the entire unit refused to work. Thankfully we weren't in production or that would have been a fun 24 hours... To EMC's credit we received the replacement controller at 6AM the next morning.
6am was how many hours later for a "never fail" system that failed on the most basic task?
~18 hours. It took them ~3 hours to determine the controller was bricked (even though I told them it was when we started the support call). My manager at the time didn't really understand what was going on... so I caught all kinds of hell for breaking it.
-
@coliver said:
@scottalanmiller said:
@coliver said:
@scottalanmiller said:
I need a place to collect all of these horror stories of the inverted pyramid with a SAN killing people. The number of times that firmware takes out the magic "dual controller" SAN is unbelievable...
http://community.spiceworks.com/topic/1028886-dell-md3200i-firmware-issue
Haha... when we deploy our VNXe-3300 dual-controller wonder-box (we were told it would do everything up-to but not including slice and toast bread) at my last job we were testing it out and the first thing I did was update it to the newest firmware... the firmware was applied correctly to one controller but not the other and without both the entire unit refused to work. Thankfully we weren't in production or that would have been a fun 24 hours... To EMC's credit we received the replacement controller at 6AM the next morning.
6am was how many hours later for a "never fail" system that failed on the most basic task?
~18 hours. It took them ~3 hours to determine the controller was bricked (even though I told them it was when we started the support call). My manager at the time didn't really understand what was going on... so I caught all kinds of hell for breaking it.
Eighteen hours to replace a failed SAN? That's crazy. HP servers are four to six hours for parts replacement SLA!! Same with Dell. This is why I fear SANs, is there any SAN vendor that treats their SAN as even a fraction as critical as a server vendors treats their servers?
If this is the kind of care that goes into support, how much care goes into the engineering?
-
Move this conversation to a Thread! Good information there.
-
Getting you a replacement at 6am wasn't really to their credit, it was really to their shame. HP or Dell would have been embarrassed by that kind of SLA.
