CVS log for xfs-cmds/xfstests/115

Up to [Development] / xfs-cmds / xfstests

Request diff between arbitrary revisions

Default branch: MAIN

Revision 1.5 / (download) - annotate - [select for diffs], Tue Aug 12 04:14:21 2008 UTC (9 years, 2 months ago) by brads.longdrop.melbourne.sgi.com
Branch: MAIN
CVS Tags: HEAD
Changes since 1.4: +1 -1 lines
Diff to previous 1.4 (unified)

Various tests were incorrectly identifying themselves in header comments
Merge of master-melb:xfs-cmds:31874a by kenmcd.

  Change header comment to correctly identify test name

Revision 1.4 / (download) - annotate - [select for diffs], Thu May 17 15:58:12 2007 UTC (10 years, 4 months ago) by ddiss.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.3: +1 -2 lines
Diff to previous 1.3 (unified)

Currently there are a few ways mkfs options are specified in XFSQA:
1) suite wide MKFS_OPTIONS are specified before tests are run
	e.g.
	vimes:/home/fsgqa/kali/xfsqa/xfstests # export MKFS_OPTIONS="-l size=100m"

2) test wide MKFS_OPTIONS are specified during a particular test
	e.g. 119
	export MKFS_OPTIONS="-l version=2,size=1200b,su=64k"

3) mkfs options are appended by a test at mkfs time
	e.g.  083
	_scratch_mkfs_xfs -dsize=$fsz,agcount=$ags  >>$seq.full

(4) Another form of appending is just appending to MKFS_OPTIONS directly
	e.g. 	114:export MKFS_OPTIONS="$MKFS_OPTIONS -i parent=1"
		115:export MKFS_OPTIONS="$MKFS_OPTIONS -i paths=1"

Conflicts between mkfs options specified with method 1 & 3 are common.
960377 	XFSQA 041, 042 - mkfs fails with large log size MKFS_OPTIONS.

This change means if a mkfs fails where mkfs options have been appended by a test (method 3),
The mkfs is retried using only those options defined by the test.

occurances of method 4 (in test 114 & 115) are also changed to use method 3.

$seq.full logs the fact that a mkfs options conflict has occured.
Merge of master-melb:xfs-cmds:28601a by kenmcd.

  append -i paths mkfs option using _scratch_mkfs_xfs -i paths...
  rather than export MKFS_OPTIONS="$MKFS_OPTIONS -i paths=1.
  this avoids mkfs option conflicts

Revision 1.3 / (download) - annotate - [select for diffs], Wed Nov 9 02:49:08 2005 UTC (11 years, 11 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.2: +0 -28 lines
Diff to previous 1.2 (unified)

Update copyright annotations and license boilerplates to correspond with SGI Legals preferences.
Merge of master-melb:xfs-cmds:24327a by kenmcd.

Revision 1.2 / (download) - annotate - [select for diffs], Thu Sep 15 15:05:47 2005 UTC (12 years ago) by tes.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.1: +3 -1 lines
Diff to previous 1.1 (unified)

paranoid testing that mkfs of scratch works without ipaths option
Merge of master-melb:xfs-cmds:23822a by kenmcd.

  paranoid testing that mkfs of scratch works without ipaths option

Revision 1.1 / (download) - annotate - [select for diffs], Tue May 24 04:00:32 2005 UTC (12 years, 4 months ago) by tes.longdrop.melbourne.sgi.com
Branch: MAIN

qa tests for parentptr stuff
on irix
Merge of master-melb:xfs-cmds:22663a by kenmcd.

  tests whether xfs_check_ipaths and xfs_repair_ipaths are working.
  It also uses attr to do bad things to EAs and see if xfs_repair_ipaths
  can fix them up.

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.