5

RHEL and Centos VMs with IO failure on root

view full story
linux-howto

http://www.unix.com – Hello, I am running into this issues, few VMWare VM's that are running with RHEL 5.6 and Centos 5.7, are having read write errors on the root file system. This is noticed on all vm's. After looking to log files this what I noticed. #touch test.txt touch: cannot touch `test.txt': Read-only file system. # after this we have reboot the server, during booting up, fsck is fixing the issue, in one case we had to rebuild whole VM as did keep on panic, it did'nt as prompt for fsck. some of the log message error that I noticed. Jan 18 13:25:01 Hostname1 kernel: EXT3-fs warning (device (HowTos)

robot1's picture
Submitted by robot1 on 01/19/2012 – Made popular on 01/19/2012

Stories similar to RHEL and Centos VMs with IO failure on root

Please have a look on the attached. What could be done to solve it?

[root@LAB-oam-blade-3 tomcat]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) [...] /dev/mapper/TOMCATp1 on /opt/nls/float/tomcat type ext3 (**rw**) [root@LAB-oam-blade-3 tomcat]# pwd /opt/nls/float/tomcat [root@LAB-oam-blade-3 tomcat]# touch test.test touch: cannot touch `test.test': Read-only file system

Hello, everyone. First of all, I'm quite a noob, so ANY help will be.. helpful :)

Yesterday I've updated my openSUSE 11.1 to 11.2 using installation DVD. After that, as system boots, I started to get lines like:

Code: FATAL: Module jbd not found FATAL: Module mbcache not found FATAL: Module ext3 not found and so on with different modules..

Has anyone noticed anything weird with their phone's touch screen? I never really noticed this, or had an issue until I played GTA on my phone. The multi-touch doesn't recognize two point near the bottom (where the buttons are) of the screen or near the top (near the logo). It chooses to recognize one and ignores the other. (can't drive and steer at the same time.

I am stuck in a problem. i am not able to start my system. it has centos 5 installed on it and gives the following error on reboot:

fsck.ext3: Attempt to read blocks from filesystem resulted in short read while trying to open /dev/VolGroup01/bkup

could this be a zero length partition?

anyone for help

Running CentOS 5.6 with mdadm RAID1, 2TB, 3 partitions (boot, swap and root). I had a kernel panic in the server, and after rebooting, the system stays up for about 5-10 minutes, the it starts printing out fsck errors to the console and the root file system is put into readonly mode.

I understand this first example:

> mkdir foo > chmod u-w foo > touch foo/test touch: cannot touch `foo/test': Permission denied > echo "BAD" >> foo/test bash: foo/test: Permission denied

This makes sense: I don't have write permission on the directory so I shouldn't be able to write any changes. I can not touch nor create a file that can be appended to.

I tried "chattr +i DIRNAME", it's great, but I cannot create files in the DIR after chattr.

I use BTRFS on my root system with Fedora 18 (fully updated as of now). I noticed extreme data/file loss when an unclean shutdown happens (e.g. power loss, hardware reset etc.).

I tested this doing the following test:

~ # touch test.txt ~ # echo 'hello' > test.txt ~ # cat test.txt hello

So the file is there and it should be written on disk correctly.

I am trying to debug a kernel panic. Panic message says unable to handle kernel paging request for address 40025694.

At the time of panic it was executing ldreq r10, [lr, #-4] @ get SWI instruction. According to my understanding link register value is not a valid address. It is a very strange behavior. At the time of panic running process on cpu 1 was uEventObserver.