POSIX Compliance Testing - Revision history

Docadmin at 21:35, 23 March 2010

2010-03-23T21:35:01Z

Sbarthel at 18:53, 22 February 2010

2010-02-22T18:53:43Z

← Older revision		Revision as of 11:53, 22 February 2010
Line 1:		Line 1:
			<small>''(Updated: Sep 2009)''</small>
	__TOC__		__TOC__
	This page provides instructions for installing and running the POSIX compliance suite of file system tests.		This page provides instructions for installing and running the POSIX compliance suite of file system tests.
Line 197:		Line 198:

	'''''Note:''''' Rebuilding individual POSIX tests is not straightforward due to the reliance on tcc. One option is to substitute edited source files into the source tree while following the manual installation procedure outlined above and let the existing POSIX install scripts do the work. The installation scripts (specifically ''/home/tet/test_sets/run_testsets.sh'') contain relevant commands for building the test suite -- something akin to ''tcc -p -b -s $HOME/scen.bld $*'' -- but these commands may not work outside the scripts. Please let us know if you manage to get better mileage rebuilding these tests.		'''''Note:''''' Rebuilding individual POSIX tests is not straightforward due to the reliance on tcc. One option is to substitute edited source files into the source tree while following the manual installation procedure outlined above and let the existing POSIX install scripts do the work. The installation scripts (specifically ''/home/tet/test_sets/run_testsets.sh'') contain relevant commands for building the test suite -- something akin to ''tcc -p -b -s $HOME/scen.bld $*'' -- but these commands may not work outside the scripts. Please let us know if you manage to get better mileage rebuilding these tests.

	~~''(Updated 09/09)''~~

Docadmin at 21:24, 18 February 2010

2010-02-18T21:24:15Z

← Older revision		Revision as of 14:24, 18 February 2010
Line 197:		Line 197:

	'''''Note:''''' Rebuilding individual POSIX tests is not straightforward due to the reliance on tcc. One option is to substitute edited source files into the source tree while following the manual installation procedure outlined above and let the existing POSIX install scripts do the work. The installation scripts (specifically ''/home/tet/test_sets/run_testsets.sh'') contain relevant commands for building the test suite -- something akin to ''tcc -p -b -s $HOME/scen.bld $*'' -- but these commands may not work outside the scripts. Please let us know if you manage to get better mileage rebuilding these tests.		'''''Note:''''' Rebuilding individual POSIX tests is not straightforward due to the reliance on tcc. One option is to substitute edited source files into the source tree while following the manual installation procedure outlined above and let the existing POSIX install scripts do the work. The installation scripts (specifically ''/home/tet/test_sets/run_testsets.sh'') contain relevant commands for building the test suite -- something akin to ''tcc -p -b -s $HOME/scen.bld $*'' -- but these commands may not work outside the scripts. Please let us know if you manage to get better mileage rebuilding these tests.

			''(Updated 09/09)''

Docadmin at 19:37, 3 February 2010

2010-02-03T19:37:18Z

← Older revision		Revision as of 12:37, 3 February 2010
Line 2:		Line 2:
	This page provides instructions for installing and running the POSIX compliance suite of file system tests.		This page provides instructions for installing and running the POSIX compliance suite of file system tests.

	'''''Note:''''' The Lustre™ code is not completely POSIX compliant, so test results may show some errors. If you have questions about the test results, submit a request for ~~help~~ through [[Reporting Bugs\|Bugzilla]].		'''''Note:''''' The Lustre™ code is not completely POSIX compliant, so test results may show some errors. If you have questions about the test results, submit a request for assistance through [[Reporting Bugs\|Bugzilla]].

	== Quick Start ==		== Quick Start ==

Docadmin at 19:34, 3 February 2010

2010-02-03T19:34:59Z

← Older revision		Revision as of 12:34, 3 February 2010
Line 2:		Line 2:
	This page provides instructions for installing and running the POSIX compliance suite of file system tests.		This page provides instructions for installing and running the POSIX compliance suite of file system tests.

	'''''Note:''''' The Lustre™ code is not completely POSIX compliant, so test results may show some errors. If you have questions about the test results, ~~contact our~~ [~~mailto:lustre-koala-team@sun.com QE and Testing Team~~]]		'''''Note:''''' The Lustre™ code is not completely POSIX compliant, so test results may show some errors. If you have questions about the test results, submit a request for help through [[Reporting Bugs\|Bugzilla]].

	== Quick Start ==		== Quick Start ==

Docadmin: /* Installing Using the Quick Start Script */

2009-12-23T01:07:53Z

Installing Using the Quick Start Script

