<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 08:16:37 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[BDS-17043] Behaviour/Resource Packs &#8212; File System Issue</title>
                <link>https://bugs.mojang.com/browse/BDS-17043</link>
                <project id="11700" key="BDS">Bedrock Dedicated Server</project>
                    <description>&lt;h1&gt;&lt;a name=&quot;Issue&quot;&gt;&lt;/a&gt;Issue&lt;/h1&gt;

&lt;p&gt;Behaviour/resource packs are not loaded when run on a Linux machine with `XFS` as the filesystem and the `ftype` flag set to `0`.&lt;/p&gt;

&lt;p&gt;We discovered an issue recently where a number of our Linux machines had Bedrock Dedicated Servers which would not load behaviour/resource packs. After some investigation we found the only real difference between machines that did work and machines that didn&apos;t were the file system:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;CentOS 7 `ext4`: works&lt;/li&gt;
	&lt;li&gt;CentOS 7 `XFS`: works&lt;/li&gt;
	&lt;li&gt;Almalinux 8 `ext4`: works&lt;/li&gt;
	&lt;li&gt;Almalinux 8 `XFS` with `ftype=1`: works&lt;/li&gt;
	&lt;li&gt;Almalinux 8 `XFS` with `ftype=0`: does not work&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The flag seems to be purely a metadata structure thing so we are unsure why this would cause an issue.&lt;/p&gt;

&lt;p&gt;Unfortunately, changing the flag requires rebuilding the entire filesystem (aka, reinstalling the OS). &#8212; This isn&apos;t feasible for us so we hope there&apos;s a way this can be resolved upstream.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;hr /&gt;
&lt;h1&gt;&lt;a name=&quot;ReplicationProcess&quot;&gt;&lt;/a&gt;Replication Process&lt;/h1&gt;

&lt;p&gt;1. For demonstration purposes, let&apos;s use a known working one from a public library: &lt;a href=&quot;https://mcpedl.com/extended-amethyst-add-on/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mcpedl.com/extended-amethyst-add-on/&lt;/a&gt; (though any would work as far as we can tell)&lt;/p&gt;

&lt;p&gt;2. Once the files are downloaded, one will be a behaviour pack, and the other will be a resource pack. Let&apos;s import both to the client by simply double-clicking them.&lt;/p&gt;

&lt;p&gt;3. After that, let&apos;s create a new single-player world and under &apos;Add-Ons&apos;, select both.&lt;/p&gt;

&lt;p&gt;4. Once created, we can verify in creative that it does work in single-player by simply searching for an amethyst ring: &lt;a href=&quot;https://i.geri.dev/sQIRTPXwBGj5.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/sQIRTPXwBGj5.png&lt;/a&gt;&lt;br/&gt;
Now, let&apos;s exit out of this world and copy the files into a server.&lt;/p&gt;

&lt;p&gt;5. Download the dedicated server files from &lt;a href=&quot;https://www.minecraft.net/en-us/download/server/bedrock&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.minecraft.net/en-us/download/server/bedrock&lt;/a&gt; (Apparently only the Beta one is available there currently so we&apos;ll use the latest stable instead, `v1.18.31`)&lt;/p&gt;

&lt;p&gt;6. Upload the freshly created world folder from `%LocalAppData%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds` to `./worlds/` on the server and rename it to `Bedrock level`.&lt;/p&gt;

&lt;p&gt;7. Start the server directly and attempt to connect.&lt;/p&gt;
&lt;h3&gt;&lt;a name=&quot;Onaworkingmachine%2Chereiswhatwe%27llsee%3A&quot;&gt;&lt;/a&gt;On a working machine, here is what we&apos;ll see:&lt;/h3&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Login screen: Shows that we would have to download 0.04 MB to apply the resource pack (see below about the cache) &#8212; &lt;a href=&quot;https://i.geri.dev/vI1nYpMRyzHk.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/vI1nYpMRyzHk.png&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Once logged in, we can search for the amethyst ring without any issues: &lt;a href=&quot;https://i.geri.dev/2YpxTzICd7fP.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/2YpxTzICd7fP.png&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;h3&gt;&lt;a name=&quot;Onamachinethathas%60XFS%60with%60ftype%3D0%60%2Chereiswhatwesee%3A&quot;&gt;&lt;/a&gt;On a machine that has `XFS` with `ftype=0`, here is what we see:&lt;/h3&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Login screen: Shows that we&apos;d only need to download 0.02 MB (see about cache below) &#8212; &lt;a href=&quot;https://i.geri.dev/maxb4yn9SdoA.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/maxb4yn9SdoA.png&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;In-game, we cannot view any new items such as the amethyst ring &#8212; &lt;a href=&quot;https://i.geri.dev/pPaLxrJnyHCi.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/pPaLxrJnyHCi.png&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;hr /&gt;
&lt;h1&gt;&lt;a name=&quot;MoreInformation&quot;&gt;&lt;/a&gt;More Information&lt;/h1&gt;

