IBM Spectrum Archive - Revision history

Leo: Added categories and navbox

2021-12-30T01:01:17Z

Added categories and navbox

← Older revision		Revision as of 01:01, 30 December 2021
Line 759:		Line 759:

	*https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General%20Parallel%20File%20System%20(GPFS)/page/Quickly%20determining%20the%20file%20state%20or%20status%20of%20all%20files%20within%20Spectrum%20Archive%20EE		*https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General%20Parallel%20File%20System%20(GPFS)/page/Quickly%20determining%20the%20file%20state%20or%20status%20of%20all%20files%20within%20Spectrum%20Archive%20EE
			{{Navbox Linux}}
			[[Category:Linux]]

Leo: /* File status by tape ID */

2021-04-27T17:03:27Z

File status by tape ID

← Older revision		Revision as of 17:03, 27 April 2021
Line 268:		Line 268:
	There are two ways to get a list of files that are migrated to a particular tape.:		There are two ways to get a list of files that are migrated to a particular tape.:

	#Use the <code>list_by_tape.policy</code> policy file. This requires a full filesystem scan using the policy which may take a long time. The file can be obtained from IBM and the usage is documented in the header of the policy file.		#Use the <code>list_by_tape.policy</code> policy file. This requires a full filesystem scan using the policy which may take a long time. The file can be obtained from IBM and the usage is documented in the header of the policy file. {{Highlight
	{{Highlight
	\| code = # mmapplypolicy /dev/gpfs1 -P list_by_tape.policy -I defer -f /tmp/output_t00100l8 -M tape=T00100L8		\| code = # mmapplypolicy /dev/gpfs1 -P list_by_tape.policy -I defer -f /tmp/output_t00100l8 -M tape=T00100L8
	## Generates /tmp/output_t00100l8.list.mig and /tmp/output_t00100l8.list.premig		## Generates /tmp/output_t00100l8.list.mig and /tmp/output_t00100l8.list.premig
Line 275:		Line 274:
	\| lang = terminal		\| lang = terminal
	}}		}}

	#Read the tape's metadata from the <code>volume_cache</code> directory. The <code>.schema</code> file contains a list of all migrated and premigrated files for a particular tape.{{highlight\|lang=terminal\|code=		#Read the tape's metadata from the <code>volume_cache</code> directory. The <code>.schema</code> file contains a list of all migrated and premigrated files for a particular tape.{{highlight\|lang=terminal\|code=
	# cat /tiered/.ltfsee/meta/library-id/volume_cache/T00100schema{{!}}grep gpfs -A 1 {{!}} grep tiered {{!}} sed "s/<\/value>//g" {{!}} while read i ; do ltfsee info files -f "$i" ; done		# cat /tiered/.ltfsee/meta/library-id/volume_cache/T00100schema{{!}}grep gpfs -A 1 {{!}} grep tiered {{!}} sed "s/<\/value>//g" {{!}} while read i ; do ltfsee info files -f "$i" ; done

Leo: code template to code tag

2020-09-09T17:03:41Z

code template to code tag

← Older revision		Revision as of 17:03, 9 September 2020
Line 2:		Line 2:

	==Usage==		==Usage==
	Use the {{code\|ltfsee}} command to interact with Spectrum Archive. Other binaries related to LTFS can be found at {{code\|/opt/ibm/ltfsee/bin/}}.		Use the <code>ltfsee</code> command to interact with Spectrum Archive. Other binaries related to LTFS can be found at <code>/opt/ibm/ltfsee/bin/</code>.

	Here is a quick cheat sheet of common commands:		Here is a quick cheat sheet of common commands:
Line 74:		Line 74:

	===Spectrum Archive Status===		===Spectrum Archive Status===
	{{code\|ltfsee info libraries}} shows all libraries.		<code>ltfsee info libraries</code> shows all libraries.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# ltfsee info libraries		# ltfsee info libraries
