!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
I'm sure there's probably some sort of mdadm invocation to shrink an existing RAID1 mirror pair, but in the absence of that, one option is to create the mirror pair you want on your 2.5" SSDs, and then shrink-and-clone the filesystem from the NVMe mirror to the 2.5" SSDs, using something like Gparted.
In that way, you end up with the mdadm pair that you wanted, and the filesystem is correctly sized. You can even clone the UUIDs for the filesystem so fstab entries won't have to be changed.
Uhm... why don't you just move the contents over, then change all references to the new file systems? (fstab, boot loader, etc.)
Yeah, I've considered that - Remake the mdraid and partition schema on the correct drives, and then rsync everything over. It's just a lot more manual than what I was hoping for was possible.
It's probably just a technicality, but I would not use rsync, but tar -cp ...|tar -xvpC ...
Depending on how you made the images, you can probably also mount and change them or extract just the files etc.
Edit: disregard this. I have gotten my wires crossed somewhere.
~~tar cannot preserve hard links, where rsync can. Definitely something to bear in mind before doing a full drive copy.~~
As for why anyone would choose hard links over symlinks, sometimes, for some purposes, it's not clear which file should be the target and which the link and also, symlinks - especially explicit, non-relative symlinks - are very easily broken when files are moved around. Patching them all can be a pain.
you mixed something up tar can and will preserve hard links by default
I could have sworn that the last time I tried to tar-copy part of a filesystem containing hard links that I ended up with copies everywhere rather than preservation of the hard links, and the tar manual page isn't particularly clear about it at all.
But it looks like I've misremembered because a quick test with tar confirms that it detects and saves hard links, and they unpack correctly too. Now I'm wondering precisely what it was that I was doing where I ended up with all those copies.
maybe the target file system didn't support hard links. hard to say.
This! I've done it many a time following 3.7 Full system backup. For some reason can't get table of contents to load on mobile and get a proper anchor link.