Actions
action #51833
closed[tools][functional][u] s390p8 is out-of-space in /
Start date:
2019-05-22
Due date:
% Done:
0%
Estimated time:
Updated by nicksinger almost 5 years ago
- Copied to action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with salt added
Updated by nicksinger almost 5 years ago
- Copied to deleted (action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with salt)
Updated by nicksinger almost 5 years ago
- Related to action #51836: Manage (parts) of s390 kvm instances (formerly s390p7 and s390p8) with salt added
Updated by mgriessmeier almost 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
Updated by mgriessmeier almost 5 years ago
- Status changed from Resolved to Feedback
Updated by mgriessmeier almost 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