Language Selection

English French German Italian Portuguese Spanish

The Future of Linux File Systems and Volume Managers

Filed under
Linux

This is a topic I can be extremely passionate about. I enjoy working with data storage technologies and especially enjoy topics on file systems/volume managers. It is true when they say, “Once you get into data storage it is difficult getting out.” That is because the industry is fascinating. Working with enterprise class equipment is an experience that cannot be forgotten. We are talking about rack mountable blade servers, RAID and JBOD storage arrays working with SCSI-based technologies such as Fibre Channel, SAS (SATA under the SAS), protocol analyzers and more. And that is only the hardware. Step into the software aspect of it such as High Availability, i.e. Clustering, Dynamic Multipathing, Load Balancing, things tend to get a bit more exciting.

Over the course of time, I have had significant exposure to this industry in both permanent and part-time consulting roles. With that, I have also had a significant amount of exposure with UNIX, GNU/Linux and Microsoft Windows running in these environments. With this exposure I have seen what has been efficient and what has not. It is my personal opinion that both UNIX and GNU/Linux are more well equipped to cater to enterprise market although I am still concerned for the future of GNU/Linux with regards to one specific area and that is storage management.

The Dilemma

To date, I don’t think I have ever seen any other operating environment support so many file systems and volume managers. You name it and I can assure you that one way or another, it runs on Linux. The problem with having multiple choices of methods or applications in configuring and managing your storage is that there may come a time where you will have to toggle between multiple interfaces in order to accomplish one set of tasks.

A good example is...




More in Tux Machines

today's leftovers

'Turbo Boost Max 3.0' and Mesa 17.2.4

  • Turbo Boost Max 3.0 Support For Skylake Fixed With Linux 4.15
    The platform-drivers-x86 updates have been sent in for Linux 4.15 and include a range of improvements for Intel hardware support. One of the bigger items is support for Skylake CPUs with Turbo Boost Max 3.0.
  • Mesa 17.2.4 Graphics Stack Lands for Ubuntu 16.04 LTS and Ubuntu 17.10 Gamers
    Canonical's Timo Aaltonen reports on the availability of the Mesa 17.2.4 open-source graphics drivers stack on the X-SWAT updates PPA for Ubuntu 16.04 LTS and Ubuntu 17.10 systems. Ubuntu systems have always lagged behind the development of the Mesa 3D Graphics Library, the Linux graphics stack containing open-source drivers for Intel, AMD Radeon, and Nvidia GPUs, but they usually catch up with it through a specially crafted PPA (Personal Package Archive) repository that can be easily installed by users.

OSS Leftovers

  • The Future of Marketing Technology Is Headed for an Open-Source Revolution
  • Edging Closer – ODS Sydney
    Despite the fact that OpenStack’s mission statement has not fundamentally changed since the inception of the project in 2010, we have found many different interpretations of the technology through the years. One of them was that OpenStack would be an all-inclusive anything-as-a-service, in a striking parallel to the many different definitions the “cloud” assumed at the time. At the OpenStack Developer Summit in Sydney, we found a project that is returning to its roots: scalable Infrastructure-as-a-Service. It turns out, that resonates well with its user base.
  • Firefox Quantum Now Available on openSUSE Tumbleweed, Linux 4.14 Coming Soon
    Users of the openSUSE Tumbleweed rolling operating system can now update their computers to the latest and greatest Firefox Quantum web browser.
  • Short Delay with WordPress 4.9
    You may have heard WordPress 4.9 is out. While this seems a good improvement over 4.8, it has a new editor that uses codemirror.  So what’s the problem? Well, inside codemirror is jshint and this has that idiotic no evil license. I think this was added in by WordPress, not codemirror itself. So basically WordPress 4.9 has a file, or actually a tiny part of a file that is non-free.  I’ll now have to delay the update of WordPress to hack that piece out, which probably means removing the javascript linter. Not ideal but that’s the way things go.

Red Hat and Fedora Leftovers