New storage management

While implementing the LVM plugin i came to the conclusion that the current storage management is too limited. E.g. the current datamodel does not support features like implementing a plugin that allows the user to mount a ISO as shared folder. Because i know that such a feature request will come someday i started to reimplement the datamodel and infrastructure. Now the whole storage management does not need to have any configuration, this means all data is detected during runtime, this also applies to the filesystems. If you mount a filesystem this is the first configuration entry for the whole storage management. Due this code refactoring i hope that the datamodel and backend is nearly ready for every feature. The LVM plugin is currently not finished, because of that i did not show the logical volume administration section. Experts maybe miss some features in the WebGUI, but those can use the console for that because, as i already told above, everything is done during runtime, so changes via console should be visible in the WebGUI too.

The new storage management is far from that what i have planned at the beginning: It should be easy to use. Now its a little bit more difficult for novices, but i really did not want to hear anything from special peoples around here why i did not implement it these or that way. Im ready with that, now it is like it is.

42 thoughts on “New storage management

  1. I noticed in the video that you grew the empty VM volume. What happens when you try to shrink one that cannot be shrunk with its given data?

    …before you release this (if you ever do), please setup a good forum structure as these blog-like pages are pathetic; I suggest you ax these pages completely. I’m sure you have some good forum moderators in line, as you have had a good following.
    Your work appears to be really good (let me stress, appears :-)); I still run an old FN7 that is still running strong. I won’t touch FN8 for my newer hardware for obvious reasons. I run Deb Squeeze on that.

    There’s alot that goes into a release. As I’m sure you have thought of….documentation (basic at least), proper forum setup, bug reporting, release notes, etc…

    …I wish you good luck and I hope you realize that this project will be just what the linux community has needed. Linux hardware support wins hands-down.

    …I’ll check back next month. ….and the next?


    • I noticed in the video that you grew the empty VM volume. What happens when you try to shrink one that cannot be shrunk with its given data?

      Not tested till now because the LVM plugin is still in progress.

    • Such features may be included later. I also would like to see a power feature that will shutdown the system after x minutes of doing nothing.

      – shutdown when all downloads finished

      Hard to implement it generic, depends on the software that are doing the download or you have to check the download traffic.

      – shutdown when noone is connected via dlna,samba, etc

      Hmm, sound a little bit easier.

      – shutdown when specific IPs in the local network are’nt reachable

      Could be done via ‘monit’ which is already installed.

      – shutdown when network or cpu load is under a defined level

      Another ‘monit’ job

      – shutdown when backups are finished


  2. Hi Volker,

    just curious:
    – how much Ram will be needed for decent performance (4 HHD as 2 x Raid 1, ext4). Is 512 MB enough?
    – How much space will be needed for the system partition (is a 4 GB DOM enough)? Do we need swap?

    • how much Ram will be needed for decent performance (4 HHD as 2 x Raid 1, ext4). Is 512 MB enough?

      I don’t know it. I did not have done any performance test till now because this is not necessary for my personal scenario.

      How much space will be needed for the system partition (is a 4 GB DOM enough)? Do we need swap?

      Partitioning is not available in the system setup. A harddisc is completely used for the OS. In your case the 4GiB DOM, which should be enough. I have the same DOM (Transcend) in my NAS. A swap partition is automatically created by the Debian installer.

  3. After is realeased i will give some feedback about touchpad browsing the web interface.
    Farewell my friend!

  4. Hi Volker,
    I hope you are working well for us 🙂
    Do you find some bug in your new storage management for the moment ?

  5. Something new and shining is always fun, but I think al lot of people using linux are using a debian based distro or some sort. This makes it easier to install software on top of OMV or develop plugins for the system.
    Personally I have no experiance using FreeBSD and find using Debian much easier. Also I can install an IRC client on OMV wich I wouldn’t/Couldn’t do on FreeNas. Sure FreeNAS does it’s the Job perfectly but you have to have some knowledge of FreeBSD to expand it yourself. OMV will make this a lot easier I hope.

  6. Looks very nice. I’m hoping on that the OMV is ready for it’s début soon.
    I’m sick of freenas and want to migrate to a debian bases system.

    Thanks for all your efforts!

    • I agree with Martijn. I am also getting tired of FreeNAS. Is there a possibility of creating a mailing list or some sort of notification when you have released it?

    • What is it about FreeANS that you are tired of?
      I’ve been using it in multiple places without a problem for years. It does exactly what it says it will do. Actually I enjoy the comfort of knowing its the same as it was yesterday. Why change what works?

      Maybe you just want something new and shinny?

      • No, the whole design was too limited to enhance it. E.g. there was no easy way to integrate a plugin infrastructure. As starting to plan FreeNAS 8 i decided that everything has to be coded from beginning, new concept, new technologies, new design. Another reason was that i do not want to waste my time with packaging, i wanted to use an existing repository like Debian has. OK, FreeBSD has ports, but they are no easy to use out of the box and at the end you have to build your ports yourself. Also there is no tool available like live-helper/live-build to create installer CD. All such issues are available in the Debian world. Because i work with Debian at work i decided also to switch the OS. The community does not like it -> i was not a big FreeBSD expert -> so OMV was born.

        • Volker, it makes complete sense why you moved away from FreeNAS. From a coding stand-point I see the limitations that FreeBSD has.
          My question was for those users that are “tired” or “sick” of FreeNAS. FreeNAS is a very useful and stable product that should not be looked down upon just because something new is on the horizon.
          FreeNAS is still a very good NAS choice.

  7. Ich muss sagen, meine größten Respekt!!
    Sehr schön und übersichtlich geworden. Findes es schöne als FreeNAS.

    Hoffe das Projekt läuft weiter so, und verläuft nicht irgendwann im Sande, hätte schon schöne Anwendungsgebiete dafür….

  8. Hi volker !
    Keep doing good work 🙂
    I just got a simple question about what you show us in the video, will BTRFS be implemented ? You was talking about some month ago, so I just wanted to know if it will be in the futur release, or been some kind of abandoned (for the moment or totally) ?
    I hope it’s not a question you have already answer.
    Thank you very much anyway, when I heard about your project, I was really, really happy about a nas system on Debian !

  9. Why did you choose the same header logo background as the older versions of FreeNAS? Is this some sort of “FU” to FreeNAS?


  10. Volker, Nice work on the LVM. Looks really simple to use. I hope you release soon so I don’t have to listen to all the h8ers. Getting sick of those fools. Will a 64bit version be coming much after the 32bit????


    • The 64-bit version will be available as soon as possible. I do not expect any problems, but i have to say that i did not build any 64-bit version till now.

  11. It looks pretty good. But I didn’t see anything regarding a ‘4K’ option. Is there any?

    With most (if not all) of the big disks having 4K advanced format but reporting 512 byte per sector, that can lead to performance issue if there is no such option.

    • The partitions are optimal aligned and the block size of the filesystem is set to 4096b (useless in most cases because the manpage tells that 4k is the default).

      E.g. it can be manipulated if necessary via /etc/defaults/openmediavault:

      OMV_INITFS_OPTIONS_EXT3=”-b 4096″
      OMV_INITFS_OPTIONS_EXT4=”-b 4096″
      OMV_INITFS_OPTIONS_XFS=”-b size=4096 -f”

Comments are closed.