← Older revision		Revision as of 18:07, 22 December 2009
Line 36:		Line 36:
	</pre>		</pre>

	'''''Note:''''' The quick start procedure only works with the paths ''/home/tet'' and ''/mnt/lustre''. If you want to change the paths, follow the [[#~~Bulding~~ from Scratch\|Building from Scratch]] instructions below and create a new tarball.		'''''Note:''''' The quick start procedure only works with the paths ''/home/tet'' and ''/mnt/lustre''. If you want to change the paths, follow the [[POSIX Compliance Testing#Building from Scratch\|Building from Scratch]] instructions below and create a new tarball.

	=== Running the Test Suite===		=== Running the Test Suite===

Docadmin: /* Quick Start */

2009-12-23T01:05:06Z

Quick Start

← Older revision		Revision as of 18:05, 22 December 2009
Line 8:		Line 8:
	Several versions of the POSIX compliance suite available to [http://downloads.lustre.org/public/tools/benchmarks/posix/ download]. Each version is gcc and architecture specific. You will need to determine which version of gcc you are running locally (''{{{gcc -v}}}'') and then download the appropriate tarball.		Several versions of the POSIX compliance suite available to [http://downloads.lustre.org/public/tools/benchmarks/posix/ download]. Each version is gcc and architecture specific. You will need to determine which version of gcc you are running locally (''{{{gcc -v}}}'') and then download the appropriate tarball.

	If a package isn't available for your particular combination of gcc+architecture, see [[#Building and Running a POSIX Compliance Test Suite on Lustre\|Building and Running a POSIX Compliance Test Suite on Lustre]].		If a package isn't available for your particular combination of gcc+architecture, see [[POSIX Compliance Testing#Building and Running a POSIX Compliance Test Suite on Lustre\|Building and Running a POSIX Compliance Test Suite on Lustre]].

	The following quick start versions are provided:		The following quick start versions are provided:

Docadmin at 20:34, 17 December 2009

2009-12-17T20:34:33Z

← Older revision		Revision as of 13:34, 17 December 2009
Line 1:		Line 1:
			__TOC__
	This page provides instructions for installing and running the POSIX compliance suite of file system tests.		This page provides instructions for installing and running the POSIX compliance suite of file system tests.

Docadmin: Protected "POSIX Compliance Testing" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2009-12-16T19:39:06Z

Protected "POSIX Compliance Testing" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 12:39, 16 December 2009
(No difference)

Docadmin at 19:38, 16 December 2009

2009-12-16T19:38:53Z

← Older revision		Revision as of 12:38, 16 December 2009
Line 1:		Line 1:
	This page provides instructions for installing and running the POSIX compliance suite of file system tests.		This page provides instructions for installing and running the POSIX compliance suite of file system tests.

	'''''Note:''''' The ~~Lustre~~ code is not completely POSIX compliant, so test results may show some errors. If you have questions about the test results, contact our [mailto:lustre-koala-team@sun.com QE and Testing Team]]		'''''Note:''''' The Lustre™ code is not completely POSIX compliant, so test results may show some errors. If you have questions about the test results, contact our [mailto:lustre-koala-team@sun.com QE and Testing Team]]

	== Quick Start ==		== Quick Start ==

← Older revision		Revision as of 14:35, 23 March 2010
Line 92:		Line 92:
	8. Continue with the installation at this point. Answer 'y' to the "Build testsets" question.		8. Continue with the installation at this point. Answer 'y' to the "Build testsets" question.

	The script ~~will proceed~~ to build and install all the file system tests and ~~will~~ then ~~run~~ them all. Even though the script is running them on a local file system, this is a valuable baseline for comparison with the behavior of Lustre.		The script proceeds to build and install all the file system tests and then runs them all. Even though the script is running them on a local file system, this is a valuable baseline for comparison with the behavior of Lustre.

	The results ~~will be~~ put into ''/home/tet/test_sets/results/0002e/journal''. It is suggested that you rename or symlink this directory to ''/home/tet/test_sets/results/ext3/journal'' (or the name of the local file system that the test was run on).		The results are put into ''/home/tet/test_sets/results/0002e/journal''. It is suggested that you rename or symlink this directory to ''/home/tet/test_sets/results/ext3/journal'' (or the name of the local file system that the test was run on).

	Running the full test should only take 5 minutes or so.		Running the full test should only take 5 minutes or so.
Line 100:		Line 100:
	9. Answer 'n' to re-running just the failed tests, and you are done. The results (in a very lengthy table) are in ''/home/tet/test_sets/results/report''.		9. Answer 'n' to re-running just the failed tests, and you are done. The results (in a very lengthy table) are in ''/home/tet/test_sets/results/report''.

	10. At this point ,you need to ''save'' the test suite to use for running further tests on a Lustre file system. Tar up the tests to avoid rebuilding each time by entering:		10. At this point you need to ''save'' the test suite to use for running further tests on a Lustre file system. Tar up the tests to avoid rebuilding each time by entering:
	<pre>		<pre>
	tar cvzf TESTROOT.tgz -C /mnt/lustre TESTROOT		tar cvzf TESTROOT.tgz -C /mnt/lustre TESTROOT
	</pre>		</pre>

	You will ~~probably~~ also want to remove the installed tests ~~at this time,~~ to save ~~a bit~~ space, and more importantly to avoid confusion if you forget to mount your Lustre file system before running the test.		You will may also want to remove the installed tests to save space, and more importantly to avoid confusion if you forget to mount your Lustre file system before running the test.

	=== Running the Suite against Lustre and checking your results ===		=== Running the POSIX Test Suite against Lustre and checking your results ===
	1. As root, set up your Lustre filesystem, mounted on ''/mnt/lustre'' (e.g. ''sh llmount.sh'') and untar the POSIX tests back to their home by entering:		1. As root, set up your Lustre filesystem mounted on ''/mnt/lustre'' (e.g. ''sh llmount.sh'') and untar the POSIX tests back to their home by entering:
	<pre>		<pre>
	tar --same-owner -xzpvf /path/to/tarball/TESTROOT.tgz -C /mnt/lustre		tar --same-owner -xzpvf /path/to/tarball/TESTROOT.tgz -C /mnt/lustre