Error Remounting Filesystem Read-only
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you detected aborted journal remounting filesystem read only might have Meta Discuss the workings and policies of this site linux remount filesystem read only About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting remount filesystem read write ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users remount read only file system of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top read only root filesystem up vote 11 down vote favorite 4 Somehow my Debian went to
Linux Read Only File System Fix
read only in root file system. I have no idea how this could have happened. For example when I am in /root folder and type command nano and after that press Tab to list possible file in that folder I get the message: root@debian:~# nano -bash: cannot create temp file for here-document: Read-only file system The same for the cd command when I type cd /home and press Tab to list paths I have this: root@debian:~# cd /home -bash: cannot create temp file for here-document: Read-only file system I also have problems with software like apt and others. Can't even apt-get update. I have a lot of errors like this: Err http ://ftp.de.debian.org wheezy-updates/main Sources 406 Not Acceptable W: Not using locking for read only lock file /var/lib/apt/lists/lock W: Failed to fetch http ://ftp.de.debian.org/debian/dists/wheezy/Release rename failed, Read-only file system (/var/lib/apt/lists/ftp.de.debian.org_debian_dists_wheezy_Release -> /var/lib/apt/lists/ftp.de.debian.org_debian_dists_wheezy_Release). W: Failed to fetch http ://security.debian.org/dists/wheezy/updates/main/source/Sources 404 Not Found W: Failed to fetch http ://security.debian.org/dists/wheezy/updates/main/binary-amd64/Packages 404 Not Found W: Failed to fetch http ://ftp.de.debian.org/debian/dists/wheezy
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back
Linux Going In Read Only
Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red cannot remount block device /dev/sda1 read-write, is write-protected Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back read-only file system centos Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red http://unix.stackexchange.com/questions/145882/read-only-root-filesystem/145919 Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux https://access.redhat.com/solutions/26049 Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English español Deutsch italiano í•œêµì–´ français æ—
Bug #1445195: [Hyper-V] Kernel patches for storvsc. Edit Remove 28 This bug affects 6 people Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit https://bugs.launchpad.net/bugs/1456985 Fix Committed Undecided Unassigned Edit Also affects project (?) Also affects distribution/package Nominate for series Bug Description Because "ubuntu-bug linux" not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). read only Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read-only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS only file system machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en-us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal