Known issues/en: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(Updating to match new version of source page)
(Updating to match new version of source page)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
<languages />
<languages />
= Report an issue =
* Please report issues to the [[Technical Support|technical support]] team.


= Shared issues =
Problems that affect many users and are being investigated, such as a cluster-wide malfunction or outage, are on [https://status.alliancecan.ca/ the Alliance Status page]. This "Known issues" page describes problems that affect many users but that may take some time to repair, or are not planned for repair at this time. Problems that only affect a specific software package are described on the wiki page for that software package.  
* 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 ==
==Report an issue==
Please report issues to the [[Technical Support|technical support]] team.


No known issues at this time.
==Shared issues==
The [https://status.alliancecan.ca/ status page] is updated manually, so there may be a delay between when a problem begins and when it is posted to the status page.


== Quota and filesystem problems ==
===Scheduler issues===


=== Nearline ===
No known issues.
* 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 ===
===Quota and filesystem issues===
* Upon creation of a new account for a Principal Investigator, the [[Project layout|PROJECT]] storage space might not be allocated until the next business day.


= Cedar only =
====Missing project folder====
Nothing to report at this time.
Upon creation of a new account for a Principal Investigator, the [[Project layout|<code>/project</code>]] storage space might not be allocated until the next business day.


= Graham only =
==Cluster-specific issues==
* 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).
===Béluga===
** 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.
No known issues.
** 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.
===Cedar===
No known issues.
 
===Graham===
Graham's /scratch is often slow; it will be replaced soon.
 
===Narval===
No known issues.

Latest revision as of 22:23, 28 October 2024

Other languages:

Problems that affect many users and are being investigated, such as a cluster-wide malfunction or outage, are on the Alliance Status page. This "Known issues" page describes problems that affect many users but that may take some time to repair, or are not planned for repair at this time. Problems that only affect a specific software package are described on the wiki page for that software package.

Report an issue

Please report issues to the technical support team.

Shared issues

The status page is updated manually, so there may be a delay between when a problem begins and when it is posted to the status page.

Scheduler issues

No known issues.

Quota and filesystem issues

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.

Cluster-specific issues

Béluga

No known issues.

Cedar

No known issues.

Graham

Graham's /scratch is often slow; it will be replaced soon.

Narval

No known issues.