Read Only File System Error Xen
Contents |
there, i've xen running and the domU which runs apache and the other stuff worked fine for 3 weeks now, but yesterday i got those "warning file system is read only" linux read only file system fix message again, and yeah.. the filesystem turns read-only and i'm getting errors. my partition touch: cannot touch : read-only file system table on the domU looks like that: Code: /dev/sda1 / ext3 errors=remount-ro,usrquota,grpquota 0 1 proc /proc proc rw,nodev,nosuid,noexec 0 0 /dev/sda2 virtualbox read only file system error none swap sw 0 0 errors=remount-ro - that tells me it remounts the partition in read-only mode, but WHY does he remount the partiton? which errors could have forced that, and is it advised to mount: cannot remount block device read-write, is write-protected change that errors=remount-ro to remount-rw or could that f**** up my whole filesystem and everything goes BOOM? weezul, Sep 10, 2008 #1 falko Super Moderator ISPConfig Developer Can you restart the VM and then immediately go to its console ( Code: xm console
Linux Going In Read Only
falko, Sep 11, 2008 #2 weezul New Member hello, i'm getting this after rebooting the domU: Code: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 processor: Unknown symbol pm_idle WARNING: Error inserting processor (/lib/modules/2.6.18-6-xen-amd64/kernel/drive rs/acpi/processor.ko): Unknown symbol in module, or unknown parameter (see dmesg ) FATAL: Error inserting thermal (/lib/modules/2.6.18-6-xen-amd64/kernel/drivers/a cpi/thermal.ko): Unknown symbol in module, or unknown parameter (see dmesg) Done. Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Begin: Loading MD modules ... Success: loaded module raid1. Done. Begin: Assembling all MD arrays ... md: md0 stopped. mdadm: no devices found for /dev/md0 md: md1 stopped. mdadm: no devices found for /dev/md1 md: md2 stopped. mdadm: no devices found for /dev/md2 md: md3 stopped. mdadm: no devices found for /dev/md3 Failure: failed to assemble all arrays. Done. and my dmesg output on the domU: Bootdata ok (command line is root=/dev/sda1 ro) Memory: 492800k/532480k available (1949k kernel code, 30764k reserved, 878k data, 148k init) md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 processor: Unknown symbol pm_idle powernow_k8: Unknown symbol acpi_processor_notify_smm powernow_k8: Unknown symbol acpi_processor_unregist
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly
Redhat Read Only File System Error
Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and ext4-fs remounting filesystem read-only Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenServer linux read only file system remount XenServer Product Family Administrator Console Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Read-only file system Started https://www.howtoforge.com/community/threads/problem-with-xen-partition-gets-read-only.26725/ by Tonny Andersson , 11 July 2012 - 12:06 PM Login to Reply 3 replies to this topic Tonny Andersson Members #1 Tonny Andersson 539 posts Posted 11 July 2012 - 12:06 PM One of my XenServers suddelny went unavailable via XenCenter.Logged on with SSH and tried xe-restart-toolstackGot errormessages that says "Read-only file system"I cannot create files or http://discussions.citrix.com/topic/310031-read-only-file-system/ folders anywhere on the filesystem. It just says "Read-only file system"...The VM's are still running on this host but I cannot migrate them via XenCenter or commandline.Suggestions please? 1333-310031-1657519 Back to top Tonny Andersson Members #2 Tonny Andersson 539 posts Posted 12 July 2012 - 09:30 AM When rebooting the server I was prompted for fixing errors on the filesystem. Selected Yes and after scanning through the disk and "fixing errors" the server came up normal after next reboot.No clue whatever the rootcause of this problem was.... 1333-310031-1657818 Back to top Chuck Homic Members #3 Chuck Homic 1 posts Posted 29 May 2013 - 05:14 PM I had this happen twice on one server, then once on another. They are Dell R410's, and I ran Dell's diagnostics continually for about a month looking for a hardware problem, but found none. We also tried memtest86. So far we've found no hardware-related cause for this error. Now that it has happened on two servers, I'm more suspicious that it is a software error. 1333-31003
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://serverfault.com/questions/30657/xen-domu-root-filesystems-becoming-read-only-on-iscsi-virtual-ip-failover of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask read only a question Anybody can answer The best answers are voted up and rise to the top Xen DomU root filesystems becoming read-only on iSCSI virtual IP failover up vote 8 down vote favorite 8 My Xen servers are openSUSE 11.1 with open-iscsi to our iSCSI SAN cluster. The SAN modules are in an IP failover group behind a virtual IP that the initiators only file system connect to. In the event that the primary SAN server goes down, the secondary picks up the role of serving as the target. This is all handled by the LeftHand SAN/iQ software and works well in most situations. The problem I have is that occasionally some of my Xen DomUs will have their root filesystem go read-only after an IP failover. It's not consistent, and happens to a different subset each time a failover occurs. They're all running the same openSUSE 11.1 software image. The root filesystems for each DomU are mounted by open-iscsi in the Dom0 and then Xen uses the standard block device driver to expose it to the DomU. The exact symptom is that as a root as running touch /test returns the error "read-only filesystem". However, the output of mount shows it as being mounted read-write. Of course, all other I/O on the domU is also failing at this time so the machine comes down hard. Simply restarting it with xm from the Dom0 without even reconnecting the iSCSI session makes everything work again. On the Dom0 side the syslog messages dur