installation on pvscsi fails with "The request was too large for this host"

[Yuri Pankov]

Trying to install latest snapshot (20201210) on a VMware 
ESXi/Workstation VMs with pvscsi fails on bootloader step, and the 
following is in dmesg:


pvscsi0: pvscsi_execute_ccb error 27
pvscsi0: pvscsi_execute_ccb error 27
(da0:pvscsi0:0:0:0): WRITE(10). CDB: 2a 00 00 00 00 28 00 04 00
(da0:pvscsi0:0:0:0): CAM status: The request was too large for this host
(da0:pvscsi0:0:0:0): Error 22, Unretryable error
(da0:pvscsi0:0:0:0): WRITE(10). CDB: 2a 00 00 00 00 28 00 04 00
(da0:pvscsi0:0:0:0): CAM status: The request was too large for this host
(da0:pvscsi0:0:0:0): Error 22, Unretryable error

That is the first I'm trying installing on pvscsi since it was 
integrated, so no idea if it worked previously.  If yes, I have not 
tried to bisect this yet hoping that it could be identified as related 
to any of the recent changes.


The VMs in question are set with 8-64 GB RAM, and 100 GB boot disks.
___
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"

HEADS UP: FreeBSD src repo transitioning to git this weekend

[Warner Losh]

Greetings,

The FreeBSD project will be moving it's source repo from subversion to git
starting this this weekend. The docs repo was moved 2 weeks ago. The ports
repo will move at the end of March, 2021 due to timing issues.

The short version is that we're switching the version control we're using.
This switch will preserve much of the current FreeBSD development workflow.
After the switch, the subversion repo will become almost read-only. All
future work will be done in git, however as a transition aide we'll be
replaying the MFCs to stable/11, stable/12 and the related releng branches
for the life of those branches.

For more detailed information, please see
https://github.com/bsdimp/freebsd-git-docs/ for the current documentation.

Please see https://wiki.freebsd.org/git for the latest detailed schedule
(please note that this schedule is subject to change).

Warner
___
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"

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

[Ryan Moeller]

On 12/13/20 12:25 PM, John Kennedy wrote:

On Sun, Dec 13, 2020 at 08:19:30AM +, Graham Perrin wrote:

Please: is there some way to include openzfs-kmod at buildkernel time?



Not that I'm aware of, but you can write a script to build your system 
the way you like it and then build the kmod, clone a BE, etc, so you 
don't forget anything.




To work around
 I habitually
remove openzfs-kmod from /etc/src.conf _and_ modify /boot/loader.conf
before performing the build:

zfs_load="YES"
openzfs_load="NO"

Isn't openzfs-kmod on 13-CURRENT more or less moot since r36474, the OpenZFS
merge, ~2020/8/25?  That ticket was opened on 2019/7/28, pre-merge.



The port tracks the openzfs/zfs master branch while the base system 
tracks the zfs-2.0-release branch. However, that is planned to switch to 
master once base makes the transition to git.




Now, I still see recent updates on openzfs-kmod port so the question might
still be relevant for non-13 or if you're just using the port for reasons or
anywhere older than 13 (12.2, etc).



If the newer features in master (eg draid) aren't needed, the base zfs 
is at least less likely to break from kernel changes that haven't been 
coordinated well with the openzfs upstream and the port, which does 
happen from time to time.



-Ryan

___
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"