Line 88:		Line 88:
	}}		}}

	{{code\|ltfsee info pools}} shows all pools.		<code>ltfsee info pools</code> shows all pools.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# ltfsee info pools		# ltfsee info pools
Line 116:		Line 116:
	}}		}}

	When performing maintenance on a drive, you should first remove it from Spectrum Archive so that it won't be used by any jobs. Remove a drive with <code>ltfsee drive remove driveid</code>. Drives can be added with the {{code\|ltfsee drive add}} command. A drive can have 3 roles assigned in any combination as flags: Migration (4), Recall (2), or Generic (1). Assign the roles by setting the appropriate value. The default is to allow all roles (7).{{highlight\|lang=terminal\|code=		When performing maintenance on a drive, you should first remove it from Spectrum Archive so that it won't be used by any jobs. Remove a drive with <code>ltfsee drive remove driveid</code>. Drives can be added with the <code>ltfsee drive add</code> command. A drive can have 3 roles assigned in any combination as flags: Migration (4), Recall (2), or Generic (1). Assign the roles by setting the appropriate value. The default is to allow all roles (7).{{highlight\|lang=terminal\|code=
	## To add a drive to node 4 for recall jobs only:		## To add a drive to node 4 for recall jobs only:
	# ltfsee drive add 0007807A0B:2 4		# ltfsee drive add 0007807A0B:2 4
Line 170:		Line 170:

	====Adding Tapes to a Pool====		====Adding Tapes to a Pool====
	To add tapes to a particular pool, use {{code\|ltfsee pool add -p pool -t tape ...}}:		To add tapes to a particular pool, use <code>ltfsee pool add -p pool -t tape ...</code>:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# ltfsee pool add -p TIERED2 -t T00099L8		# ltfsee pool add -p TIERED2 -t T00099L8
Line 190:		Line 190:
	}}		}}

	When dealing with tapes that are in an <code>Error</code> state, you must first remove the tape from the storage pool using {{code\|ltfsee pool remove -p ... -t ... -r}}, unassign it from the logical library in the tape library GUI, run <code>ltfsee retrieve</code> to remove the tape entirely from LTFS, then re-add the tape back to the logical library and re-run <code>ltfsee retrieve</code>. These steps will make the tape in an <code>Unavailable</code> state and only then can the cartridge be added back to a storage pool via re-formatting or checking.		When dealing with tapes that are in an <code>Error</code> state, you must first remove the tape from the storage pool using <code>ltfsee pool remove -p ... -t ... -r</code>, unassign it from the logical library in the tape library GUI, run <code>ltfsee retrieve</code> to remove the tape entirely from LTFS, then re-add the tape back to the logical library and re-run <code>ltfsee retrieve</code>. These steps will make the tape in an <code>Unavailable</code> state and only then can the cartridge be added back to a storage pool via re-formatting or checking.

	====Removing Tape from a pool====		====Removing Tape from a pool====
