-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a dedicated ZFS SR driver to avoid losing VDI metadata #401
Labels
Comments
stormi
changed the title
Create a dedicated ZFS SR driver
Create a dedicated ZFS SR driver to avoid losing VDI metadata
Jun 15, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Aug 12, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Aug 12, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Aug 12, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Aug 13, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Aug 13, 2020
stormi
pushed a commit
to xcp-ng/sm
that referenced
this issue
Aug 17, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Sep 18, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Sep 18, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Nov 6, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Nov 6, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Dec 14, 2020
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Jan 11, 2021
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Apr 28, 2021
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Apr 29, 2021
xandrus
pushed a commit
to xandrus/sm
that referenced
this issue
May 4, 2021
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
May 27, 2021
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
May 27, 2021
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Jun 22, 2021
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Jan 4, 2022
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Jun 14, 2022
andrey-podko
pushed a commit
to andrey-podko/sm
that referenced
this issue
Aug 16, 2022
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Sep 1, 2022
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Dec 8, 2022
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Dec 8, 2022
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Mar 6, 2023
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Mar 6, 2023
ydirson
pushed a commit
to xcp-ng/sm
that referenced
this issue
Mar 27, 2023
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Apr 17, 2023
ydirson
pushed a commit
to xcp-ng/sm
that referenced
this issue
Apr 20, 2023
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Apr 25, 2023
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Jul 31, 2023
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Sep 18, 2023
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Sep 18, 2023
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Sep 18, 2023
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Oct 13, 2023
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Dec 11, 2023
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Jan 23, 2024
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Feb 6, 2024
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Apr 10, 2024
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Apr 11, 2024
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Jun 12, 2024
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Jun 24, 2024
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Aug 12, 2024
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Aug 13, 2024
benjamreis
pushed a commit
to xcp-ng/sm
that referenced
this issue
Aug 13, 2024
Wescoeur
added a commit
to xcp-ng/sm
that referenced
this issue
Oct 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we allow mounting ZFS through the
file
SR driver, which is convenient because it does not need to know how the data is mounted into the directory.However, that driver cannot detect the situation when the mountpoint is empty because of a (temporary) mount failure, such as what happened to a user who switched to the alternate kernel (which doesn't provide a ZFS driver) for a test. The SR driver sees an empty directory and considers that here are no VDIs anymore in the SR. So it forgets about all those VDIs. Once they are seen again during a later scan, all the metadata about them is lost.
There are built-in protections against this in theActually the protections are not on when the SR type isfile
SR driver for common mountpoints, but ZFS doesn't use such mount points as far as I can tell, so the protection didn't work.file
.A dedicated driver may also include ZFS-specific features (e.g. using ZFS snapshots for snapshots?), but the exact behaviour of the driver is yet to be decided. Maybe start with a
zfsbasic
driver just for fixing the "VDI disappearing" bug?The text was updated successfully, but these errors were encountered: