[Bug 247696] Boot fails when attempting to mount with gmirror disk from different o/s release

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247696

            Bug ID: 247696
           Summary: Boot fails when attempting to mount with gmirror disk
                    from different o/s release
           Product: Base System
           Version: 12.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: bfriedman at emax.ca

In order to upgrade a server running 10.4 using gmirror,  shutdown the system
and removed one disk.  Installed the disk on another machine and proceeded to
upgrade to 12.1-release-p2.  Installed a new disk on 10.4 system and rebuilt
the mirror.
Once the 12.1 system build was stable did a gmirror remove on the rebuilt
mirror on 10.4 and removed the spare disk. Brought the spare disk over to the
new system and attempted a boot with both disks present.  The boot produced a
series of  "init getting kqueues resource limit: Invalid argument" messages. 
When I attempted to login the login failed and returned to the login: prompt, 
Syslog showed the Invalid argument message.  Disabling the spare disk, 12.1
booted as normal. Attempted to boot the 10.4 system which was on the spare disk
and this failed to mount /.

Brought the spare disk back to the 10.4 system and the system booted.

I believe there is some kind of a mismatch between the 10.4 gmirror disk and
what 12.1 is expecting.  

At this point I have both systems running, should anyone like to have me
troubleshoot this.  My plan at the moment is to disable the gmirror on the 10.4
system and mount both disks stand alone.  Then re-format the spare.  I would
also like to destroy the 12.1 mirror and proceed to rebuild the mirror from
scratch although I am not sure that that is safe.

Setting component to kern although it might be gnu.

-- 
You are receiving this mail because:
You are the assignee for the bug.