I am always told "Read-only file system" error while building large projects

Pioneer
1

Recently, I found that the filesystem of fedora 38 on my milkv pioneer always tell me “Read-only file system” after I build some large projects like LLVM on it. After some searching on web, operating system faults are thought to be the root of the problem. So anyone else have met the same question? And how do you solve this problem?

Below are details about my OS running on my milkv pioneer:
Distribution: Fedora 38
Output of uname -a: Linux fedora-riscv 6.1.31 #1 SMP Thu Jun 15 01:30:00 CST 2023 riscv64 GNU/Linux

1 Like
2

You’re going to have to be much more specific. Can you show the build logs or the error message you are getting?

Typically a “Read-only file system” error is caused by trying to modify a filesystem that is marked read-only.

3

Sorry, I didn’t make the question clear. After I do something rather HEAVY with the milkv pioneer machine, it seems that the system crashes and reports a problem like this, and after that, I can’t use the system for anything. Building large projects is just one example, similar examples are running many programs in parallel and so on. The process of compiling llvm was successful, I guess because compiling llvm writes a lot of data to disk, and the instability of the OS causes this to crash the machine!

1 Like
4

But what do you mean with “I can’t use the system for anything”. What are the exact symptoms of your problem?

5

Thank you for your continued interest in this issue first! I can do nothing while occurring the error. For example, I cannot connect to the machine by ssh or cannot execute any command through early-connected ssh terminal. This file system problem would also occur after I download a huge mount of files to the machine. So I guess the root cause is that the file system is not robose of fedora 38 on milkv pioneer.

6

Yeah, the IO might’ve been the bottleneck. However, nobody can guess it unless you supply the logs of it breaking the filesystem.

Also, it would be rather interesting to observe what’s going on via the debug UART interface, if possible.

7

Thank you for your suggestion; this perspective is great. I will try out this approach.

1 Like