Architecture - User Level OSS - Revision history

Docadmin at 21:25, 22 January 2010

2010-01-22T21:25:15Z

← Older revision		Revision as of 14:25, 22 January 2010
Line 1:		Line 1:
	'''''Note:''''' The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.		'''''Note:''''' ''The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.''

	== Summary Requirements ==		== Summary Requirements ==

Docadmin: Protected "Architecture - User Level OSS" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2010-01-22T19:29:55Z

Protected "Architecture - User Level OSS" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 12:29, 22 January 2010
(No difference)

Docadmin at 00:22, 19 January 2010

2010-01-19T00:22:07Z

← Older revision		Revision as of 17:22, 18 January 2010
Line 1:		Line 1:
			'''''Note:''''' The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.

	== Summary Requirements ==		== Summary Requirements ==

Docadmin: /* References */

2010-01-18T23:47:40Z

References

← Older revision		Revision as of 16:47, 18 January 2010
Line 17:		Line 17:
	\| Ideally with LAID llogging, a more complex method can be introduced that can undo the damage in the double failure case		\| Ideally with LAID llogging, a more complex method can be introduced that can undo the damage in the double failure case
	\|}		\|}



	~~== References ==~~

Docadmin: /* References */

2010-01-18T23:47:33Z

References

← Older revision		Revision as of 16:47, 18 January 2010
Line 21:		Line 21:

	== References ==		== References ==



	~~[[Category:QAS\|User Level OSS]]~~

Docadmin: moved QAS User Level OSS to Architecture - User Level OSS

2010-01-15T18:54:36Z

moved QAS User Level OSS to Architecture - User Level OSS

← Older revision	Revision as of 11:54, 15 January 2010
(No difference)

Docadmin: 1 revision

2010-01-15T18:51:39Z

1 revision

← Older revision	Revision as of 11:51, 15 January 2010
(No difference)

Docadmin at 23:11, 20 January 2007

2007-01-20T23:11:17Z

New page

== Summary Requirements ==

{| width="80%" border=1
| io_cli_fail
| if a Lustre client fails, and the OSS has partially executed an IO operation, it leaves the server file system in a reasonable state.
|-
| io_oss_fail
| if an OSS fails, a client will retry to complete partial IO operations and they will complete as if the OSS had not failed
|-
| io_no_copy
| for large IO transfers there will be no copy of data pages as is common in read/write system call implementation.
|-
| io_double_failure
| If the OSS and the client fail, allowing 0's in the file due to truncation is certainly permitted, even the possibility of bad data like in ext3 write back mode is probably acceptable.
|-
|io_llog_refinement
| Ideally with LAID llogging, a more complex method can be introduced that can undo the damage in the double failure case
|}

== References ==

[[Category:QAS|User Level OSS]]