search

kasmtech / workspaces-issues

20 stars 5 forks source link

[Bug] - Persistent Profile Data Loss #622

Open jm1021 opened 2 months ago

jm1021 commented 2 months ago

Existing Resources

Describe the bug I have about 40 people using Kasm MultiServer for about 3 weeks. We get about 2 a day that experience data corruption on their Persistent Profile Path. It is not a full data loss but I notice these two things every time.

  1. "bundle" script in gem is lost
  2. "github projects .git corruption, it is every github project we typically work with 2 or 3

Also, we need to delete the home directory on S3, A re-install of tools on corrupted home directory only survives the session. After deleting the S3 persistent mount, the user has success for many days.

To Reproduce This is the string used in the workspaces for Persistent Profile Path was found in documentation.

s3://kasm-profile/{image_id}/{username}/

Expected behavior No data loss.

Screenshots Partial list of mounts on S3

image

Workspaces Version Version 1.15

Workspaces Installation Method Multi-Server

Client Browser (please complete the following information): N/A

Workspace Server Information (please provide the output of the following commands):

default:~$ uname -a
Linux kasm 6.5.0-1022-aws #22~22.04.1-Ubuntu SMP Fri Jun 14 16:31:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux 
default:~$ cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Additional context Is there recommendation to preserve data? Always "Delete" the session? Is there a known bug or patch as I see something about small files lost on S3 mounted drives in 1.16 plans.

jm1021 commented 1 month ago

Is there a persistent profile outstanding issues or best practices for 1.16 with AWS S3. We had data loss on 1.15 and things seem to be worse on 1.16. We are trying to use the machines for student development and have a lot of "little files" and "multiple projects".