Line 204:		Line 204:
	\| lang = terminal		\| lang = terminal
	}}		}}
	Tapes containing no migrated data can also be removed from a pool with {{code\|ltfsee pool remove -p pool -t tape ...}}.		Tapes containing no migrated data can also be removed from a pool with <code>ltfsee pool remove -p pool -t tape ...</code>.
	{{Highlight		{{Highlight
	\| code = # ltfsee pool remove -p TIERED1 -t T00030L8		\| code = # ltfsee pool remove -p TIERED1 -t T00030L8
Line 226:		Line 226:

	====Moving a tape cartridge====		====Moving a tape cartridge====
	If a tape is in a drive, you can move it back to its homeslot using {{code\|ltfsee tape move homeslot -t tape -p pool}}. Alternatively, use {{code\|ieslot}} to move it to the IO slot of the tape library for extraction.		If a tape is in a drive, you can move it back to its homeslot using <code>ltfsee tape move homeslot -t tape -p pool</code>. Alternatively, use <code>ieslot</code> to move it to the IO slot of the tape library for extraction.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# ltfsee tape move homeslot -t T00037L8 -p TIERED1		# ltfsee tape move homeslot -t T00037L8 -p TIERED1
Line 238:		Line 238:
	\|1=Side Notes on Migrated Files		\|1=Side Notes on Migrated Files
	\|2=		\|2=
	Migrated files will have a stub file with zero size. To count sizes with {{code\|du}}, you need to use {{code\|--apparent-size}} Eg.		Migrated files will have a stub file with zero size. To count sizes with <code>du</code>, you need to use <code>--apparent-size</code> Eg.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	[root@node001 xuexu]# du -sh dbgap_UK_OTTO		[root@node001 xuexu]# du -sh dbgap_UK_OTTO
Line 255:		Line 255:

	====See file status by path====		====See file status by path====
	File statuses can be viewed with {{code\|ltfsee info files -f filepath}}. The location (or locations if multiple copies were made) is given as the tape ID and library name under each file entry.{{highlight\|lang=terminal\|code=		File statuses can be viewed with <code>ltfsee info files -f filepath</code>. The location (or locations if multiple copies were made) is given as the tape ID and library name under each file entry.{{highlight\|lang=terminal\|code=
	# ltfsee info files -f /tiered/ewang_scratch/xuexu/dbgap_UK_OTTO/SRR302*		# ltfsee info files -f /tiered/ewang_scratch/xuexu/dbgap_UK_OTTO/SRR302*
	Name: /tiered/ewang_scratch/xuexu/dbgap_UK_OTTO/SRR3021220_2.fastq		Name: /tiered/ewang_scratch/xuexu/dbgap_UK_OTTO/SRR3021220_2.fastq
Line 284:		Line 284:

	===Movement Policies===		===Movement Policies===
	File movements are defined and applied by {{code\|mmapplypolicy}}. A scheduled job invoking {{code\|mmapplypolicy}} daily can be used to tier files on a regular basis.		File movements are defined and applied by <code>mmapplypolicy</code>. A scheduled job invoking <code>mmapplypolicy</code> daily can be used to tier files on a regular basis.

	The primary policy is on the LTFS server located at {{code\|/mmpolicies/mmpolicyLATEST.txt}} and are applied with a daily cronjob that invokes:		The primary policy is on the LTFS server located at {{code\|/mmpolicies/mmpolicyLATEST.txt}} and are applied with a daily cronjob that invokes:

Leo: /* List Tape Cartridges */

2020-09-09T17:01:51Z

List Tape Cartridges

← Older revision		Revision as of 17:01, 9 September 2020
Line 126:		Line 126:
	===Tape Cartridge Management===		===Tape Cartridge Management===
	====List Tape Cartridges====		====List Tape Cartridges====
	To show all tapes in the library, run {{code\|ltfsee info tapes}}. Common tape status codes are:		To show all tapes in the library, run <code>ltfsee info tapes</code>. Common tape status codes are:
	{\| class="wikitable"		{\| class="wikitable"
	\|+Consult the documentation for more status codes at https://www.ibm.com/support/knowledgecenter/ST9MBR_1.2.6/ltfs_ee_ltfsee_info_tapes.html		\|+Consult the documentation for more status codes at https://www.ibm.com/support/knowledgecenter/ST9MBR_1.2.6/ltfs_ee_ltfsee_info_tapes.html
Line 134:		Line 134:
	\|Critical		\|Critical
	\|The Critical status indicates that an attempt to write to this cartridge failed.		\|The Critical status indicates that an attempt to write to this cartridge failed.
	To avoid data loss, recover the data on this cartridge by using the ltfsee recover command, then discard this cartridge.		To avoid data loss, recover the data on this cartridge by using the <code>ltfsee recover</code> command, then discard this cartridge.
	\|-		\|-
	\|Error		\|Error
Line 142:		Line 142:
	\|Invalid		\|Invalid
	\|The Invalid status indicates that the cartridge is inconsistent with the LTFS format.		\|The Invalid status indicates that the cartridge is inconsistent with the LTFS format.
	To check and repair this tape before you add it to a tape storage pool, use the ltfsee pool add command with the check option.		To check and repair this tape before you add it to a tape storage pool, use the <code>ltfsee pool add</code> command with the check option.
	\|-		\|-
	\|Unavailable		\|Unavailable
	\|The Unavailable status indicates that the cartridge is not available in the IBM Spectrum Archive Enterprise Edition system.		\|The Unavailable status indicates that the cartridge is not available in the IBM Spectrum Archive Enterprise Edition system.
	Tapes that are newly inserted into the tape library have an Unavailable status. To recall files from a tape with this status, first import the tape by using the ltfsee import command. To add a tape with this status to the IBM Spectrum Archive Enterprise Edition system:		Tapes that are newly inserted into the tape library have an Unavailable status. To recall files from a tape with this status, first import the tape by using the ltfsee import command. To add a tape with this status to the IBM Spectrum Archive Enterprise Edition system:
	First, move the tape to a home slot by using the ltfsee tape move command.		First, move the tape to a home slot by using the <code>ltfsee tape move</code> command.
	Then, add the tape to a tape storage pool by using the ltfsee pool command.		Then, add the tape to a tape storage pool by using the <code>ltfsee pool</code> command.
			\|-
			\| Unknown
			\| A tape has an Unknown status if it was removed and then re-added to Spectrum Archive. Tapes in this state can be made valid again by validating the tape using <code>ltfsee tape validate -p POOL -t TAPEID</code>.
	\|-		\|-
	\|Valid		\|Valid

Leo: /* Logging */

2020-07-02T18:17:07Z

Logging

← Older revision		Revision as of 18:17, 2 July 2020
Line 479:		Line 479:
	\|Run: <code>/opt/ibm/ltfsee/bin/ltfsee_log_collection</code>		\|Run: <code>/opt/ibm/ltfsee/bin/ltfsee_log_collection</code>
	\|}		\|}

			See Also: https://www.ibm.com/support/knowledgecenter/en/ST9MBR_1.3.0/ltfs_ee_logging_facilities_config.html

	===<code>The reclamation process failed</code>===		===<code>The reclamation process failed</code>===

Leo: /* Logging */

2020-07-02T18:15:45Z

Logging

← Older revision		Revision as of 18:15, 2 July 2020
Line 463:		Line 463:
	\|Spectrum Archive Logs		\|Spectrum Archive Logs
	\|/var/log/ltfsee.log		\|/var/log/ltfsee.log
			\|-
			\| Spectrum Archive Debug Logs
			\| tail -f /var/log/ltfsee_trc.log \| ltfsee_catcsvlog
	\|-		\|-
	\|HSM Logs		\|HSM Logs

Leo: /* Removing Tape from a pool */

2020-06-29T17:10:08Z

Removing Tape from a pool

← Older revision		Revision as of 17:10, 29 June 2020
Line 190:		Line 190:

	====Removing Tape from a pool====		====Removing Tape from a pool====
	To remove a tape containing migrated data from a pool, use <code>ltfsee reclaim</code>. This command will move all migrated data to other tapes in the storage pool and then remove the tape from the storage pool.		To remove a tape containing migrated data from a pool, use <code>ltfsee reclaim</code>. This command will move all migrated data to other tapes in the storage pool and then remove the tape from the storage pool. Reclaiming a damaged tape may take a very long time. You can always interrupt a reclaim process with a SIGINT (ctrl-c) and wait for the process to terminate.
	{{Highlight		{{Highlight
	\| code = # ltfsee reclaim -p TIERED2 -t T00101L8		\| code = # ltfsee reclaim -p TIERED2 -t T00101L8

Leo: formatting tape

2020-06-23T23:04:30Z

formatting tape

← Older revision		Revision as of 23:04, 23 June 2020
Line 174:		Line 174:
	}}		}}

	Tapes can only be added if they contain a valid format. Tapes that require formatting will need the <code>-f</code> option. Tapes that have been used previously ~~but~~ with ~~data manually migrated will need to~~ be formatted ~~with~~ the <code>-e</code> option.		Tapes can only be added if they contain a valid format. Tapes that require formatting will need the <code>-f</code> option. Tapes that have been used previously and has old metadata associated with the cartridge cannot be formatted using this method as a safe guard against unintended data loss. An exception format is required using the <code>-e</code> option to ignore metadata during formatting.

	~~You cannot~~ add tapes in an <code>Error</code> state ~~directly. Instead~~, you must first remove the tape from the storage pool using {{code\|ltfsee pool remove -p ... -t ... -r}}, unassign it from the logical library in the tape library GUI, run <code>ltfsee retrieve</code> to remove the tape entirely from LTFS, then re-add the tape back to the logical library and re-run ltfsee retrieve. ~~The~~ tape in ~~LTFS should now be~~ <code>Unavailable</code> ~~which~~ can be added back to a storage pool via re-formatting or checking.		{{Highlight
			\| code = # ltfsee pool add -p TIERED1 -t T00030L8 -f
			GLESL042I(00894): Adding tape T00030L8 to storage pool TIERED1.
			GLESL091E(00937): This operation is not allowed to this state of tape. Need to check the status of Tape T00030L8 by using the ltfsee info tapes command.
			# ltfsee pool add -p TIERED1 -t T00030L8 -e
			GLESL042I(00894): Adding tape T00030L8 to storage pool TIERED1.
			Tape T00030L8 successfully formatted.
			Added tape T00030L8 to pool TIERED1 successfully.
			\| lang = terminal
			}}

			When dealing with tapes that are in an <code>Error</code> state, you must first remove the tape from the storage pool using {{code\|ltfsee pool remove -p ... -t ... -r}}, unassign it from the logical library in the tape library GUI, run <code>ltfsee retrieve</code> to remove the tape entirely from LTFS, then re-add the tape back to the logical library and re-run <code>ltfsee retrieve</code>. These steps will make the tape in an <code>Unavailable</code> state and only then can the cartridge be added back to a storage pool via re-formatting or checking.

	====Removing Tape from a pool====		====Removing Tape from a pool====
Line 199:		Line 210:
	For tapes that Spectrum Archive believes contains migrated data when in fact it doesn't (verified by checking every file listed in the tape volume_cache or using the list_by_tape.policy), you may force remove a tape using the <code>-r</code> option. If you force remove a tape containing migrated data, you may still be able to recover the data if you do a deep recovery check when adding the tape without reformatting.{{Warning		For tapes that Spectrum Archive believes contains migrated data when in fact it doesn't (verified by checking every file listed in the tape volume_cache or using the list_by_tape.policy), you may force remove a tape using the <code>-r</code> option. If you force remove a tape containing migrated data, you may still be able to recover the data if you do a deep recovery check when adding the tape without reformatting.{{Warning
	\|1=Force removing a mounted cartridge		\|1=Force removing a mounted cartridge
	\|2=If you force remove a tape that's mounted in a drive, the tape will be removed from the pool and unmount. However, Spectrum Archive will not be moved to its homeslot since it is no longer aware of the tape's existence. The tape will sit ejected on the drive and will prevent the tape changer from fulfilling any requests to this tape drive made by Spectrum Archive.		\|2=If you force remove a tape that's mounted in a drive, the tape will be removed from the pool and unmount. However, Spectrum Archive will not be moved to its homeslot since it is no longer aware of the tape's existence. The tape will sit ejected in the drive and will prevent the tape changer from fulfilling any requests to this tape drive made by Spectrum Archive until it is moved manually via the Tape Library interface.

	~~You must~~ manually ~~move it using~~ the Tape Library interface.
	}}		}}

Leo: /* The reclamation process failed */

2020-06-23T21:31:40Z

The reclamation process failed

← Older revision		Revision as of 21:31, 23 June 2020
Line 242:		Line 242:
	}}		}}

	==== See file status by path ====		====See file status by path====
	File statuses can be viewed with {{code\|ltfsee info files -f filepath}}. The location (or locations if multiple copies were made) is given as the tape ID and library name under each file entry.{{highlight\|lang=terminal\|code=		File statuses can be viewed with {{code\|ltfsee info files -f filepath}}. The location (or locations if multiple copies were made) is given as the tape ID and library name under each file entry.{{highlight\|lang=terminal\|code=
	# ltfsee info files -f /tiered/ewang_scratch/xuexu/dbgap_UK_OTTO/SRR302*		# ltfsee info files -f /tiered/ewang_scratch/xuexu/dbgap_UK_OTTO/SRR302*
Line 253:		Line 253:
	}}		}}

	==== File status by tape ID ====		====File status by tape ID====
	There are two ways to get a list of files that are migrated to a particular tape.:		There are two ways to get a list of files that are migrated to a particular tape.:

	# Use the <code>list_by_tape.policy</code> policy file. This requires a full filesystem scan using the policy which may take a long time. The file can be obtained from IBM and the usage is documented in the header of the policy file.		#Use the <code>list_by_tape.policy</code> policy file. This requires a full filesystem scan using the policy which may take a long time. The file can be obtained from IBM and the usage is documented in the header of the policy file.
	{{Highlight		{{Highlight
	\| code = # mmapplypolicy /dev/gpfs1 -P list_by_tape.policy -I defer -f /tmp/output_t00100l8 -M tape=T00100L8		\| code = # mmapplypolicy /dev/gpfs1 -P list_by_tape.policy -I defer -f /tmp/output_t00100l8 -M tape=T00100L8
Line 263:		Line 263:
	\| lang = terminal		\| lang = terminal
	}}		}}
	# Read the tape's metadata from the <code>volume_cache</code> directory. The <code>.schema</code> file contains a list of all migrated and premigrated files for a particular tape.{{highlight\|lang=terminal\|code=
			#Read the tape's metadata from the <code>volume_cache</code> directory. The <code>.schema</code> file contains a list of all migrated and premigrated files for a particular tape.{{highlight\|lang=terminal\|code=
	# cat /tiered/.ltfsee/meta/library-id/volume_cache/T00100schema{{!}}grep gpfs -A 1 {{!}} grep tiered {{!}} sed "s/<\/value>//g" {{!}} while read i ; do ltfsee info files -f "$i" ; done		# cat /tiered/.ltfsee/meta/library-id/volume_cache/T00100schema{{!}}grep gpfs -A 1 {{!}} grep tiered {{!}} sed "s/<\/value>//g" {{!}} while read i ; do ltfsee info files -f "$i" ; done
	Name: /tiered/file/path.txt		Name: /tiered/file/path.txt
Line 443:		Line 444:


	== Troubleshooting ==		==Troubleshooting==

	===Logging===		===Logging===
Line 462:		Line 463:
	\|lin_tape driver		\|lin_tape driver
	\|/var/log/lin_tape.*		\|/var/log/lin_tape.*
			\|-
			\|LTFSEE Log Collection
			\|Run: <code>/opt/ibm/ltfsee/bin/ltfsee_log_collection</code>
	\|}		\|}

Line 738:		Line 742:

	==See Also==		==See Also==

	*https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General%20Parallel%20File%20System%20(GPFS)/page/Quickly%20determining%20the%20file%20state%20or%20status%20of%20all%20files%20within%20Spectrum%20Archive%20EE		*https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General%20Parallel%20File%20System%20(GPFS)/page/Quickly%20determining%20the%20file%20state%20or%20status%20of%20all%20files%20within%20Spectrum%20Archive%20EE

Leo at 21:25, 23 June 2020

2020-06-23T21:25:41Z

Show changes