Forgot your password?
typodupeerror
Data Storage

WD Announces 8TB, 10TB Helium Hard Drives 296

Posted by Soulskill
from the ballooning-storage-capacity dept.
Lucas123 writes: Western Digital's HGST subsidiary today announced it's shipping its first 8TB and the world's first 10TB helium-filled hard drive. The 3.5-in, 10TB drive also marks HGST's first foray into the use of shingled magnetic recording technology, which Seagate began using last year. Unlike standard perpendicular magnetic recording (PMR), where data tracks rest side by side, SMR overlaps the tracks on a platter like shingles on a roof, thereby allowing a higher areal density. Seagate has said SMR technology will allow it to achieve 20TB drives by 2020. That company has yet to use helium, however. HGST said its use of hermetically-sealed helium drives reduces friction among moving drive components and keeps dust out. Both drives use a 7-platter configuration with a 7200 RPM spindle speed. The company said it plans to discontinue its production of air-only drives by 2017, replacing all data center models with helium drives.

Comment: Re:Document formats... (Score 2) 579

by magamiako1 (#47699825) Attached to: Munich Reverses Course, May Ditch Linux For Microsoft
Starting with Microsoft Office 2007, the Office Open XML file formats have become the default[3] target file format of Microsoft Office.[4][5] Microsoft Office 2010 provides read support for ECMA-376, read/write support for ISO/IEC 29500 Transitional, and read support for ISO/IEC 29500 Strict.[6] Microsoft Office 2013 additionally supports both reading and writing of ISO/IEC 29500 Strict

http://en.wikipedia.org/wiki/Ooxml

Not to be confused with Open Office XML or Microsoft Office XML formats.

I didn't say Microsoft supported ALL standards, just that they support *some* standards.

Comment: Document formats... (Score 1) 579

by magamiako1 (#47699505) Attached to: Munich Reverses Course, May Ditch Linux For Microsoft
What are you talking about?<br><br>http://en.wikipedia.org/wiki/Ooxml<br>http://blogs.msdn.com/b/dmahugh/archive/2010/04/06/office-s-support-for-iso-iec-29500-strict.aspx<br>http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=61798<br><br>Microsoft supports an open document standard, standardized by the ISO, with Office and has for some time, though admittedly not "Strict" support until Office 2013.

Comment: Re:Dead as a profit source for Symantec, well, ... (Score 1, Informative) 331

by magamiako1 (#47688933) Attached to: Ask Slashdot: How Dead Is Antivirus, Exactly?
We use McAfee at work. With proper coaxing, it works pretty well and is unobtrusive--but it actually requires becoming familiar with the product and its features. It took a lot of trial and error.

One quick way you can help reduce A/V hit on a system is to remove zip file scanning during on-access scans and on-demand scans. Also, setting a file scan time limit can limit the amount of time the AV spends on one particular type of file.

Other antivirus solutions handle this a bit better, but McAfee is workable with the proper implementation.

Comment: Re:Comcast engineer here (Score 1) 224

by magamiako1 (#47636719) Attached to: The Hidden Cost of Your New Xfinity Router
AAAAAAND furthermore, in a purely technical sense IPv6 should be faster than IPv4 connectivity when it comes to routing.

Current IPv4 implementations actually do two state table tracking. Both the NAT table and the firewall's state table. In a dual stack, native configuration; only the firewall state table is required for IPv6 traffic alone; with no NAT table required. Or, in some cases, minimal NAT tables for specific devices when you wish to deploy IPv6 only and are supporting legacy devices that do not support it.

So, in theory, routing performance should be edged up a bit in IPv6 land. Also including the fact that hosts are now doing traffic fragmentation and the router's only involvement in fragmentation is sending an ICMP response (PACKET-TOO-BIG) rather than queuing and fragmenting traffic itself. Router performance should ultimately go up by quite a bit.

Comment: Re:Comcast engineer here (Score 1) 224

by magamiako1 (#47636697) Attached to: The Hidden Cost of Your New Xfinity Router
"Dual stack takes more resources and complexity."

Yes, it does take labor and sometimes duplication of effort, but it doesn't REALLY negatively impact actual routing performance for most people with the exception of situations where routing for v4 is done in ASICs and v6 is done in the CPU, where v6's performance will ultimately be slower than the equivalent in v4 traffic.

However, this is so rare of a hardware configuration these days in most cases. Modern firewalls/routers/edge devices are doing everything in software with powerful enough CPUs to do both, where the performance would be no different than the equivalent increase in IPv4 traffic. Juniper SRX devices run in this configuration (with BSD running as the base OS), and my Ubiquiti device runs a dual core CPU as well.

If you have any questions, why not talk to Comcast? They've deployed IPv6 in a dual stack configuration across nearly their entire residential network (as the OP noted here). Clearly if there were performance problems that negatively impacted the cost of scalability, they wouldn't have made that move.

Comment: Re:Comcast engineer here (Score 1) 224

by magamiako1 (#47636633) Attached to: The Hidden Cost of Your New Xfinity Router
You are hurting my head, honestly. You're so flat out wrong it's not even funny.

Nobody's saying go "v6 only". We're saying run the two in parallel. When running 'dual stack', v4 and v6 are independent short of DNS resolution where you'll often receive both A and AAAA responses and your application needs to decide which one it prefers. For sockets that aren't v6 compatible, it will just use the A response and ignore the AAAA response completely.

Just because Skype isn't currently v6 compatible should have no bearing on whether or not you actually deploy IPv6.

Go study for your CCNA.

Comment: Sigh...fucking slashdot (Score 2, Insightful) 702

by magamiako1 (#47398519) Attached to: TSA Prohibits Taking Discharged Electronic Devices Onto Planes
As another poster stated, this is only on certain international flights originating from certain countries--and in addition to that, I'm sure you can power your phone off once you've powered it on for them.

While this could be for another form of 'tracking' with cell phone tracking technologies (which exist), I feel it would be impossible to know just from cell phone identification what a person intends to do.

So I suspect it's nothing more than "Ensure that the phone is not a bomb in disguise".

What hath Bob wrought?

Working...