&lt;p&gt;Additionally, this happens to all players on different devices from further testing.&lt;/p&gt;

&lt;p&gt;As for the cache, it looks like if you already connected previously to a world with the exact resource/behaviour packs, it will store it locally so the download screen may not match correctly. As such, we made sure to clear the game&apos;s cache through Main Menu &#10140; &apos;Settings&apos; &#10140; &apos;Storage&apos; when possible just so that is not the problem.&lt;/p&gt;

&lt;p&gt;We have also tried numerous times to manually install these behaviour packs just in case single player did it incorrectly &#8212; though it seems to be doing it perfectly as the `world_resource_packs.json` and `world_behavior_packs.json` seems to always match the data in the packs&apos; `manifest.json` information.&lt;/p&gt;

&lt;p&gt;For convenience, we have compiled a ZIP archive of an entire server that has issues when running on a machine with the conditions mentioned above: &lt;a href=&quot;https://archive.geri.dev/bedrock_test.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://archive.geri.dev/bedrock_test.zip&lt;/a&gt; (~73 MB total)&lt;/p&gt;</description>
                <environment></environment>
        <key id="504627">BDS-17043</key>
            <summary>Behaviour/Resource Packs &#8212; File System Issue</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="4" iconUrl="https://bugs.mojang.com/images/icons/statuses/reopened.png" description="This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.">Reopened</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="Geeeri">Geri K</reporter>
                        <labels>
                    </labels>
                <created>Wed, 1 Jun 2022 08:50:04 +0200</created>
                <updated>Tue, 11 Jun 2024 21:10:37 +0200</updated>
                                            <version>1.18.31</version>
                    <version>1.19.0</version>
                    <version>1.19.2 Hotfix</version>
                                                            <votes>3</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="1280229" author="cory" created="Mon, 18 Sep 2023 23:33:55 +0200"  >&lt;p&gt;Unable to run scripts under an `xfs` filesystem if the `ftype` is set to 0. This issue continues to be a problem and identical to the issue we were having a year ago.&lt;/p&gt;

&lt;p&gt;I&#8217;ve entirely isolated this issue to a VPS using the service called `Vulr` and replicated the problem by doing the following. This is worth noting as when installing `AlmaLinux` as the (&#8220;Host Machine&#8221;) with an xfs filesystem it was `ext4` in this environment.&lt;/p&gt;

