Known issues/en: Difference between revisions
Jump to navigation
Jump to search
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 14: | Line 14: | ||
=== Nearline === | === Nearline === | ||
* Nearline capabilities are not yet available; see https://docs.computecanada.ca/wiki/National_Data_Cyberinfrastructure for a brief description of the intended functionality. | * Nearline capabilities are not yet fully available; see https://docs.computecanada.ca/wiki/National_Data_Cyberinfrastructure for a brief description of the intended functionality. | ||
** | ** January 2019: on Graham, /nearline has been in near-production use since late last year; Cedar is adding some storage hardware to enable /nearline, as well - not clear whether it'll be available for RAC2019. Contact [[Technical Support|technical support]] if you would like more information. | ||
=== Missing project folder === | === Missing project folder === | ||
Revision as of 21:01, 15 January 2019
Report an issue
- Please report issues to the technical support team.
- The status page at http://status.computecanada.ca/ is not updated automatically yet, so may lag in showing current status.
- CC Clusters are vulnerable to the recent Meltdown/Spectre vulnerabilities, and will be updated, which involves updating the OS and CPU microcode. Read more at Meltdown and Spectre bugs.
Scheduler issues
No known issues at this time.
Quota and filesystem problems
Nearline
- Nearline capabilities are not yet fully available; see https://docs.computecanada.ca/wiki/National_Data_Cyberinfrastructure for a brief description of the intended functionality.
- January 2019: on Graham, /nearline has been in near-production use since late last year; Cedar is adding some storage hardware to enable /nearline, as well - not clear whether it'll be available for RAC2019. Contact technical support if you would like more information.
Missing project folder
- Upon creation of a new account for a Principal Investigator, the PROJECT storage space might not be allocated until the next business day.
Cedar only
Nothing to report at this time.
Graham only
- A component of the /project filesystem malfunctioned while returning to service as described here. Some details of the restoration process:
- A list of affected files (.files_being_restored) is in the base directory of each project. For privacy reasons, this list is only readable by the project owner (sponsor or PI).
- Affected files behave oddly: they cannot be removed (because they make reference to an offline storage component, so a failure is returned when trying to deallocate). They can be moved, though (the "mv" command doesn't work though.) Affected files will show up in directory listings with "?" in some fields.
- We are restoring files to a separate location, then moving the broken file elsewhere, and moving the restored file into place. This is happening incrementally, and every restored file is noted in another per-project list (.files_restored).
- Based on the overall number of files affected, we expect the entire process to take 8-10 days. The particular order of files restored depends on tape scheduling, so is difficult to predict.