one_knight_scripting

@one_knight_scripting@lemmy.world

• ⁨Comment⁩ on ⁨Half-Life 2 peaks at 52,000 concurrent players, 20 years after its release⁩ ⁨⁨4⁩ ⁨days⁩ ago⁩:

  You just changed my life.

• ⁨Comment⁩ on ⁨If you already know Docker CLI, is there a reason to use Portainer?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Wow. What an awesome wife. I think I just discovered a new relationship goal.

• ⁨Comment⁩ on ⁨Microsoft Edge gets "unfair advantage", browser makers claim⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Take your upvote and gtfo. Lol

• ⁨Comment⁩ on ⁨Best Guest VM Filesystem for NTFS Host⁩ ⁨⁨2⁩ ⁨months⁩ 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.