Skip to content
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

Add a data persistence test #1763

Open
jlebon opened this issue Jul 17, 2024 · 2 comments
Open

Add a data persistence test #1763

jlebon opened this issue Jul 17, 2024 · 2 comments

Comments

@jlebon
Copy link
Member

jlebon commented Jul 17, 2024

We claim to support data persistence across reprovisions:

We should have a test for it. This would've caught #1745.

@Nemric
Copy link

Nemric commented Aug 9, 2024

Hi Jonathan,
I did read carefully this link https://docs.fedoraproject.org/en-US/fedora-coreos/live-booting/#_using_persistent_state and

Avoid writing persistent data to RAID volumes, since Ignition cannot reuse those.

I use raid like this :

variant: fcos
version: 1.5.0

storage:
  raid:
    - name: Raid
      level: mirror
      devices:
        - /dev/disk/by-id/ata-WDC_WD10SPZX-80Z10T2_WD-WX41A49H9FT4
        - /dev/disk/by-id/ata-WDC_WD10SPZX-80Z10T2_WD-WXL1A49KPYFD
      options:
        - --metadata=1.2
        - --assume-clean
        - --uuid=7ec8d4df:823fae52:c55d5e56:e773b281

  filesystems:
    - path: /var
      device: /dev/md/Raid
      format: xfs
      label: Var
      wipe_filesystem: false
      with_mount_unit: true

I now only use pxe booted nodes (5 nodes) all of them have persistent storage without encryption, and one of them have raid mirroring drives, all nodes are re-provisioned at least every 2 weeks (CoreOS updates) and it works well since ... let's say ... close to first stable CoreOS release

I didn't use these arguments at first use of this butane file, but for reboot only :

the --assume-clean setting avoid rebuild of raid array on reboot, fortunately, a check is done weekly thanks to a raid-check.service and raid-check.timer on sunday morning

when using mdadm --detail --scan after first boot I did get array uuid so I did set it in butane to avoid conflicts (can't say if I'm right :D ) : --uuid=7ec8d4df:823fae52:c55d5e56:e773b281

I can't remember if I really use `--metadata=1.2' at first boot :/

Of course I have no spare drives and I don't know what will happen when actual ones will die ! at the same time ?! Same provider, same buy date, same reference, ...

so I think we can use raid device with live environment but at our own risks ;)

@jlebon
Copy link
Member Author

jlebon commented Aug 9, 2024

I think that doc item is talking about coreos/ignition#579. The workaround above probably belongs there instead.

so I think we can use raid device with live environment but at our own risks ;)

Yeah, agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants