• 1 Post
  • 4 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Cenzorrll@lemmy.worldOPtoSelfhosted@lemmy.worldLVM question
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 days ago

    I try keep my data drives and boot drives separate on my servers, I make sure I can rebuild the server relatively easily so no matter what happens I can get back up and running. In my research on LVMs I wasn’t seeing anything saying you could just move the drives to a new setup, that you had to export and import first. In the case of a suddenly dead boot drive, I wouldn’t be able to do that. I did see some steps for backing up an LVMs metadata and recovering from that, so I might be sure I do that at some point, but another user said that modern distros should be able to scan for LVMs without issue, which is not what I found in my quick test in my setup. So I’ll be checking that out in a more modern setup to double check.

    From what I was reading, recovering from corrupted metadata is not something I want to do. I’d rather not use LVM if that’s what’s required if I can’t just move the drives to a new server, as nice as it would be to resize filesystems on a whim.


  • Cenzorrll@lemmy.worldOPtoSelfhosted@lemmy.worldLVM question
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 days ago

    I did not find just moving the drives to work. There were some other issues that I came across that might have a part to play in it, I made the lvm and filesystem on an RPI5 running OMV and moved it to a rock3c running OMV from an armbian install. Turns out there’s a pagefile size mismatch between the two that prevented mounting the btrfs filesystem. But I still wasn’t able to get the rock3c to recognize the VG or that there were new PVs attached without exporting first. So perhaps the armbian install isn’t modern enough to automatically recognize it.

    I didn’t expect learning new things about btrfs to be the outcome of this little experiment, but I guess that’s just how things work.


  • Cenzorrll@lemmy.worldOPtoSelfhosted@lemmy.worldLVM question
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    That’s kind of what I figured, my biggest concern at this point would be how difficult it is to move the lvm volume to a different device. It seems pretty straightforward if you have a working setup, but from what I’m seeing in my research is silence if your device (server, etc.) dies and you need to move those volumes to another. I’m finding guides on either recovering from corruption or lost metadata, or transferring from one working device to another. Nothing I can find about importing a fully functional lvm to a new device if it hasn’t been exported.

    I’ll be able to do that later today, so I guess I’ll see what happens if I do. Better to try it out now when it isn’t critical.



  • I try to keep lossless on my server for the fact that new algorithms come out all the time. I don’t want to be stuck with a 160k mp3 when a better algorithm comes out or if I need to stream just a little lower than that. I’d rather have lossless quality that can be converted at any time to whatever I need, even though I mostly have it set to 160k for listening if I’m streaming away from home. My work internet and cell service can get really terrible, and being able to buffer 10 songs when I get a few minutes of service is a godsend while not getting stuck with low quality, several times converted files, or keeping multiple bitrate versions of the same song.