commit b0e80858aa6cd445ee194efcfd8906e2311fc39a
author Tom Wai-Hong Tam <waihong@chromium.org> Wed Dec 07 16:15:06 2011 +0800
committer Gerrit <chrome-bot@google.com> Wed Dec 07 23:34:18 2011 -0800
tree fd724dc8f9c75e081a00d5dae7efcd70c806e93b
parent 02c087998f92ae779f96b9054cc31bfda0fab61a

Mount the USB disk as EXT2 explicitly.

We found when we run FAFT many time, the data of USB disk is changed and
causes our test failed. It may be caused by the USB mount command. Adding
the explicit EXT2 type is safer.

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
        servo_vid=0x18d1 servo_pid=0x5001" UserRequestRecovery/control.normal

Change-Id: I77c4c53d118de7321f835664168dadb6137891d5
Reviewed-on: https://gerrit.chromium.org/gerrit/12533
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>

server/cros/faftsequence.py

diff --git a/server/cros/faftsequence.py b/server/cros/faftsequence.py
index 99b4078..9cc0a8f 100644
--- a/server/cros/faftsequence.py
+++ b/server/cros/faftsequence.py
@@ -112,7 +112,7 @@
                     'An USB disk should be plugged in the servo board.')
 
         tmp_dir = tempfile.mkdtemp()
-        utils.system('sudo mount -r %s3 %s' % (usb_dev, tmp_dir))
+        utils.system('sudo mount -r -t ext2 %s3 %s' % (usb_dev, tmp_dir))
         code = utils.system(
                'grep -qE "(Test Build|testimage-channel)" %s/etc/lsb-release' %
                tmp_dir, ignore_status=True)