&lt;p&gt;Additional things to note. We do know this isn&#8217;t meant to be run on AlmaLinux, and we run our bedrock servers in docker running Ubuntu. However, since the (&#8220;Host Machine&#8221;) is an xfs filesystem with ftype=0. This will cause (&#8220;scripts&#8221;) to fail. We isolated it to make sure it wasn&#8217;t a docker-related issue, and it&#8217;s not.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
yum -y install zip unzip parted screen
echo -e &lt;span class=&quot;code-quote&quot;&gt;&quot;yes\nyes&quot;&lt;/span&gt; | parted /dev/vda ---pretend-input-tty resizepart 2 15GB
echo -e &lt;span class=&quot;code-quote&quot;&gt;&quot;n\np\n1\n\n\n+5G\nw&quot;&lt;/span&gt; | fdisk /dev/vda
echo -e &lt;span class=&quot;code-quote&quot;&gt;&quot;n\np\n1\n\n\n+5G\nw&quot;&lt;/span&gt; | fdisk /dev/vda
mkfs.xfs -f -n ftype=1 /dev/vda3
mkfs.xfs -f -m crc=0 -n ftype=0 /dev/vda4
mkdir -p /ftype1
mkdir -p /ftype0
systemctl daemon-reload
mount /dev/vda3 /ftype1
mount /dev/vda4 /ftype0 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;If you use `Vultr` they do have a scripts area where you can easily copy/paste to build this server from scratch and don&#8217;t have to manually do it. The main command is creating partitions with the `mkfs.xfs` parameters.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Once the server has booted or completed the tasks.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
#check meta data
xfs_info /ftype1 | grep &lt;span class=&quot;code-quote&quot;&gt;&quot;ftype&quot;&lt;/span&gt;
xfs_info /ftype0 | grep &lt;span class=&quot;code-quote&quot;&gt;&quot;ftype&quot;&lt;/span&gt;
xfs_info /ftype1 | grep &lt;span class=&quot;code-quote&quot;&gt;&quot;crc&quot;&lt;/span&gt;
xfs_info /ftype0 | grep &lt;span class=&quot;code-quote&quot;&gt;&quot;crc&quot;&lt;/span&gt; &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;If everything looks set up properly. We&#8217;re going to build a server mostly from scratch. This will create the essential files/worlds required.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
mkdir -p /home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/
cd /home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/
wget https:&lt;span class=&quot;code-comment&quot;&gt;//minecraft.azureedge.net/bin-linux/bedrock-server-1.20.15.01.zip -O bedrock-server.zip
&lt;/span&gt;unzip -o bedrock-server.zip
cp -rf &lt;span class=&quot;code-quote&quot;&gt;&quot;config/&lt;span class=&quot;code-keyword&quot;&gt;default&lt;/span&gt;&quot;&lt;/span&gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;config/Bedrock level&quot;&lt;/span&gt;
screen -dmS bedrock ./bedrock_server
screen -S bedrock -p 0 -X stuff &lt;span class=&quot;code-quote&quot;&gt;&apos;stop^M&apos;&lt;/span&gt; &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;The next step is the scripts. You can find your own scripts or use the one provided. This includes behavior and resource packs and a modified `level.dat` to enable experimental builds. Might want to do this manually to ensure the files get extracted properly.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
cd &lt;span class=&quot;code-quote&quot;&gt;&quot;/home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/worlds/Bedrock level/&quot;&lt;/span&gt;
wget https:&lt;span class=&quot;code-comment&quot;&gt;//cory.pro/Origins.zip -O Origins.zip
&lt;/span&gt;unzip -o Origins.zip &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Next, we will proceed by copying these same files into the new directories/partitions we created earlier.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
cd /home/
cp -rf &lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; /ftype0/
cp -rf &lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; /ftype1/ &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Modify the ports to avoid conflicts or just run one at a time.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
sed -i &lt;span class=&quot;code-quote&quot;&gt;&apos;s/server-port=[0-9]*/server-port=19142&apos;&lt;/span&gt;/g /ftype0/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/server.properties
sed -i &lt;span class=&quot;code-quote&quot;&gt;&apos;s/server-port=[0-9]*/server-port=19152&apos;&lt;/span&gt;/g /ftype1/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/server.properties
sed -i &lt;span class=&quot;code-quote&quot;&gt;&apos;s/server-portv6=[0-9]*/server-portv6=19143&apos;&lt;/span&gt;/g /ftype0/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/server.properties
sed -i &lt;span class=&quot;code-quote&quot;&gt;&apos;s/server-portv6=[0-9]*/server-portv6=19153&apos;&lt;/span&gt;/g /ftype1/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/server.properties &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Let us confirm the issue. Go into each directory and start the server respectively.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
cd /home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/; screen -dmS bedrock_ext4 ./bedrock_server
cd /ftype0/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/; screen -dmS bedrock_ftype0 ./bedrock_server
cd /ftype1/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/; screen -dmS bedrock_ftype1 ./bedrock_server &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;You will see that `ext4` and `ftype1` works perfectly fine, and for `ftype0` the scripts don&#8217;t load at all. Keep in mind these are identical servers we just copied and the 2 main differences are the filesystem and server port.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;This is where it becomes interesting&#8230;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
cd /home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/
screen -dmS bedrock_ext4 /home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/bedrock_server; screen -x bedrock_ext4 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;This will load the scripts fine. However, if we switch to:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
cd /ftype0/
screen -dmS bedrock_ext4 /home/&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;/bedrock_server; screen -x bedrock_ext4 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Do you notice we&#8217;re using the same `screen` command as above? The difference in this case, we ran the command from `/ftype0` and the result is that it failed. However, we run it from `cd /home/new/` directly. It doesn&#8217;t fail. Not likely a path issue per Se. This is still a `ftype=0` issue and needs to be resolved.&lt;/p&gt;</comment>
                            <comment id="1198800" author="geeeri" created="Thu, 8 Sep 2022 16:30:03 +0200"  >&lt;p&gt;This is still indeed an issue, though it seems like I was able to discover some more information.&lt;/p&gt;

&lt;p&gt;On systems using XFS with the `ftype` flag set to `0` servers with these resource packs were no longer able to launch.&#160;&lt;/p&gt;

