Date: Fri, 18 Sep 2020 04:41:20 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 222425] GPT broken after "gpart backup ada0 | gpart restore -F ada1" Message-ID: <bug-222425-227-zBfcki8X2V@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222425-227@https.bugs.freebsd.org/bugzilla/> References: <bug-222425-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222425 --- Comment #15 from Louis <lrb@minmet.org> --- (In reply to Christos Chatzaras from comment #14) Interesting. In my case, I wasn't trying to set up gmirror, but just to copy a 500 GB di= sk onto a 2 TB one, because I was running out of space. (The machine is my desktop, incidentally.) I did this backup/restore thing, figured I'd keep the 1st partition, and delete/recreate the others with larger sizes. Maybe that also had something= to do with triggering the bug. I do wonder why I'm not using the occasion to switch to ZFS. Probably becau= se I'm a bit conservative and don't fully trust it yet, LOL. So I get these problems instead! I have other boxes set up with UFS and gmirror and did manage to get them to the point where they'd boot off either drive. Somehow, I didn't end up triggering the bug that time. I wonder why not. Maybe because I didn't try = to delete/recreate any partitions? It reminds me of the interesting time I = had setting up gmirror on a hosted server, where FreeBSD isn't supported, and I= was trying to do it without having to have a KVM put in. I did manage it once, = but only after practicing it on a test box at home first! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222425-227-zBfcki8X2V>