van Sleeuwen, Berry wrote: > Hello list, > > For various tests we have created a group of new SLES10 guests. They all are > just one 3390-3 volume so they can be cloned vary fast.
If you use FLASHCOPY its fast regardless of DASD size. > But for some reason these machines sometimes switch the rootdisk, and > therefore the entire filesystem, to readonly. I have tried a remount but that > didn't work so only a reboot will get the / back in write mode. The reboot > itself run without errors. But even that sometimes doesn't solve the error > and we have to clone the guest again. We also have a different SLES10 > installation and there we don't see any errors there but then we aren't > running any load there. > > I can't find any reason for this, other than what I can find in de guest > console log. Any ideas? What can be the cause of this and how can it be fixed? You have a problem in with you root filesystem, so it switches to R/O to give you a chance to fix it, e.g. with fsck. > > The guest is a SLES10 SP2. I have many SP2 systems, all with ext3 - never any problems at all. > > [EMAIL PROTECTED]:~> uname -a > Linux nlzlx921 2.6.16.60-0.21-default #1 SMP Tue May 6 12:41:02 UTC 2008 > s390x s390x s390x GNU/Linux > > > [EMAIL PROTECTED]:~> df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/dasda1 2365444 1682640 562644 75% / > udev 145620 64 145556 1% /dev > > > The message from the console: > 08/08/19 12:23:31 NLZLX921 VMLXES21: EXT3-fs error (device dasda1): > ext3_readdir: bad entry in directory #270514: rec_len is > 08/08/19 12:23:31 NLZLX921 VMLXES21 smaller than minimal - offset=0, > inode=0, rec_len=0, name_len=0ŸAborting journal on device > 08/08/19 12:23:31 NLZLX921 VMLXES21 dasda1.Ÿext3_abort called.ŸEXT3-fs > error (d > 08/08/19 12:23:31 NLZLX921 VMLXES21: Aug 19 12:23:31 nlzlx921 > syslog-ngÃ1092¨: io.c: do_write: write() failed (errno 30), Read-only > 08/08/19 12:23:31 NLZLX921 VMLXES21 file system > > > When I asked one of our linux specialists he did mention there were a few > bugs relating ext3 that have been fixed in RHEL 5.1. Now I have noticed that > RHEL 5.1 is on a newer kernel level than the SLES 10 SP2. Could a bug in ext3 > by any chance be the problem here? > The bug is most likely in your cloning process, perhaps the DASD extents copied and/or used are different. This will only show up when data is used within the bad extent range. mark ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