&lt;p&gt;Here is a download link to the testing files: &lt;a href=&quot;https://archive.geri.dev/bedrock_test_v3.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://archive.geri.dev/bedrock_test_v3.zip&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For reference, here is what happens on all of our other nodes that are working, where we use different file system types or `ftype` `1`:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Server logs: &lt;a href=&quot;https://p.geri.dev/raw/zipifidoninihisemide&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://p.geri.dev/raw/zipifidoninihisemide&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Login screen: &lt;a href=&quot;https://i.geri.dev/YWeRFLSgMhjX.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/YWeRFLSgMhjX.png&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Inventory: &lt;a href=&quot;https://i.geri.dev/XvsD2VxfAjIh.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/XvsD2VxfAjIh.png&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&amp;#8212;&lt;/p&gt;

&lt;p&gt;On a node with XFS and `ftype` 0, here is the startup crash: &lt;a href=&quot;https://p.geri.dev/raw/lewipejokeficagoqifo&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://p.geri.dev/raw/lewipejokeficagoqifo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Out of curiosity, I tried disabling the resource/behaviour pack to see if that&apos;s the issue and it still crashed with the same log.&lt;/p&gt;

&lt;p&gt;After poking around I found that simply removing the `level.dat` file allows the server to launch even when the resource/behaviour packs are enabled.&#160;&lt;/p&gt;

&lt;p&gt;I do not know much about the format of this file but from reading the wiki, it seems like experiments are stored here: &lt;a href=&quot;https://minecraft.fandom.com/wiki/Bedrock_Edition_level_format#level.dat&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://minecraft.fandom.com/wiki/Bedrock_Edition_level_format#level.dat&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After a closer look and a DIFF check, it does seem like the freshly generated `level.dat` file has none of the experiments: &lt;a href=&quot;https://i.geri.dev/iuKaQpolLV7j.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/iuKaQpolLV7j.png&lt;/a&gt; (aside from some of the other, seemingly irrelevant differences)&lt;/p&gt;

&lt;p&gt;Just to confirm, I checked in-game and indeed the resource/behaviour packs are not working without these experiments: &lt;a href=&quot;https://i.geri.dev/9dGTxw3Dy0Om.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://i.geri.dev/9dGTxw3Dy0Om.png&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I went back to check if these specific experiments were enabled for the packs that we reported before and that indeed appears to have been the case.&#160;&lt;/p&gt;

&lt;p&gt;Using a combination of hex editors and other 3rd party tools, I was able to modify the original level.dat to discover that in this case, the `gametest` experiment when it&apos;s set to `1` was causing this crash&lt;/p&gt;

&lt;p&gt;Modifying the `level.dat` file to set this to `0` allowed the server to boot without crashes and the resource/behaviour packs worked without any issues as well.&lt;/p&gt;

&lt;p&gt;For reference, here are all the files at the end of this test: &lt;a href=&quot;https://archive.geri.dev/bedrock_test_v4.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://archive.geri.dev/bedrock_test_v4.zip&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&amp;#8212;&lt;/p&gt;

&lt;p&gt;Lastly, I tested a resource as well as a behaviour pack that did not require any experiments to be enabled and sure enough, that appears to work without any issues as well across all different file system types and file system flags.&#160;&lt;/p&gt;

&lt;p&gt;&amp;#8212;&lt;/p&gt;

&lt;p&gt;To summarize: It seems like the issue is being caused by some of these experiments that are failing to load correctly on systems using the XFS file system type with the `ftype` flag set to `1`.&lt;/p&gt;

&lt;p&gt;While we completely understand that experiments are just that and may cause instability, it&apos;d be great if the team could check why it would not work on such a widely used file system type and configuration.&lt;/p&gt;

&lt;p&gt;Though with the mentioned configuration and full server file downloads, it should be fairly easy to replicate this issue, we would be more than happy to provide a testing server and tools to replicate this issue consistently.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Geri K.&lt;/p&gt;</comment>
                            <comment id="1198728" author="JIRAUSER648376" created="Thu, 8 Sep 2022 11:45:46 +0200"  >&lt;p&gt;Hi&lt;/p&gt;

&lt;p&gt;Does this issue still occur after updating to 1.19.22?&lt;/p&gt;

&lt;p&gt;This ticket will automatically reopen when you reply. &lt;/p&gt;</comment>
                            <comment id="1182749" author="lordsherman" created="Fri, 15 Jul 2022 14:13:57 +0200"  >&lt;p&gt;I can confirm the issue presents itself on Ubuntu 22.04&lt;/p&gt;

&lt;p&gt;Also had a hunch that it could have been due to the filesystems CRC setting but this does not seem to be the case. It seems to only fail if ftype=0 is specified when generating the XFS filesystem.&lt;/p&gt;</comment>
                            <comment id="1181959" author="JIRAUSER648376" created="Wed, 13 Jul 2022 13:57:40 +0200"  >&lt;p&gt;&lt;b&gt;Thank you for your report!&lt;/b&gt;&lt;br/&gt;
