Project

General

Profile

action #51833

[tools][functional][u] s390p8 is out-of-space in /

Added by okurz over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Target version:
-
Start date:
2019-05-22
Due date:
% Done:

0%

Estimated time:

Related issues

Related to openQA Infrastructure - action #51836: Manage (parts) of s390p7 and s390p8 with saltBlocked2019-05-22

History

#1 Updated by nicksinger over 3 years ago

  • Copied to action #51836: Manage (parts) of s390p7 and s390p8 with salt added

#2 Updated by nicksinger over 3 years ago

  • Copied to deleted (action #51836: Manage (parts) of s390p7 and s390p8 with salt)

#3 Updated by nicksinger over 3 years ago

  • Related to action #51836: Manage (parts) of s390p7 and s390p8 with salt added

#4 Updated by mgriessmeier over 3 years ago

  • Status changed from New to Resolved
  • Assignee set to mgriessmeier

so Today we learned that s390p8 is apparently not reboot safe, as it got rebooted 3 days ago and the fcp data disk was not mounted - so everything ended up in the / disk which is obviously way too small for that.
should work now again

#5 Updated by mgriessmeier over 3 years ago

  • Status changed from Resolved to Feedback

#6 Updated by mgriessmeier over 3 years ago

  • Status changed from Feedback to Resolved

s390p8 is now reboot safe in regards of mounting the correct disks at bootup.
there was a duplicate entry in the fstab, that's why it failed before - I have no clue where it came from

considering as resolved

Also available in: Atom PDF