Known issues/fr: Difference between revisions
Jump to navigation
Jump to search
(Updating to match new version of source page) |
No edit summary |
||
| Line 24: | Line 24: | ||
Aucun problème rapporté. | Aucun problème rapporté. | ||
= Problèmes rapportés pour Graham = | = Problèmes rapportés pour Graham = | ||
* | * A component of the /project filesystem malfunctioned while returning to service as described [http://status.computecanada.ca/incident/104 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. | |||
Revision as of 20:07, 15 January 2019
Rapporter un problème
Pour rapporter un problème, contactez le soutien technique.
Problèmes généraux
- L'état courant des systèmes est rapporté sur cette page web; comme la mise à jour des renseignements n'est pas encore automatisée, un certain délai est à prévoir.
- Les grappes de Calcul Canada sont sensibles aux récentes vulnérabilités Meltdown et Spectre; le système d'exploitation sera mis à jour (voir Bogues Meltdown et Spectre).
Ordonnanceur
Aucun problème rapporté.
Quotas et systèmes de fichiers
Nearline
- Les fonctionnalités nearline ne sont pas encore disponibles; pour la date planifiée, voyez Cyberinfrastructure nationale de données.
- Mise à jour en date du 17 juillet : pas encore disponibles. Pour obtenir votre quota alloué pour 2017, contactez le soutien technique.
Répertoire /PROJECT non disponible
L'espace de stockage /PROJECT est généralement alloué le prochain jour ouvrable suivant la création d'un compte par un chercheur principal.
Problèmes rapportés pour Cedar
Aucun problème rapporté.
Problèmes rapportés pour Graham
- 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.