Language Selection

English French German Italian Portuguese Spanish

Tiny drives set for space boost

Filed under
Hardware

Hitachi has said it can fit 230 gigabits of data per square inch on a disk using "perpendicular recording"
The storage industry currently makes hard drives using longitudinal recording, which is reaching its limit.

Hitachi's work means we could see one-inch hard drives holding 60Gb instead of up to 10Gb currently.

One terabyte is the equivalent of 1,000Gb - enough to hold 240,000 songs at the standard encoding rate for digital music files.

Perpendicular recording was pioneered by the late 19th century work of Danish scientist Valdemar Poulsen, who demonstrated magnetic recording with his telegraphone.

He is widely thought to have been the first to experiment with magnetically recorded sound using perpendicular methods.

The technology industry wants smaller hard drives that hold more information to go into all kinds of digital devices like portable music players.

As storage prices come down and data capacity increases, more portable devices are coming out with built-in hard drives, such as music and media players from Apple, Creative Labs, Archos, iRiver and others.

"Consumers' demand for storing more data on smaller devices has provided a strong impetus for us to pursue perpendicular recording with a greater sense of urgency," he said.

But there are limits to this process, which are fast being approached. The biggest problem hard drive technology faces is what is called the superparamagnetic effect.

This is when microscopic magnetic grains on the disk get so tiny that they interfere with one another. Often this results in reduced ability to hold their magnetic orientations. When this happens, bits of data can become corrupt.

Perpendicular recording methods overcomes the problem and aligns data bits vertically, perpendicular to the disk.

Hitachi said it would start using perpendicular recording in the next generation of its products, in 2007. Over the next five to seven years, it said, perpendicular recording could mean a 10-fold increase in data densities over longitudinal recording.

This means its one-inch drive technology could store 60Gb of data.

Full Story.

Seagate also in HD stakes with its own perpendicular recording hard drive. Hitachi's first drives to use perpendicular recording will use 2.5-inch platters, while Toshiba plans 1.8-inch drives. Seagate quietly delivered its first samples at the end of 2004.

More in Tux Machines

Today in Techrights

Fedora: Anaconda Improvements, Greenboot, Fedora Scientific Vagrant Boxes and Abhishek

  • Anaconda improvements in Fedora 28
    Fedora 28 was released last month, and the major update brought with it a raft of new features for the Fedora Installer (Anaconda). Like Fedora, Anaconda is a dynamic software project with new features and updates every release. Some changes are user visible, while others happen under the hood — making Anaconda more robust and prepared for future improvements.
  • Lorbus: Introducing: greenboot
    Not too long ago, I applied to Google Summer of Code for the student scholarship position together with a Fedora project ideated by Peter Robinson, who is the principal IoT architect at Red Hat, named Fedora IoT: Atomic Host Upgrade Daemon. As you may be guessing by now, I was very fortunate and the proposal was accepted! The coding phase started on the 14th of May and in this blog post I’ll try to give a little insight into my first month working on the project.
  • Pre-release Fedora Scientific Vagrant Boxes
    I am very excited to share that sometime back the Fedora project gave the go ahead on my idea of making Fedora Scientific available as Vagrant boxes starting with Fedora 29. This basically means (I think) that using Fedora Scientific in a virtual machine is even easier.
  • [Week 5] GSoC Status Report for Fedora App: Abhishek

Red Hat News

  • An Open Source Load Balancer for OpenShift
    A highly-available deployment of OpenShift needs at least two load balancers: One to load balance the control plane (the master API endpoints) and one for the data plane (the application routers). In most on-premise deployments, we use appliance-based load balancers (such as F5 or Netscaler).
  • Red Hat Beefs Up Platform as a Service Suite
    Red Hat has begun shipping Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service (iPaaS) offering, Fuse Online. With Fuse 7, the vendor says expanding its integration capabilities natively to Red Hat OpenShift Container Platform, an enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • Red Hat ‘Fuses’ Low Code Development and Data Integration
    Red Hat, a provider of open source solutions, has announced Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service offering, Fuse Online. With Fuse 7, Red Hat is expanding its integration capabilities natively to Red Hat OpenShift Container Platform, a comprehensive enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • The GPL cooperation commitment and Red Hat projects
    As of today, all new Red Hat-initiated open source projects that opt to use GPLv2 or LGPLv2.1 will be expected to supplement the license with the cure commitment language of GPLv3. The cure language will live in a file in the project source tree and will function as an additional permission extended to users from the start. This is the latest development in an ongoing initiative within the open source community to promote predictability and stability in enforcement of GPL-family licenses. The “automatic termination” provision in GPLv2 and LGPLv2.x is often interpreted as terminating the license upon noncompliance without a grace period or other opportunity to correct the error in compliance. When the Free Software Foundation released GPLv2 in 1991, it held nearly all GPL-licensed copyrights, in part a consequence of the copyright assignment policy then in place for GNU project contributions. Long after the Linux kernel and many other non-GNU projects began to adopt the GPL and LGPL, the FSF was still the only copyright holder regularly engaged in license enforcement. Under those conditions, the automatic termination feature of GPLv2 section 4 may have seemed an appropriate means of encouraging license compliance.
  • Monness Believes Red Hat (NYSE: RHT) Still Has Room to Grow
  • Comparing Red Hat (RHT) & Autoweb (AUTO)
  • As Red Hat (RHT) Share Value Rose, Calamos Advisors Upped Its Position by $300,831; Chilton Capital Management Increases Stake in Equinix (EQIX)
  • Blair William & Co. IL Buys 23,279 Shares of Red Hat Inc (RHT)

Total War: WARHAMMER