Hello all,
I am having an issue where my Fedora 27 guest goes into read only file-system mode, usually when under heavy disk I/O.
I am running a Fedora 27 host, and I run the guest to connect to a VPN. I then run the apps (e.g. qbittorrent) that I would like to connect to the net through the VPN in the guest.
Attached is the VBox log split into two parts, along with dmesg from my host from a session that ended up with the guest going into a read only file-system mount.
I have tried remaking the virtual machine, and the issue happens on two separate host machine I own, both with the same setup.
Any help massively appreciated!
Fedora 27 guest frequently goes into read only fs mount
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fedora 27 guest frequently goes into read only fs mount
Can you please substitute your two 1/2 parts of the VBox.log, with one single ZIPPED version of it? It helps save a (virtual) tree or two, and it makes it a lot easier to work with, if it's a single file. Thanks...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Fedora 27 guest frequently goes into read only fs mount
Sure, done.
Last edited by socratis on 15. Jan 2018, 20:07, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Reason: Removed unnecessary verbatim quote of the whole previous message.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fedora 27 guest frequently goes into read only fs mount
I don't know why your setup goes read-only, but my feeling is that there is too much I/O, some operations time out, and the Linux kernel decides to take the filesystem read-only to prevent damage, thinking that the I/O timeout is due to something going wrong with its hard drive.
Let's see if anyone else with better Linux knowledge might come up with something. And I would think that the 'dmesg' output of the guest would be more important compared to that of the host.
Let's see if anyone else with better Linux knowledge might come up with something. And I would think that the 'dmesg' output of the guest would be more important compared to that of the host.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Fedora 27 guest frequently goes into read only fs mount
Just ran dmesg on the guest and it doesn't return any output (this is prior to the read only file-system thing happening). I'll update if i can run it after the error occurs.
Re: Fedora 27 guest frequently goes into read only fs mount
Updated to Vbox 5.2.6 and the issue still occurs. The root filesystem going ro, means I can't dmesg.
Anyone out there who may be able to help?
Anyone out there who may be able to help?
Re: Fedora 27 guest frequently goes into read only fs mount
Added output from cat /dev/kmsg on the guest.
- Attachments
-
- kmsg.txt
- (61.81 KiB) Downloaded 19 times
Re: Fedora 27 guest frequently goes into read only fs mount
Some poeple in #fedora on IRC suggested I might have a faulty disk.
I've ruled that out just in case:
I've ruled that out just in case:
Code: Select all
smartctl -l selftest /dev/sda
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.14.13-300.fc27.x86_64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 9510 -
# 2 Short offline Completed without error 00% 9489 -