Project

General

Profile

Actions

action #51833

closed

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

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

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

0%

Estimated time:

Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with saltResolvedokurz2019-05-22

Actions
Actions #1

Updated by nicksinger over 5 years ago

  • Copied to action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with salt added
Actions #2

Updated by nicksinger over 5 years ago

  • Copied to deleted (action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with salt)
Actions #3

Updated by nicksinger over 5 years ago

  • Related to action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with salt added
Actions #4

Updated by mgriessmeier over 5 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

Actions #5

Updated by mgriessmeier over 5 years ago

  • Status changed from Resolved to Feedback
Actions #6

Updated by mgriessmeier over 5 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

Actions

Also available in: Atom PDF