On 17/01/2021 18:22, Graham Perrin wrote:
VirtualBox 5.2.44 r139111 on FreeBSD-CURRENT.
01. Add FreeBSD-12.2-RELEASE-amd64.vhd to a machine
02. use Virtual Disk Manager to resize it to 2.0 TB
03. apply, close
04. boot single user
05. gpart show /dev/ada0
07. observe reported corruption
08. gpart recover /dev/ada0
09. I/O error <https://i.imgur.com/MoUBk6q.png>
10. gpart show /dev/ada0
11. no reported corruption
12. shutdown -r now
13. observe reported corruption:
> gptboot: invalid backup GPT header
<https://i.imgur.com/Mi6hNTM.png>
For me, this seems to be consistently reproducible.
Thoughts?
Boot proceeds and <https://i.imgur.com/c7pfsWC.png> I guess that the
UFS file system is automatically grown, but the reported I/O errors
make me nervous.
% uname -v
FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan 3 20:00:09 GMT
2021
root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
%
With FreeBSD-provided 'FreeBSD-12.1-RELEASE-amd64.vhd', things seem even
worse. Please see, for example, this screen recording:
<https://photos.app.goo.gl/4xE6w5uPmwWGPNxD9>
What's going wrong?
Is it necessary to boot first from something _other_ than the resized
disk, for things such as gpart recover to proceed without I/O error for
the resized disk?
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
