With the ORPC BlockDevice module that is merged in #126, enabling the ExFat file system in the FS init causes the booting process to hang.
This code block starts an exfat block device and mounts it. However, after updating to the BlockDevice module on ORPC servers, the system will hang at boot with this code block enabled. That means the new ORPC design for BlockDevice has some conflict with the ExFat.
The problem persists in the yingqi/raid1_orpc branch, and the code block is temporarily commented out for integrating the RAID1 module.
The latest working version of ExFat is in the commit c9bdfe6. First broken commit is 859a01a, and the commits in between are just not compilable. All these commits are on yingqi/raid1_orpc.
In the first broken commit, the Ext2 is successfully initialized and mounted, but ExFat is hanging at the line ExfatFS::open() in kernel/source/fs/mod.rs, which tries to open it.
With the ORPC BlockDevice module that is merged in #126, enabling the ExFat file system in the FS init causes the booting process to hang.
This code block starts an exfat block device and mounts it. However, after updating to the
BlockDevicemodule on ORPC servers, the system will hang at boot with this code block enabled. That means the new ORPC design forBlockDevicehas some conflict with the ExFat.The problem persists in the
yingqi/raid1_orpcbranch, and the code block is temporarily commented out for integrating the RAID1 module.The latest working version of ExFat is in the commit c9bdfe6. First broken commit is 859a01a, and the commits in between are just not compilable. All these commits are on
yingqi/raid1_orpc.In the first broken commit, the Ext2 is successfully initialized and mounted, but ExFat is hanging at the line
ExfatFS::open()inkernel/source/fs/mod.rs, which tries to open it.