this post was submitted on 27 Aug 2024
22 points (92.3% liked)

Selfhosted

60253 readers
613 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
22
Best Guest VM Filesystem for NTFS Host (infosec.pub)
submitted 2 years ago by anon2963@infosec.pub to c/selfhosted@lemmy.world
14 comments fedilink hide all child comments
 

I am setting up a Linux server (probably will be NixOS) where my VM disk files will be stored on top of an NTFS partition. (Yes I know NTFS sucks but it has to be this way.)

I am asking which guest filesystem will have the best performance for a very mixed workload. If I had access to the extra features of BTRFS or ZFS I would use them but I have no idea how CoW interacts with NTFS; that is why I am asking here.

Also I would like some NTFS performance tuning pointers.

you are viewing a single comment's thread
view the rest of the comments
[–] one_knight_scripting@lemmy.world 3 points 2 years ago

Yeah, I'd just like to ask why it has to be NTFS as well. I want to help you to the best of my ability.

Now in terms of what you are trying to accomplish, it would sincerely help to know what kind of server you are trying to create and what you want it to accomplish so I can help you with the design. It would also help to know what hypervisor you are using to read those VM disks. Now, for the sake of the rest of this post, I'm going to assume that you are simply creating a Linux server meant to share those disks with a hyper-v hypervisor (to ensure we discuss the worst case... Lol... but also because I think the only reason you need NTFS is to support a Windows hypervisor).

Now if that assumption is correct, I would still ask why the filesystem must be NTFS. If all you need is a share for the files then why does the filesystem even matter? In my opinion, the worst case scenario that you have is a samba share which shares these files over as a Windows share. Now Windows is capable of better sharing utilizing either iscsi or NFS. None of these three sharing solutions (samba, iscsi, NFS) require an NTFS filesystem. Though I will admit that there may be some other thing that causes an issue with the potential of these solutions.

Anyways, not to pry, I want to help you though but a little more detail would significantly help with helping you find a solution.