It did not happen to me yet, but if I dedicate a single SSD (non-RAID) to swap-ONLY and the server system is using it to full capacity - what happens next? How am I to recover, assuming I have an identical, tested and working SSD in my hands, biting my nails to deal with it? Let us assume I have an i3, 32GB RAM server running the latest XUbuntu with xfce. On top of that I am running Oracle's 4.3.20 VirtualBox (vbox), home to many Windows and Linux servers and clients.I understand there are a few scenarios. Scenario A: I share the SSD swap-only drive used by the XUbuntu host with the vbox Linux client's swap files and Windows client's page file.Scenario B: I isolate the XUbuntu host from VirtualBox: my vbox clients never use the hosting Linux's SSD drive for swap. Instead I restart the virtual clients to use more physical resources.Scenario C: I never allow any vbox client to go over half of 32GB, and I force the vbox clients to use their own virtual swap. Whatever the scenario is the SSD is now gone, and I need to deal with it.I am VERY much tempted to go with Scenario A, as it is the most suitable drive for swap and page files, but if the recovery from such failure is complex or impossible, please let me know. B and C is safe, but very limiting.Again, this is only a scenario and it did not happen to me yet. Thanks for reading!
SSD dedicated to swap-only fails on Debian or Ubuntu
hardware;shutdown;ssd;failure