Opened 5 years ago

Closed 5 years ago

#1508 closed error (answered)

Weird glitch/error on PUMA. (Problem with vi / tmp on PUMA)

Reported by: mbollasi Owned by: um_support
Component: PUMA Keywords:
Cc: oliver.browne@… Platform: PUMA
UM Version: <select version>

Description

Hello,

I was trying to edit my SUBMIT file for job xlaxa on puma at 1pm today. The SUBMIT file is here..

/home/mbollasi/umui_jobs/xlaxa/SUBMIT

and I was using vi when I got the error message below.

I spoke to Oliver about it a few minutes ago, and we saw the same error message.

Oliver told me it looked more like an error with the tmp/ space, rather than anything I could have done.

We tried to delete the file to moved on, but upon doing so the directory contents disappeared. When we moved up the directory chain, things reappeared, and now when I try to edit the file everything seems fine.

I appreciate that these kind of one-off behaviours are difficult to reproduce and track down, but I felt I should report it all the same, in case there is some other bigger problem going on.

ciao,

Massimo

E325: ATTENTION
Found a swap file by the name "/var/tmp/SUBMIT.swp"
          owned by: swr05npk   dated: Wed Dec 22 21:12:31 2010
         [cannot be opened]
While opening file "SUBMIT"

(1) Another program may be editing the same file.
    If this is the case, be careful not to end up with two
    different instances of the same file when making changes.
    Quit, or continue with caution.

(2) An edit session for this file crashed.
    If this is the case, use ":recover" or "vim -r SUBMIT"
    to recover the changes (see ":help recovery").
    If you did this already, delete the swap file "/var/tmp/SUBMIT.swp"
    to avoid this message.

Swap file "/var/tmp/SUBMIT.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:

Change History (1)

comment:1 Changed 5 years ago by annette

  • Resolution set to answered
  • Status changed from new to closed

Hi Massimo,

We haven't seem this behaviour before so assume it is a one-off, but it has been noted by our sys admin. Thanks for letting us know.

Best regards,
Annette

Note: See TracTickets for help on using tickets.