OpenMediaVault FAQ #12

    • OpenMediaVault FAQ #12

      In this forum I read in the OpenMediaVault FAQ article by WastlJ:

      <<<
      12. What filesystem should I use on my data drive(s)?

      PLEASE format your data drives with EXT3/EXT4. With other filesystems
      like NTFS you´ll run into problems as soon as you create your first
      folder because of the privileges!
      >>>

      Can anybody please elaborate, how and under which circumstances the privelege problems occure?

      To try out, I attached some external NTFS formatted USB drives (most contents were already there) to my HP microserver with OVM 2.2.25. I accessed the drives, created directories, copied files inside, edited the files and deleted them. No problem so far. Not many tests either.

      For all internal drives, I am using ext4, but for the external drive, NTFS is convenient at the moment because of hopefully easy usage together with Windows type OS. I just like to understand the concrete nature of the problems, to be able to better plan, how to set things up.

      [BTW., using ext4 was not without problems. Using a disk formated to ext4 by gparted-live-cd yields in confusing error messages ("special file missing" or similar). In dmesg, I then found the real reason was, that gparted obviously used some newer ext4 features (#400), which are not supported on OMV 2.2.25 an which will make mounting the disk fail. Formatting the disk with OMV allowed mounting again. Seems to show, that ext4 is not that universally usable as i.e. ext3.]
      OMV 4.1.13-1 (typically everything up to date), only plugin: flash memory; HP Microserver, 4 internal ext4 HDDs, SSD for OS, SD-Card for booting (can't boot on SSD with 4 HDD used …), external USB3 HDDs (ext4 + NTFS)
    • ntfs and other non-native filesystems do not support all Linux filesystem features. The biggest one is ACLs which is what wastlj was referring to.

      gparted live uses a much newer version of ext4 utilities. This may be an issue with OMV 2.x due to the fact that it uses Debian Wheezy which is old. I doubt this is an issue with OMV 3.x. Not sure why you would format with gparted though.

      I also don't understand the desire to use ntfs. OMV is a NAS. If you want the files from the drive, transfer them over the network. There is no reason Windows needs to read the drive directly. If the server failed and you want to put the drive in a windows box, you could always use the ext driver or boot a live linux distro.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Ryecoaaron, from your answer, I unfortunately still not understand, under which concrete circumstances the privelege problems occure. You mention ACL. Does it mean, it will fail, when I need ACL from Windows clients? When I need Unix type ACLs? Am I safe, when I have no desire to use ACL or is some implict ACL usage already a problem.

      To your question - desire to use NTFS. I guess, the question and my answer could make a good starting point to some emotional discussion about pros and cons of different scenarios, which I'd rather avoid.
      Actually, I have no intrinsic desire to use NTFS. But still two main reasons: - a couple of TB of data are already there on NTFS, so it would be convenient, to let it there. - Moving data to some other place (which is not controlled by myself, not in "my" network - experience shows, that an external NTFS drive is typically easy to access at many places - not as easy as FAT32, however). BTW - I am only talking about external USB drives. Typically, they were attached to some Windows (or multi OS) computers, but now, I want them to attach to the file server. I am also well aware of many methods to access different Unixish file systems on Windows type OSes.
      OMV 4.1.13-1 (typically everything up to date), only plugin: flash memory; HP Microserver, 4 internal ext4 HDDs, SSD for OS, SD-Card for booting (can't boot on SSD with 4 HDD used …), external USB3 HDDs (ext4 + NTFS)
    • You cannot change basic permissions in ntfs drives, drives are mounted by default as 777 in Omv. A guest login can delete all data if he wants. ACL in Omv (and Linux) are only for Fs that support them, of course ntfs is not included. Quota also is not supported.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • buers wrote:

      Actually, I have no intrinsic desire to use NTFS. But still two main reasons: - a couple of TB of data are already there on NTFS, so it would be convenient, to let it there.
      I´d go with tekkbs suggestion to move the data do an ext4 drive. Or at least save it temporarily on another drive, format this one as an ext4 drive and move it back.

      There are also things like ntfs-3g for debian but those things mostly do not work as expected (still not doing the permissions/acl right)
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive