From 3bb64fe675877c6c357e80b99670555a39fbdd24 Mon Sep 17 00:00:00 2001 From: Stephen Soltesz Date: Thu, 26 Feb 2009 16:05:04 +0000 Subject: [PATCH] address a continuing issue on production machines where a node will fsck, mount during BM, but after kexec, the fs will be corrupted again and hang. changing these values will ensure that the production system runs fsck again. not at all sure where the source of the problem is coming from. --- source/steps/InstallWriteConfig.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/steps/InstallWriteConfig.py b/source/steps/InstallWriteConfig.py index f7afb52..dedde10 100644 --- a/source/steps/InstallWriteConfig.py +++ b/source/steps/InstallWriteConfig.py @@ -90,9 +90,9 @@ def Run( vars, log ): fstab= file( "%s/etc/fstab" % SYSIMG_PATH, "w" ) fstab.write( "%s none swap sw 0 0\n" % \ PARTITIONS["mapper-swap"] ) - fstab.write( "%s / ext3 defaults 0 0\n" % \ + fstab.write( "%s / ext3 defaults 1 1\n" % \ PARTITIONS["mapper-root"] ) - fstab.write( "%s /vservers ext3 tagxid,defaults 0 0\n" % \ + fstab.write( "%s /vservers ext3 tagxid,defaults 1 2\n" % \ PARTITIONS["mapper-vservers"] ) fstab.write( "none /proc proc defaults 0 0\n" ) fstab.write( "none /dev/shm tmpfs defaults 0 0\n" ) -- 2.47.0