Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    NO this is manual patch on ubuntu 22 Commented Feb 9 at 12:08
  • 2
    " the kernel patch team rebooted the server and the database crashed" if done without stopping the database server gracefully this is expected behaviour: postgress will automatically do a recovery (mysql does that too). "Is it mandatory to back up the database during kernel patch activity, " --No-- cuz you should already have backups :P Commented Feb 9 at 13:36
  • 2
    Why are you (livepatching?) the kernel when you're going to reboot anyway? Commented Feb 10 at 4:31
  • 3
    You have filesystem corruption, not just a corrupt database. See the "Unmount and run xfs_repair" part Commented Feb 10 at 5:05
  • 3
    Your corruption goes far deeper than just your database. This is filesystem-level corruption. Boot the server/system up in a Live environment and then run xfs_repair from the live environment. You need to start by repairing the XFS filesystem. THEN, you should schedule maintenance and backup periods. VM snapshots as 'restore 'points before you do updates is generally safe, but they are not long term backup solutions and cause issues when you have tons of snapshots and a chain of them to work with. Commented Feb 10 at 5:23