release loop device on SLURM

[Andre Zonca]

At the end of a SLURM job I get:

ERROR : Could not clear loop device /dev/loop0: (16) Device or resource busy

 

Do you have any suggestion to improve cleanup of the job?

Thanks!
Andre

[Gregory M. Kurtzer]

I am assuming this is version 1.2.1?

The only reason you should get that is if there are background processes still running. Can you check to see if that was the case?

--
You received this message because you are subscribed to the Google Groups "singularity" group.
To unsubscribe from this group and stop receiving emails from it, send an email to singularity+unsubscribe@lbl.gov.

--

Gregory M. Kurtzer

HPC Systems Architect and Technology Developer

Lawrence Berkeley National Laboratory HPCS
University of California Berkeley Research IT
Singularity Linux Containers (http://singularity.lbl.gov/)

Warewulf Cluster Management (http://warewulf.lbl.gov/)

GitHub: https://github.com/gmkurtzer, Twitter: https://twitter.com/gmkurtzer

[Andre Zonca]

Thanks,

2.2,

I added a ps aux > processes after calling singularity, any better way?

Owned by my user I see only ps aux and the slurm script.

On Tuesday, September 20, 2016 at 6:03:34 PM UTC-7, Gregory M. Kurtzer wrote:

I am assuming this is version 1.2.1?

The only reason you should get that is if there are background processes still running. Can you check to see if that was the case?

On Tue, Sep 20, 2016 at 6:01 PM, Andre Zonca <andrea...@gmail.com> wrote:

At the end of a SLURM job I get:

ERROR : Could not clear loop device /dev/loop0: (16) Device or resource busy

 

Do you have any suggestion to improve cleanup of the job?

Thanks!
Andre

--
You received this message because you are subscribed to the Google Groups "singularity" group.

To unsubscribe from this group and stop receiving emails from it, send an email to singularity...@lbl.gov.

[Gregory M. Kurtzer]

Hi Andre,

Can you send the rest of your command, and perhaps a debug output (singularity --debug ....). Version 2.2 should not be calling the function that emits that error message unless there was another error message also associated with it (regarding failure to set flags).

Maybe it is possible the node that ran the job is running an older version of Singularity?

Greg

To unsubscribe from this group and stop receiving emails from it, send an email to singularity+unsubscribe@lbl.gov.