However, this issue is &lt;font color=&quot;#ff5722&quot;&gt;&lt;b&gt;Invalid&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;

&lt;p&gt;Only Ubuntu 18 and later versions are supported.&#160;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Quick Links&lt;/b&gt;:&lt;br/&gt;
&#128211; &lt;a href=&quot;https://aka.ms/MCBugTrackerHelp&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Bug Tracker Guidelines&lt;/a&gt;&#160;&#8211; &#128231; &lt;a href=&quot;https://help.minecraft.net/hc/en-us/requests/new&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Mojang Support&lt;/a&gt;&lt;br/&gt;
&#128211; &lt;a href=&quot;https://bugs.mojang.com/projects/BDS/summary&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;Project Summary&lt;/a&gt; &#8211; &#9997;&#65039; &lt;a href=&quot;https://feedback.minecraft.net/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Feedback and Suggestions&lt;/a&gt; &#8211; &#128214; &lt;a href=&quot;https://minecraft.fandom.com/wiki/Bedrock_Dedicated_Server&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;BDS Wiki&lt;/a&gt; &#8211; &#128214; &lt;a href=&quot;https://help.minecraft.net/hc/en-us/articles/360035131651-Dedicated-Servers-for-Minecraft-on-Bedrock-&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;FAQs&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1180207" author="JIRAUSER656552" created="Wed, 6 Jul 2022 15:24:09 +0200"  >&lt;p&gt;I don&apos;t think mojang accept issues for linux distros other then ubuntu and I think another distro&lt;/p&gt;</comment>
                            <comment id="1179744" author="geeeri" created="Tue, 5 Jul 2022 10:09:56 +0200"  >&lt;p&gt;This still appears to be an issue in the latest BDS version (v1.19.2.xx) downloaded from &lt;a href=&quot;https://minecraft.azureedge.net/bin-linux/bedrock-server-1.19.2.02.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://minecraft.azureedge.net/bin-linux/bedrock-server-1.19.2.02.zip&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1173015" author="geeeri" created="Tue, 14 Jun 2022 06:35:22 +0200"  >&lt;p&gt;The issue appears to be present on the latest release of The Wild Update. The client says it&apos;s using v1.19.0 while BDS itself is using v1.19.1.01 if I understand correctly.&lt;/p&gt;

&lt;p&gt;Using the same setup, it works perfectly unless it is on AlmaLinux with XFS using ftype=0.&lt;/p&gt;

&lt;p&gt;The 1.19 files can be downloaded from here: &lt;a href=&quot;https://archive.geri.dev/bedrock_test_v2.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://archive.geri.dev/bedrock_test_v2.zip&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1168380" author="geeeri" created="Wed, 1 Jun 2022 09:14:10 +0200"  >&lt;p&gt;Shortly after posting it, I realized there was a dedicated section for BDS. &#8212; I&apos;m unsure whether moving it to that section would be more appropriate but apologies for the headache.&lt;/p&gt;</comment>
                            <comment id="1168379" author="arisabot" created="Wed, 1 Jun 2022 08:50:15 +0200"  >&lt;div class=&quot;panel&quot; style=&quot;border-color: orange;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelContent&quot;&gt;
&lt;p&gt;&lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/warning.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Please do not mark &lt;em&gt;Unreleased Versions&lt;/em&gt; as affected. You don&apos;t have access to them yet.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&lt;sub&gt;&lt;font color=&quot;#888&quot;&gt;&amp;#8211; I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on &lt;a href=&quot;https://discordapp.com/invite/rpCyfKV&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Discord&lt;/a&gt; or &lt;a href=&quot;https://www.reddit.com/r/Mojira/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Reddit&lt;/a&gt;&lt;/font&gt;&lt;/sub&gt;&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>891850</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10302"><![CDATA[Community Consensus]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_12700" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Description</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>[Briefly describe the bug here]&lt;br/&gt;
&lt;br/&gt;
*Steps to Reproduce:*&lt;br/&gt;
# [Step 1]&lt;br/&gt;
# [Step 2]&lt;br/&gt;
# [Step 3]&lt;br/&gt;
&lt;br/&gt;
*Observed Results:*&lt;br/&gt;
[Describe what happens]&lt;br/&gt;
&lt;br/&gt;
*Expected Results:*&lt;br/&gt;
[Describe what should happen]&lt;br/&gt;
&lt;br/&gt;
*Screenshots/Videos attached:* [please attach an image or short video]&lt;br/&gt;
&lt;br/&gt;
*Notes:*</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Multiple, see below</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i28ign:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>