Re: Deprecating base system ftpd?
On 06/04/2021 11:29, Stefan Bethke wrote: Am 05.04.2021 um 21:01 schrieb Patrick M. Hausen : But still even on "the Internet", FTP is the most used method for customers of static website hosting. You cannot teach these people what an SSH key is. Just my experience, but backed by a load of customer interactions over more than 20 years ... Strato did disable FTP access over a year ago, and instructed customers on how to use SSH-based access instead, so it's definitely possible, and people are moving towards more secure protocols, even when (non-technical) end users are affected. Working for small / average web hosting company - we disabled plaintext FTP over 15 years ago. All customers are able to use FTP client supporting FTPeS (FTP with explicit TLS). So it definitely is possible if there is a will or enough pressure on customers. On the other hand it does not matter to me if ftpd will be shipped in FreeBSD base for next 10 years. It is just a matter of maintaining it / man power for each release, testing etc. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Deprecating base system ftpd?
On 03/04/2021 22:39, Ed Maste wrote: I propose deprecating the ftpd currently included in the base system before FreeBSD 14, and opened review D26447 (https://reviews.freebsd.org/D26447) to add a notice to the man page. I had originally planned to try to do this before 13.0, but it dropped off my list. FTP is not nearly as relevant now as it once was, and it had a security vulnerability that secteam had to address. I'm happy to make a port for it if anyone needs it. Comments? I am on FreeBSD for more than 20 years, running FTP service on almost all our servers but it never was ftpd from base. I saw other comments against removing it but from my point of view ftpd in base is useless for me. And I don't see much cases where FTP service is needed before any other package / port can be installed. As always there will be at least two groups of users one for, one against. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: build failed for 12.2-p5
On 27/03/2021 14:23, Miroslav Lachman wrote: On 27/03/2021 13:57, Juraj Lutter wrote: On 27 Mar 2021, at 13:24, Miroslav Lachman <000.f...@quip.cz> wrote: [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken *** Error code 1 *** Error code 1 *** Error code 1 Usr: 399.369s Krnl: 9.440s Totl: 6:48.81s CPU: 99.9% swppd: 0 I/O: 2907+51057 This machine built 12.2-p4 two days ago and the failure is always on the same point so I do not suspect random HW failure but of course it can be new HW problem. Did you do a source-upgrade from 11.4 to 12.2? If yes, then did you also do `make delete-old` and `make delete-old-libs` after upgrade? Yes it was source upgrade from 11.4 to 12.2 but no, make delete-old was not run. Waited to upgrade all packages. I will try it soon. Thanks for the pointer. In the meantime I tired to rebuild 12.2-p4 again and it failed at the same point on libroken. I will go for make delete-old + delete-old-libs before the next test. The same error is there after make delete-old + delete-old-libs again. I am out of ideas. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: build failed for 12.2-p5
On 27/03/2021 13:57, Juraj Lutter wrote: On 27 Mar 2021, at 13:24, Miroslav Lachman <000.f...@quip.cz> wrote: [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken *** Error code 1 *** Error code 1 *** Error code 1 Usr: 399.369s Krnl: 9.440s Totl: 6:48.81s CPU: 99.9% swppd: 0 I/O: 2907+51057 This machine built 12.2-p4 two days ago and the failure is always on the same point so I do not suspect random HW failure but of course it can be new HW problem. Did you do a source-upgrade from 11.4 to 12.2? If yes, then did you also do `make delete-old` and `make delete-old-libs` after upgrade? Yes it was source upgrade from 11.4 to 12.2 but no, make delete-old was not run. Waited to upgrade all packages. I will try it soon. Thanks for the pointer. In the meantime I tired to rebuild 12.2-p4 again and it failed at the same point on libroken. I will go for make delete-old + delete-old-libs before the next test. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: build failed for 12.2-p5
On 27/03/2021 12:57, Dimitry Andric wrote: On 27 Mar 2021, at 12:39, Miroslav Lachman <000.f...@quip.cz> wrote: [...] # make -DNO_CLEAN buildkernel cc -O2 -pipe -fno-common -I/usr/src/crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/include -g -MD -MF.depend.copyhostent.o -MTcopyhostent.o -std=gnu99 -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -c /usr/src/crypto/heimdal/lib/roken/copyhostent.c -o copyhostent.o /usr/src/crypto/heimdal/lib/roken/copyhostent.c:42:1: error: unknown type name 'ROKEN_LIB_FUNCTION' ROKEN_LIB_FUNCTION struct hostent * ROKEN_LIB_CALL ^ /usr/src/crypto/heimdal/lib/roken/copyhostent.c:42:51: error: expected ';' after top level declarator ROKEN_LIB_FUNCTION struct hostent * ROKEN_LIB_CALL ^ ; Since the roken.h file is bad, it won't compile. Delete the bad roken.h, or maybe your entire /usr/obj, and after your hardware turns out to be okay, try again. I repeatedly deleted /usr/src and /usr/obj and it always failed on roklen. This is from the last attempt from clean src and obj on the first run with "make buildworld" sh /usr/src/tools/install.sh -o root -g wheel -m 444 make-roken.debug /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib/debug/usr/bin/make-roken.debug ===> kerberos5/lib/libroken (obj,all,install) [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken *** Error code 1 *** Error code 1 *** Error code 1 Usr: 399.369s Krnl: 9.440s Totl: 6:48.81s CPU: 99.9% swppd: 0 I/O: 2907+51057 This machine built 12.2-p4 two days ago and the failure is always on the same point so I do not suspect random HW failure but of course it can be new HW problem. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
build failed for 12.2-p5
I compiled 12.2-p4 from sources 2 days ago but any attempt to build update for 12.2-p5 ends with error. Previous build was done on 11.4: # cd /usr/src/ # git clone https://github.com/freebsd/freebsd.git -b releng/12.2 ./ # make buildworld # make buildkernel 11.4 machine was upgraded to 12.2 (I did also run mergemaster) so now I have FreeBSD 12.2-RELEASE-p4 amd64 GENERIC # cd /usr/src/ # git pull --ff-only # make -DNO_CLEAN buildworld it ends with the following error sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 xinstall /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin/install sh /usr/src/tools/install.sh -o root -g wheel -m 444 install.debug /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib/debug/usr/bin/install.debug *** Signal 11 Stop. make[3]: stopped in /usr/src/usr.bin/xinstall *** Error code 1 Usr: 437.951s Krnl: 15.620s Totl: 7:48.92s CPU: 96.7% swppd: 0 I/O: 55800+84576 I tried without -DNO_CLEAN but it failed again sh /usr/src/tools/install.sh -o root -g wheel -m 444 make-roken.debug /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib/debug/usr/bin/make-roken.debug ===> kerberos5/lib/libroken (obj,all,install) [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken *** Error code 1 Usr: 398.859s Krnl: 10.054s Totl: 7:07.24s CPU: 95.7% swppd: 0 I/O: 8544+51057 OK I deleted all sources and clone again # git clone https://github.com/freebsd/freebsd.git -b releng/12.2 ./ # make buildworld objcopy --only-keep-debug make-roken.full make-roken.debug objcopy --strip-debug --add-gnu-debuglink=make-roken.debug make-roken.full make-roken sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 make-roken /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin/make-roken sh /usr/src/tools/install.sh -o root -g wheel -m 444 make-roken.debug /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib/debug/usr/bin/make-roken.debug ===> kerberos5/lib/libroken (obj,all,install) [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken *** Error code 1 Usr: 399.257s Krnl: 9.732s Totl: 6:49.00s CPU: 99.9% swppd: 0 I/O: 3080+51057 # make -DNO_CLEAN buildkernel cc -O2 -pipe -fno-common -I/usr/src/crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/include -g -MD -MF.depend.copyhostent.o -MTcopyhostent.o -std=gnu99 -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -c /usr/src/crypto/heimdal/lib/roken/copyhostent.c -o copyhostent.o /usr/src/crypto/heimdal/lib/roken/copyhostent.c:42:1: error: unknown type name 'ROKEN_LIB_FUNCTION' ROKEN_LIB_FUNCTION struct hostent * ROKEN_LIB_CALL ^ /usr/src/crypto/heimdal/lib/roken/copyhostent.c:42:51: error: expected ';' after top level declarator ROKEN_LIB_FUNCTION struct hostent * ROKEN_LIB_CALL ^ ; 2 errors generated. *** Error code 1 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken *** Error code 1 What can caused this error? Am I the only one who cannot build 12.2-p5? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pf and hnX interfaces
On 13/10/2020 11:19, Kristof Provost wrote: On 13 Oct 2020, at 10:58, Eugene M. Zheganin wrote: Is there some issue with pf and hn interfaces that I'm unaware about? There’s no interface specific code in pf, so it wouldn’t be specific to hn interfaces. Are these symptoms of a bug ? Perhaps. It can also be a symptom of resource exhaustion. Are there any signs of memory allocation failures, or incrementing error counters (in netstat or in pfctl)? I have seen this kind of errors in VirtualBox with PF and emulated Intel interface (emX) Oct 1 22:42:19 bobik postfix/smtp[35330]: connect to aspmx.l.google.com[108.177.126.27]:25: Permission denied Oct 1 22:42:19 bobik postfix/smtp[36246]: connect to aspmx.l.google.com[108.177.126.27]:25: Permission denied Oct 1 22:42:19 bobik postfix/smtp[35330]: connect to alt2.aspmx.l.google.com[108.177.97.27]:25: Permission denied Oct 1 22:42:19 bobik postfix/smtp[36246]: connect to alt1.aspmx.l.google.com[172.253.118.27]:25: Permission denied Oct 1 22:42:19 bobik postfix/smtp[35330]: connect to alt1.aspmx.l.google.com[172.253.118.27]:25: Permission denied Oct 1 22:42:19 bobik postfix/smtp[36246]: connect to alt2.aspmx.l.google.com[108.177.97.27]:25: Permission denied I think it is related to states table exhaustion (reported in freebsd-pf@ mailing list about a week ago). My firewall rules are open for all outgoing traffic. So I think your problem is related to some resource exhaustion too. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
device /dev/cd1 not visible
I have an internal DVD-ROM detected as /dev/cd0 which works OK. When I plug the external USB DVD-RW drive it is show in messages as: Jun 20 16:36:11 illbsd kernel: ugen1.4: Device> at usbus1 Jun 20 16:36:11 illbsd kernel: umass0 on uhub3 Jun 20 16:36:11 illbsd kernel: umass0: Device, class 0/0, rev 2.00/1.03, addr 4> on usbus1 Jun 20 16:36:11 illbsd kernel: umass0: SCSI over Bulk-Only; quirks = 0x0100 Jun 20 16:36:11 illbsd kernel: umass0:4:0: Attached to scbus4 Jun 20 16:36:11 illbsd kernel: cd1 at umass-sim0 bus 0 scbus4 target 0 lun 0 Jun 20 16:36:11 illbsd kernel: cd1: Removable CD-ROM SCSI device Jun 20 16:36:11 illbsd kernel: cd1: 40.000MB/s transfers Jun 20 16:36:11 illbsd kernel: cd1: 612MB (313585 2048 byte sectors) Jun 20 16:36:11 illbsd kernel: cd1: quirks=0x10<10_BYTE_ONLY> # camcontrol devlist at scbus0 target 0 lun 0 (pass0,ada0) at scbus1 target 0 lun 0 (pass1,ada1) at scbus2 target 0 lun 0 (cd0,pass2) at scbus3 target 0 lun 0 (pass3,ses0) at scbus4 target 0 lun 0 (pass4,cd1) But there is no /dev/cd1 device: # ls -l /dev/cd* crw-rw-rw- 1 root operator 0xb2 20 Jun 16:33 /dev/cd0 lrwxr-xr-x 1 root wheel3 20 Jun 08:09 /dev/cdrom -> cd0 I thought it will be there automatically. Is there something I can do to make second drive work? # uname -srmi FreeBSD 11.3-RELEASE-p9 amd64 GENERIC Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stucked on reading bad cd-rom
On 15/06/2020 13:41, Eugene Grosbein wrote: 15.06.2020 18:10, Miroslav Lachman wrote: I am running FreeBSD 11.3. Whenever I inserted some 20 year old CD (backups on CD-R) which is currently unreadable the system is trying to read the CD even after I want to eject it by button in the CD drive or "eject" command. These messages are repeatedly logged in messages Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): Error 6, Unretryable error Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): cddone: got error 0x6 back Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 11 00 Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): CAM status: SCSI Status Error Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): SCSI status: Check Condition Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): SCSI sense: NOT READY asc:3a,2 (Medium not present - tray open) It can take from 1 to 5 minutes from pressing eject to actually open the drive. Is there something I can do to not wait too long for this? Any tuneables or command to interrupt endless reading? Perhaps it's GEOM doing multiple "taste" attempts to detetmine logical format of the media. Try setting "sysctl kern.geom.notaste=1" temporary. It seems it helped. Thank you! Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
stucked on reading bad cd-rom
I am running FreeBSD 11.3. Whenever I inserted some 20 year old CD (backups on CD-R) which is currently unreadable the system is trying to read the CD even after I want to eject it by button in the CD drive or "eject" command. These messages are repeatedly logged in messages Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): Error 6, Unretryable error Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): cddone: got error 0x6 back Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 11 00 Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): CAM status: SCSI Status Error Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): SCSI status: Check Condition Jun 15 13:05:28 illbsd kernel: (cd0:ahcich2:0:0:0): SCSI sense: NOT READY asc:3a,2 (Medium not present - tray open) It can take from 1 to 5 minutes from pressing eject to actually open the drive. Is there something I can do to not wait too long for this? Any tuneables or command to interrupt endless reading? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Chris wrote on 04/18/2020 04:33: On Fri, 17 Apr 2020 08:17:56 +0200 Miroslav Lachman 000.f...@quip.cz said Chris wrote on 04/17/2020 05:51: > On Thu, 16 Apr 2020 19:57:21 -0700 Mel Pilgrim > list_free...@bluerosetech.com said > >> On 2020-04-16 12:30, Miroslav Lachman wrote: >> > Pete Wright wrote on 04/16/2020 20:23: >> >> >> >> >> >> On 4/16/20 11:12 AM, Miroslav Lachman wrote: >> >>> Kurt Jaeger wrote on 04/16/2020 20:07: >> > >> I would try booting via UEFI if you can. I just installed a >> laptop >> yesterday which has a nvme root device, it was detected by >> the >> 12-STABLE snapshot I used to boot from. no other modifications >> were >> necessary on my end. >> > > I changed BIOS settings to use UEFI boot method, booted 12.1 >> installer > ISO but without luck. Still no NVME disks :( >> > > You can see it on printscreen from iDRAC https://ibb.co/tPnymL7 >> > > Anything more I can test? >> >> Looking at server specs, the R6515's NVME support is only through the >> PERC S150 RAID controller. If that's the case, I'm pretty sure you're >> out of luck. The PERC S-series controllers are software-based RAID >> that require Dell's Windows or Linux drivers. You'd need a PERC >> H-series card to get support in FreeBSD. That's something I didn't expect at all. So there is nothing which can be fixed on FreeBSD side? :( >> Someone please correct me if I'm wrong? > As I mentioned. I was suspicious of this. He should be able to flash the > card, > making it a pass. I do a lot of them. If someone doesn't beat me to it. > I'll > dig through what I have, and see if I can't find the right image(s), and > program(s). This is rented dedicated machine. I cannot flash anything on it. Apologies for the late reply. Unfortunately $JOB requires me to $WORK. :( OK Given these are rentals. Probably the most I could supply for your needs are images that allow you to poll, and change settings of the controller(s). I have cd9660, and USB flash images of the utilities for the 100-300 series HBAs as provided by LSI/AvGO. They boot to (MS)DOS, or to an (U)EFI prompt. Having read what I can; the S150 controller is Software controlled (likely explaining the "S" in it's model number), and as I understand it *shouldn't* require any flashing. As I also understand you *should* be able to access control of it through UEFI configs. I *think* accessed via F2. Apologies if this comes too late, or you've already solved this. If you're still interested in the management software I have for the 100-300 series. Let me know, and I'll attach a copy, or provide a link for you as needed. As you already noticed Scott Long is helping me in current@ list. He thinks some devices are not probed during boot. I hope this problem can be solved by some "easy" patch. Thank you for your help! Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Miroslav Lachman wrote on 04/17/2020 08:17: Looking at server specs, the R6515's NVME support is only through the PERC S150 RAID controller. If that's the case, I'm pretty sure you're out of luck. The PERC S-series controllers are software-based RAID that require Dell's Windows or Linux drivers. You'd need a PERC H-series card to get support in FreeBSD. That's something I didn't expect at all. So there is nothing which can be fixed on FreeBSD side? :( Someone please correct me if I'm wrong? As I mentioned. I was suspicious of this. He should be able to flash the card, making it a pass. I do a lot of them. If someone doesn't beat me to it. I'll dig through what I have, and see if I can't find the right image(s), and program(s). This is rented dedicated machine. I cannot flash anything on it. I can ask the provider if they can install some card. Do you have some recommendation? What is supported by Dell and FreeBSD for ZFS? I really appreciate your help! I tried to find info about controller in the iDRAC. I walk through the System / Inventory / Hardware Inventory and found nothing about S130 I found this informations PCIe SSD in Slot 1 in Bay 1 Bus: 82 BusProtocol: PCIE Device: 0 DeviceDescription: PCIe SSD in Slot 1 in Bay 1 DeviceProtocol: NVMe-MI1.0 DeviceType: PCIeSSD DriveFormFactor: 2.5 inch FailurePredicted: NO FQDD: Disk.Bay.1:Enclosure.Internal.0-1 FreeSizeInBytes: Information Not Available Function: 0 HotSpareStatus: Information Not Available InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 Manufacturer: INTEL MaximumCapableSpeed: 8 GT/s MediaType: Solid State Drive Model: Dell Express Flash NVMe P4510 1TB SFF NegotiatedSpeed: 8 GT/s PCIeCapableLinkWidth: x4 PCIeNegotiatedLinkWidth: x4 PrimaryStatus: Ok ProductID: a54 RaidStatus: Information Not Available RAIDType: Unknown RemainingRatedWriteEndurance: 100 % Revision: VDV1DP23 SerialNumber: PHLJxxWF1PN SizeInBytes: 1000204886016 Slot: 1 State: Ready SystemEraseCapability: CryptographicErasePD PCIe SSD in Slot 1 in Bay 1 - PCI Device BusNumber: 130 DataBusWidth: 4x or x4 Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) DeviceDescription: PCIe SSD in Slot 1 in Bay 1 DeviceNumber: 0 DeviceType: PCIDevice FQDD: Disk.Bay.1:Enclosure.Internal.0-1 FunctionNumber: 0 InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 LastSystemInventoryTime: 2020-04-17T03:21:39 LastUpdateTime: 2020-03-31T13:55:06 Manufacturer: Intel Corporation PCIDeviceID: 0A54 PCISubDeviceID: 2003 PCISubVendorID: 1028 PCIVendorID: 8086 SlotLength: 2.5 Inch Drive Form Factor SlotType: PCI Express Gen 3 SFF-8639 When I go in to menu Configuration / Controllers there is empty list. Is this expected in case of S130? I would really like to fulfil the client needs and run FreeBSD on it. But These R6515 are too new too me. The last PowerEdge I have in hand was R610 / T20. Both working fine with FreeBSD. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Chris wrote on 04/17/2020 05:51: On Thu, 16 Apr 2020 19:57:21 -0700 Mel Pilgrim list_free...@bluerosetech.com said On 2020-04-16 12:30, Miroslav Lachman wrote: > Pete Wright wrote on 04/16/2020 20:23: >> >> >> On 4/16/20 11:12 AM, Miroslav Lachman wrote: >>> Kurt Jaeger wrote on 04/16/2020 20:07: > >> I would try booting via UEFI if you can. I just installed a laptop >> yesterday which has a nvme root device, it was detected by the >> 12-STABLE snapshot I used to boot from. no other modifications were >> necessary on my end. > > I changed BIOS settings to use UEFI boot method, booted 12.1 installer > ISO but without luck. Still no NVME disks :( > > You can see it on printscreen from iDRAC https://ibb.co/tPnymL7 > > Anything more I can test? Looking at server specs, the R6515's NVME support is only through the PERC S150 RAID controller. If that's the case, I'm pretty sure you're out of luck. The PERC S-series controllers are software-based RAID that require Dell's Windows or Linux drivers. You'd need a PERC H-series card to get support in FreeBSD. That's something I didn't expect at all. So there is nothing which can be fixed on FreeBSD side? :( Someone please correct me if I'm wrong? As I mentioned. I was suspicious of this. He should be able to flash the card, making it a pass. I do a lot of them. If someone doesn't beat me to it. I'll dig through what I have, and see if I can't find the right image(s), and program(s). This is rented dedicated machine. I cannot flash anything on it. I can ask the provider if they can install some card. Do you have some recommendation? What is supported by Dell and FreeBSD for ZFS? I really appreciate your help! Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Pete Wright wrote on 04/16/2020 23:06: iDRAC does not allow me to do anything with the drives. But I booted Linux SystemRescueCd and nvme devices are there visible in /dev/ printscreen https://ibb.co/sj22Nwg So I think the HW is OK, but FreeBSD does not recognize the controller? might be interesting to see what the dmesg buffer and lspci output for this device is under linux. that should give pointers to how the device is being presented to the kernel. There is verbose output of lspci https://ibb.co/dPZTwV1 dmesg contains: nvme nvme0: pci function :81:00.0 nvme nvme1: pci function :82:00.0 nvme nvme0: 32/0/0 default/read/poll queues nvme nvme1: 32/0/0 default/read/poll queues Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Chuck Tuffli wrote on 04/16/2020 22:29: On Thu, Apr 16, 2020 at 12:30 PM Miroslav Lachman <000.f...@quip.cz> wrote: Pete Wright wrote on 04/16/2020 20:23: On 4/16/20 11:12 AM, Miroslav Lachman wrote: Kurt Jaeger wrote on 04/16/2020 20:07: I would try booting via UEFI if you can. I just installed a laptop yesterday which has a nvme root device, it was detected by the 12-STABLE snapshot I used to boot from. no other modifications were necessary on my end. I changed BIOS settings to use UEFI boot method, booted 12.1 installer ISO but without luck. Still no NVME disks :( You can see it on printscreen from iDRAC https://ibb.co/tPnymL7 Anything more I can test? Fair warning, I don't deal much with Dell, but it's curious that iDrac lists the device protocol as MI Device Protocol: NVMe-MI1.0 MI or the Management Interface is defined by NVMe, but it isn't the same as a block interface. MI typically uses SMBUS and not PCIe to communicate with the device. So it's possible that the device is visible to iDrac via SMBUS but may not be on the PCIe bus for $reasons. Does iDrac have any tools to interact with the device via MI? iDRAC does not allow me to do anything with the drives. But I booted Linux SystemRescueCd and nvme devices are there visible in /dev/ printscreen https://ibb.co/sj22Nwg So I think the HW is OK, but FreeBSD does not recognize the controller? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Navdeep Parhar wrote on 04/16/2020 21:51: On 4/16/20 12:30 PM, Miroslav Lachman wrote: Pete Wright wrote on 04/16/2020 20:23: On 4/16/20 11:12 AM, Miroslav Lachman wrote: Kurt Jaeger wrote on 04/16/2020 20:07: I would try booting via UEFI if you can. I just installed a laptop yesterday which has a nvme root device, it was detected by the 12-STABLE snapshot I used to boot from. no other modifications were necessary on my end. I changed BIOS settings to use UEFI boot method, booted 12.1 installer ISO but without luck. Still no NVME disks :( You can see it on printscreen from iDRAC https://ibb.co/tPnymL7 Anything more I can test? Does the nvme controller show up in pciconf -l? # pciconf -l | grep nvme Empty result. pciconf -l show many things, tome of them are named "noneN@pci..." The machine is Dell PowerEdge R6515 with AMD EPYC 7302P Is it possible that the controller is not recognized? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Pete Wright wrote on 04/16/2020 20:23: On 4/16/20 11:12 AM, Miroslav Lachman wrote: Kurt Jaeger wrote on 04/16/2020 20:07: I would try booting via UEFI if you can. I just installed a laptop yesterday which has a nvme root device, it was detected by the 12-STABLE snapshot I used to boot from. no other modifications were necessary on my end. I changed BIOS settings to use UEFI boot method, booted 12.1 installer ISO but without luck. Still no NVME disks :( You can see it on printscreen from iDRAC https://ibb.co/tPnymL7 Anything more I can test? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: support of PCIe NVME drives
Kurt Jaeger wrote on 04/16/2020 20:07: Hi! I was requested to install FreeBSD 11.3 on a new Dell machine with only 2 NVME drives in ZFS mirror. The problem is that installer does not see the drives. Are there any special procedure to use NVME drives for installation a later for booting? I use 2 NVMe drives as zfs mirror to boot from on my testbox, but it runs CURRENT, since approx. November 2018. So maybe try it with 12.1 ? I know, that does not help if you are asked to install 11.3, but at least it gives you an idea... I tried 12.1 few minutes ago but the result is the same - no NVME drives listed. Should I try something with kernel modules, some sysctl tweaks? Should I try UEFI boot? (I never did) Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
support of PCIe NVME drives
I was requested to install FreeBSD 11.3 on a new Dell machine with only 2 NVME drives in ZFS mirror. The problem is that installer does not see the drives. Are there any special procedure to use NVME drives for installation a later for booting? Drives are described in iDRAC: Device Description: PCIe SSD in Slot 1 in Bay 1 Device Protocol: NVMe-MI1.0 Model:Dell Express Flash NVMe P4510 1TB SFF Bus: 130 Manufacturer: INTEL Product ID: a54 Revision: VDV1DP23 Enclosure:PCIe SSD Backplane 1 There is no special HW RAID card. I switched to a shell in an installer and NVME drives are not listen in dmesg.boot. I tried to manually load nvme and nvd modules but the error messages says they are already in the installer kernel. How can I make it work? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 11.3 on Dell PowerEdge R6515 Server with NVME
Hello, I would like to know if somebody have some experience with FreeBSD on Dell PowerEdge R6515? We are planing to order new hosted machine from our service provider. They are offering following configuration: PowerEdge R6515 Server AMD EPYC 7302P 3GHz, 16C/32T, 128M Cache (155W) DDR4-3200 2.5" Chassis with up to 10 NVME Drives Riser Config 1, 1x16 LP PCIe slot PowerEdge R6515 x4 or x10 Shipping Material No Quick Sync Performance Optimized 3200MT/s RDIMMs 16GB RDIMM, 3200MT/s, Dual Rank iDRAC9,Enterprise x5 Dell 1TB, NVMe, Read Intensive Express Flash, 2.5 SFF Drive, U.2, P4510 with Carrier No Hard Drive No Controller Heatsink for CPU less than 180W C13 to C14, PDU Style, 10 AMP, 6.5 Feet (2m), Power Cord Dual, Hot Plug, Redundant Power Supply (1+1), 550W No Trusted Platform Module Asset Tag - ProSupport (Website, barcode, Onboard MacAddress) Order Configuration Shipbox Label (Ship Date, Model, Processor Speed, HDD Size, RAM) Broadcom 57416 Dual Port 10 GbE BaseT Network LOM Mezz Card ReadyRails Static Rails for 2/4-post Racks C30, No RAID for NVME chassis Producer Recycling Fund Contribution PowerEdge R6515/R7515 Motherboard, with 2 x 1Gb Onboard LOM (BCM5720) Performance BIOS Settings I don't have experience with R6515, only some old R610 / R620 which work fine. Are there any compatibility problems? My main concern is NVME. This will be my first experience with NVME. Are there any gotchas witn NVME on FreeBSD? Or kldloading nvme and nvd is enough and then I can work with it like with any other disk, format to UFS? We need the best performance for database (MariaDB / MySQL) workload so I tend to use UFS instead of ZFS. I will appreciate any experiences, tips and ideas about this machine. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Light GeoIP support dropped?
Alexander Koeppe wrote on 2020/01/07 19:47: Am 06.01.20 um 22:46 schrieb Christoph Moench-Tegeder: ## Alexander Koeppe (forma...@online.de): since I've upgraded to FreeBSD 12, I don't find a package providing the lightweight geoip database API incl. GeoIP.h and libGeoIP.so. The so-called "legacy" database format used by libGeoIP has been discontinued by MaxMind, and is only available for paying customers: https://blog.maxmind.com/2018/01/02/discontinuation-of-the-geolite-legacy-databases/ For that reason, net/GeoIP has been removed quite some time ago: https://svnweb.freebsd.org/ports?view=revision&revision=493168 And the free (as in no payment required) GeoLite2 databases have seen some licensing/handling changes, too: https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ Regards, Christoph Thanks for the hints. All the information is very clearing. This deprecation has completely slipped through for me. I'll dig into the new GeoLite2 approach and see what's the impact for my software project. Thanks to all and all others who have responded. Free registration and license key works without any problem. But if your software accessed DB or CSV files directly then it will not work anymore because format of database was changed from one flat table to few tables with relations. If your SW uses some library do access the DB then it may work with updated dependency. My usecase was very simple shellscript so I was able to convert it to new CSV files. They can be converted to the old format if somebody need it. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS ghost files on 11.3-STABLE
Gareth de Vaux wrote on 2019/11/25 18:00: Hi all, I deleted a file (rm filter) by mistake instead of its backup 'filter~', however it seems a remnant of a much older version of the file (given by its date and content) is half hanging around? $ ls -l filter ls: filter: No such file or directory $ ls -l filter* -rw-r--r-- 1 lordcow lordcow 18179 Mar 28 2019 filter -rw--- 1 lordcow lordcow 19092 Nov 20 23:36 filter~ $ stat filter stat: filter: stat: No such file or directory $ stat filter* 1525321853 1911959 -rw-r--r-- 1 lordcow lordcow 4294967295 18179 "Mar 28 17:07:34 2019" "Mar 28 17:08:07 2019" "Mar 28 17:08:07 2019" "Mar 28 17:07:34 2019" 18432 24 0x800 filter 1525321853 833819 -rw--- 1 lordcow lordcow 4294967295 19092 "Aug 10 22:31:53 2016" "Nov 20 23:36:40 2019" "Nov 24 23:08:13 2019" "Nov 20 23:36:40 2019" 19456 24 0x800 filter~ $ cat filter cat: filter: No such file or directory $ cat filter* (cats both files) A zpool scrub returns no errors I haven't tried to overwrite the file yet incase anyone wants some output. FreeBSD 11.3-STABLE #0 r353939 ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Do you have snapshot of this dataset before you run the "rm filter"? What files are listed there? It is possible you have some non printable (invisible) character in the filename. It can be trailing space, newline or something else so in fact it has different filename than the one of deleted file but it looks the same. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jexec as user?
Christos Chatzaras wrote on 2019/11/19 14:09: On 19 Nov 2019, at 15:02, mike tancsa wrote: On 11/19/2019 6:42 AM, Ronald Klop wrote: Hi, Is it possible to jexec into a jail as a regular user. Or to enable that somewhere? Or is the way to do such a thing to set up ssh in the jail? On 11.3 at least, does not the built in functionality of jexec do what you need ? jexec [-l] [-u username | -U username] jail [command ...] # jexec -U testuser 3 csh testuser@cacticonsole:/ % id uid=1005(testuser) gid=1005(testuser) groups=1005(testuser) testuser@cacticonsole:/ % I think he wants to use jexec as a normal user from the main OS. If he wants to run jexec as root and login to jail as user then your command works. If you want to use jexec as normal user in host, look at sysutils/jailme from ports: https://www.freshports.org/sysutils/jailme/ This version is installed setuid and does some sanity checking to ensure the username and UID match between the jail and the host system. WWW: https://github.com/Intermedix/jailme Miroslav Lachman PS: I never used jailme personally ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?
Chris Ross wrote on 11/05/2019 21:19: On Tue, Nov 05, 2019 at 08:20:15PM +0100, Miroslav Lachman wrote: Chris Ross wrote on 11/05/2019 19:34: Hello. I have a Cisco UCS C220-M5 with a RAID controller. It calls itself "Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5. Looking at the CIMC, it shows the PCI vendor/device ids 1000:0014, which looks to be an LSI MegaRAID Tri-Mode SAS3516. It looks like this should be supported by the mpr(4) driver, but it doesn't seem to recognize it at boot time. Do you have mpr_load="YES" in loader.conf? Or for ISO booting you can manually load kernel modules at boot prompt. I dropped to boot prompt in ISO boot, and entered 'mpr_load="YES"'. I tried "load", but wasn't able to devine how to load the mpr module with that. Is that needed, or should 'mpr_load="YES"' have accomplished the desired result? mpr_load="YES" goes to /etc/loader.conf If you need to load mpr manually in boot prompt I am not sure if it should be: load mpr or load mpr.ko of full path load /boot/kernel/mpr.ko Kind Regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?
Chris Ross wrote on 11/05/2019 19:34: Hello. I have a Cisco UCS C220-M5 with a RAID controller. It calls itself "Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5. Looking at the CIMC, it shows the PCI vendor/device ids 1000:0014, which looks to be an LSI MegaRAID Tri-Mode SAS3516. It looks like this should be supported by the mpr(4) driver, but it doesn't seem to recognize it at boot time. Is there some magic I need to perform for the 12.1-RELEASE image ISO boot to get this driver loaded, or will some internal changes be needed to support this particular part due to quirks? Let me know any information I can provide that will help diagnose. Thank you. Do you have mpr_load="YES" in loader.conf? Or for ISO booting you can manually load kernel modules at boot prompt. https://www.freebsd.org/cgi/man.cgi?query=loader%288%29 On a boot prompt: load [-t type] file ... boot Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: python dameon coredumps when started from boot, but not by hand
Pete French wrote on 11/04/2019 13:30: Shot in the dark: Is it possible that python is trying to dynamically load a shared library that isn't available yet due to being on a not-yet mounted filesystem? I wondered about that, but I have these boxes confiured with only one filesystem for everything apart from mysql data. Just a random guess. A good one, and one which makes me wonder if theres some shared library config which isnt happening and maybe that is it ? Am going to do an experiment to see if the same behaviout occurs on a real hardware machine not in Azure - which might make it easier to debug as I can at least see the console that way. Check "rcorder /etc/rc.d/* /usr/local/etc/rc.d/*" Check if ldconfig is runable (I ended up with permissions 0444 on /etc/rc.d/ldconfig after some etcupdate run) Next things - try to run it as: 1) service myservice start or 2) /usr/local/etc/rc.d/myservice start There can be differencies. You can also try to start it from cron instead of hands (different environment) or try to start in on boot from crontab with tag @reboot. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS... / scrub speed up
Miroslav Lachman wrote on 2019/05/09 13:36: Dimitry Andric wrote on 2019/05/09 13:02: On 9 May 2019, at 10:32, Miroslav Lachman <000.f...@quip.cz> wrote: [...] Disks are OK, monitored by smartmontools. There is nothing odd, just the long long scrubs. This machine was started with 4x 1TB (now 4x 4TB) and scrub was slow with 1TB disks too. This machine - HP ML110 G8) was my first machine with ZFS. If I remember it well it was FreeBSD 7.0, now running 11.2. Scrub was / is always about one week. (I tried some sysctl tuning without much gain) Unfortunately https://svnweb.freebsd.org/changeset/base/339034, which greatly speeds up scrubs and resilvers, was not in 11.2 (since it was cut at r334458). If you could update to a more recent snapshot, or try the upcoming 11.3 prereleases, you will hopefully see much shorter scrub times. Thank you. I will try 11-STABLE / 11.3-PRERELEASE soon and let you know about the difference. Little bit late because I run scrub once per 60 days. Now on FreeBSD 11.3-RELEASE-p3 scrub takes 2 days and 10 hours instead of 1 week. This is a great improvement! Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: chsh corrupts /etc/pwd.db
Miroslav Lachman wrote on 2019/08/22 11:21: Alan Somers wrote on 2019/08/22 04:07: Unless, of course your master.passwd file was damaged. But the *.db files are really just caches for faster access to user data. The real master file is master.passwd. The ch* tools typically just change master.passwd, and then call pwd_mkdb to rebuild the *.db files. The pwd.db file from before the snapshot only has three entries. From after, it has four, and one of them has the wrong shell. So it does seem that chsh is corrupting the file. And fortunately the problem is repeatable. Any ideas about how to debug it? -Alan P.S. I failed to mention earlier that this is happening on 12.0-RELEASE-p10 I run in to something similar from time to time from about 10.x or 8.x (i skipped 9.x) I do not remember exactly what command did the corruption, if it was vipw or chsh or something else to manipulate user database. The fix was easy - run it again or use pwd_mkdb I searched our archive of issues and found it. It was error with "pw" command which sometimes failed in very weird way: # pw useradd -n user1 -u 1003 -G wheel -s /bin/tcsh -m -M 0700 -c "User One" pw: user 'user1' disappeared during update It was on FreeBSD 8.x. So it is different error than yours. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: chsh corrupts /etc/pwd.db
Alan Somers wrote on 2019/08/22 04:07: On Wed, Aug 21, 2019 at 7:22 PM Tom Samplonius wrote: On Aug 21, 2019, at 2:55 PM, Alan Somers wrote: Today I tried to use chsh to change my shell from bash to fish. The command completed successfully, but new logins continued to use bash! Investigating, I discovered that /etc/pwd.db and /etc/spwd.db seem to contain 3-4 entries per user. One of those still refers to my old Berkeley DB files can only have a single index, so users are stored three times, once by username, once by uid, and once by line number. So that isn’t corruption. But why was my entry stored four times? shell. Worse, if I try using chsh again, it fails with an "entry inconsistent" error, and I have to restore the password files from backup. Has anybody seen something like this before? This is just a single system, with no NIS or LDAP. You shouldn’t need to restore the files. You should be able to just regenerate the *.db files from the master.passwd file: /usr/sbin/pwd_mkdb -p /etc/master.passwd Ok, that worked. Thanks! Unless, of course your master.passwd file was damaged. But the *.db files are really just caches for faster access to user data. The real master file is master.passwd. The ch* tools typically just change master.passwd, and then call pwd_mkdb to rebuild the *.db files. The pwd.db file from before the snapshot only has three entries. From after, it has four, and one of them has the wrong shell. So it does seem that chsh is corrupting the file. And fortunately the problem is repeatable. Any ideas about how to debug it? -Alan P.S. I failed to mention earlier that this is happening on 12.0-RELEASE-p10 I run in to something similar from time to time from about 10.x or 8.x (i skipped 9.x) I do not remember exactly what command did the corruption, if it was vipw or chsh or something else to manipulate user database. The fix was easy - run it again or use pwd_mkdb Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: extremely slow boot of RELENG_10
mike tancsa wrote on 2019/07/31 17:30: While moving a pair of ZFS disks from an *very* old motherboard to a new one, I ran into an odd problem I had not seen before. The box was running just fine RELENG_10 from FreeBSD 10.1-STABLE #18 r279918 on 10yr old MB. Boots normally and expected speeds for old hardware/CPU. But on the new one, as soon as the |\-/|\ starts spinning, it looks like its 1/100th of the speed it should be. Unfortunately, we didnt have the luxury to wait for it to boot up all the way. We put the disks back in the old motherboard, did the RELENG_11 upgrade which included putting in the new boot blocks after zpool upgrade and then the disks booted just fine in the new box. We at first thought it was a hardware issue, but same behaviour on another new MB, new SATA cables etc etc. Any idea what was going on behind the scenes that might have caused it ? Is there something about the way the old boot blocks would interact poorly with new motherboards (in this case, a SuperMicro X11SSH-F) ? I have SuperMicro X11SSH-F and X11SSW-F too and I found this slow boot very annoying. We were running 10.x on them for about 2 years and as I found it was able to boot 10.x system with 11.x loader I deployed 11.x loader on all of them to workaround this issue. (must be redeployed after each 10.x update) My original notes include these links: http://smyck.net/2016/06/15/freebsd-slow-zfs-bootloader/ https://lists.freebsd.org/pipermail/freebsd-stable/2016-June/084863.html Jan Bramkamp said: "The bootloader disk caching. The old code doesn't work (well) on modern UEFI implementations. You can get acceptable bootloader performance with the FreeBSD 10.3 EFI bootloader on such boards. Even the UEFI install images contain fallback BIOS bootcode and some boards prefer the old BIOS bootcode. On such boards you have to suffer through the slow boot process once to install FreeBSD." Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
wrong permissions on files edited by etcupdate after upgrade to 11.3-RELEASE
I upgraded our first machine from 11.2-p10 to 11.3-RELEASE from the sources with GENERIC kernel. I did not run "make delete-old" but some installed apps, like tmux, cannot run anymore: # tmux Shared object "libevent-2.1.so.6" not found, required by "tmux" Then I found some services are not running. For example jails and PF. I tried to run PF manually: # service pf reload pf does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable # ls -l /etc/rc.d/pf -rw-r--r-- 1 root wheel 1.2K Jul 10 16:56 /etc/rc.d/pf OK, now I know what this problem is: # ls -l /etc/rc.d/ | grep 'rw-r--r' -rw-r--r-- 1 root wheel 3032 Jul 10 20:30 ipfw -rw-r--r-- 1 root wheel788 Jul 10 20:32 ipmon -rw-r--r-- 1 root wheel 14256 Jul 10 16:58 jail -rw-r--r-- 1 root wheel 2956 Jul 10 16:56 ldconfig -rw-r--r-- 1 root wheel 4500 Jul 10 20:34 ntpd -rw-r--r-- 1 root wheel 1263 Jul 10 16:56 pf All these files where edited by etcupdate because there were some conflicts. I was using mergemaster in the past and never had a problem like this so my question is: why files with conflicts edited by etcupdate have wrong permissions? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Michelle Sullivan wrote on 2019/06/07 01:49: Yes but you seem to have done this with ZFS too, just not in this particularly bad case. There is no r-studio for zfs or I would have turned to it as soon as this issue hit. So as an update, this Company: http://www.klennet.com/ produce a ZFS recovery tool: https://www.klennet.com/zfs-recovery/default.aspx and following several code changes due to my case being an 'edge case' the entire volume (including the zvol - which I previously recovered as it wasn't suffering from the metadata corruption) and all 34 million files is being recovered intact with the entire directory structure. Its only drawback is it's a windows only tool, so I built 'windows on a stick' and it's running from that. The only thing I had to do was physically pull the 'spare' out as the spare already had data on it from being previously swapped in and it confused the hell out of the algorithm that detects the drive order. It's really good to know there exists some tool which can recover files from broken ZFS. Thank you for sharing your very long story and I am glad you recovered all your data. It would be very nice to have similar tool running on FreeBSD... maybe it is good topic for next google summer of code project. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD flood of 8 breakage announcements in 3 mins.
Alan Somers wrote on 2019/05/16 05:16: On Wed, May 15, 2019 at 9:14 PM Miroslav Lachman <000.f...@quip.cz> wrote: It would also be good if base system vulnerabilities are first published in FreeBSD vuxml. Then it can be reported to sysadmins by package security/base-audit. +1. Reporting base + ports vulnerabilities in a common way would be great. I assume that this is already part of the pkgbase project being worked on by brd and others. The functionality is already there. The only part missing is Security Office should fill the data in to vuxml at the time of publishing new SA. Thanks to Mark Felder https://blog.feld.me/posts/2016/08/monitoring-freebsd-base-system-vulnerabilities-with-pkg-audit/ Then I provided periodic script https://www.freshports.org/security/base-audit/ Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD flood of 8 breakage announcements in 3 mins.
Mel Pilgrim wrote on 2019/05/16 02:30: [...] By batching updates, FreeBSD is making administrative decisions for other people's systems. Some folks don't need to worry about scheduling downtime and will benefit from faster update availability. Folks who need to worry about scheduling downtime are already going to batch updates and should be allowed to make those decisions for themselves. Batched SAs help in neither case. Example: the ntpd CVE is more than two months old, and was rapidly fixed in ports. I was able to switch my systems to the ports ntpd during a scheduled downtime window in March instead of doing it this weekend. So not only did I benefit from the faster update availability, I was able to make my own decision about my own systems and significantly reduce my exposure. Don't be Microsoft. Don't sit on security updates. +1 Delaying / hiding security updates cannot be good. The vulnerability already exists. Delayed updates do favor to "bad persons", not sysadmins. Even information about found vulnerability is more valuable for sysadmins than silence. Some vulnerabilities can be mitigated by configuration changes or some service replacement (eg. ntpd). But if I don't know that there is some vulnerability I cannot do anything. It would also be good if base system vulnerabilities are first published in FreeBSD vuxml. Then it can be reported to sysadmins by package security/base-audit. None of these recent Sec. Advisories are listed in Vuxml yet! It's bad example of not dog fooding there. I am not saying that FreeBSD SO do bad work. I really appreciate it. But there is still something to improve. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Alan Somers wrote on 2019/05/09 14:50: [...] On 11.3 and even much older releases, you can greatly speed up scrub and resilver by tweaking some sysctls. If you have spinning rust, raise vfs.zfs.top_maxinflight so they'll do fewer seeks. I used to set it to 8192 on machines with 32GB of RAM. Raising vfs.zfs.resilver_min_time_ms to 5000 helps a little, too. I have this in sysctl.conf vfs.zfs.scrub_delay=0 vfs.zfs.top_maxinflight=128 vfs.zfs.resilver_min_time_ms=5000 vfs.zfs.resilver_delay=0 I found it somewhere in the mailinglist discussing this issue in the past. Isn't yours 8192 too much? The machine in question has 4x SATA drives on very dump and slow controller and only 5GB of RAM. Even if I read this vfs.zfs.top_maxinflight: Maximum I/Os per top-level vdev I am still not sure what it really means and how I can "calculate" optimal value. As Michelle pointed there is drawback when sysctls are optimized for quick scrub, but this machines is only running nightly backup script fetching data from other 20 machines so this scrip sets sysctl back to sane defaults during backup sysctl vfs.zfs.scrub_delay=4 > /dev/null sysctl vfs.zfs.top_maxinflight=32 > /dev/null sysctl vfs.zfs.resilver_min_time_ms=3000 > /dev/null sysctl vfs.zfs.resilver_delay=2 > /dev/null At the and it reloads back optimized settings from sysctel.conf Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Dimitry Andric wrote on 2019/05/09 13:02: On 9 May 2019, at 10:32, Miroslav Lachman <000.f...@quip.cz> wrote: [...] Disks are OK, monitored by smartmontools. There is nothing odd, just the long long scrubs. This machine was started with 4x 1TB (now 4x 4TB) and scrub was slow with 1TB disks too. This machine - HP ML110 G8) was my first machine with ZFS. If I remember it well it was FreeBSD 7.0, now running 11.2. Scrub was / is always about one week. (I tried some sysctl tuning without much gain) Unfortunately https://svnweb.freebsd.org/changeset/base/339034, which greatly speeds up scrubs and resilvers, was not in 11.2 (since it was cut at r334458). If you could update to a more recent snapshot, or try the upcoming 11.3 prereleases, you will hopefully see much shorter scrub times. Thank you. I will try 11-STABLE / 11.3-PRERELEASE soon and let you know about the difference. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Patrick M. Hausen wrote on 2019/05/09 09:46: Hi all, Am 09.05.2019 um 00:55 schrieb Michelle Sullivan : No, one disk in the 16 disk zRAID2 ... previously unseen but it could be the errors have occurred in the last 6 weeks... everytime I reboot it started resilvering, gets to 761M resilvered and then stops. 16 disks in *one* RAIDZ2 vdev? That might be the cause of your insanely long scrubs. In general it is not recommended though I cannot find the source for that information quickly just now. Extremely slow scrub is an issue even on 4 disks RAIDZ. I already posted about it in the past. This scrub is running from Sunday 3AM. Time to go is big lie. Is was "19hXXm" 12 hour ago. pool: tank0 state: ONLINE scan: scrub in progress since Sun May 5 03:01:48 2019 10.8T scanned out of 12.7T at 30.4M/s, 18h39m to go 0 repaired, 84.72% done config: NAMESTATE READ WRITE CKSUM tank0 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 gpt/disk0tank0 ONLINE 0 0 0 gpt/disk1tank0 ONLINE 0 0 0 gpt/disk2tank0 ONLINE 0 0 0 gpt/disk3tank0 ONLINE 0 0 0 Disks are OK, monitored by smartmontools. There is nothing odd, just the long long scrubs. This machine was started with 4x 1TB (now 4x 4TB) and scrub was slow with 1TB disks too. This machine - HP ML110 G8) was my first machine with ZFS. If I remember it well it was FreeBSD 7.0, now running 11.2. Scrub was / is always about one week. (I tried some sysctl tuning without much gain) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Pete French wrote on 2019/05/03 14:28:
On 03/05/2019 13:11, Miroslav Lachman wrote:
I had this problem in the past too. I am not sure if it was on Dell or
HP machine - controller presents first disk only in the boot time so I
created small (10 - 15GB partition) on each disk and use them all in 4
way mirror. Cannot say if it was gmirror with UFS or ZFS mirroring.
The rest of the each disk was used for ZFS RAIDZ.
Snap :-) Thats exactly what I have done - but the bits you cant mirror
are the GPT partititons for bootcode. I was fiddling with hose of da0
without realising it was now using da1 to boot. If it ever chooses da2
or da3 then I will need to mirror it there too, so I have it partitioned
like that, but am currently using those as swap as it shows no signs of
wanting to boot from them for now.
Time for some scripting :) This is what I have on the machine with weird
controller
# cat bin/zfs_bootcode_update.sh
#!/bin/sh
devs="ada0 ada1 ada2 ada3"
for dev in $devs
do
echo -n "Updating ZFS bootcode on ${dev} ..."
if ! /sbin/gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i
1 ${dev} > /dev/null; then
echo " error"
exit 1
fi
echo " done"
done
So it should be able to boot from any installed drive, no matter the order.
Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Pete French wrote on 2019/05/03 11:55: Oddly enough I got bitten by something like this yesteray. I have a machine containing an HP P400 RAID controller, which is nice enough, but I run ZFS so I have made the drives all into RAID-0 as being as close as I can get to accessing the raw SAS drives. BSD seems them as da0, da1, da2, da3 - but the RAID controller oly presents one of them to the BIOS, so my booting has to be all from that drive. This has been da0 for as long as I can remember, but yesteday it decided to start using what BSD sees as da1. Of course this is very hard to recognise as da0 and da1 are pretty much mirrors of each other. Spent a long time trying to work out why the fixes I was applying to da0 were not being used at boot time. I had this problem in the past too. I am not sure if it was on Dell or HP machine - controller presents first disk only in the boot time so I created small (10 - 15GB partition) on each disk and use them all in 4 way mirror. Cannot say if it was gmirror with UFS or ZFS mirroring. The rest of the each disk was used for ZFS RAIDZ. ( Having to use Windows XP to talk to the iLo due to browsers dropping support for the old ciphers doesnt help either, what do other people with oldish HP hardware do about this ? I know its off topic, but theres a lot of it out there... ) I have WinXP guest in VirtualBox exactly for this situation. With old browser, with old Java, with Flash - believe it or not, Cisco UCS C200 has remote management created in Flash! Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CFT: FreeBSD Package Base
Cy Schubert wrote on 2019/05/01 05:56: In message <292eadc6-3662-ec43-1175-53fc25248...@quip.cz>, Miroslav Lachman wri tes: David Chisnall wrote on 2019/04/30 10:22: On 29/04/2019 21:12, Joe Maloney wrote: With CFT version you chose to build, and package individual components such as sendmail with a port option. That does entirely solve the problem of being able to reinstall sendmail after the fact without a rebuild of the userland (base) port but perhaps base flavors could solve that problem assuming flavors could extend beyond python. This sounds very much like local optimisation. It's now easy to create a custom base image. Great. But how do I express dependencies in ports on a specific base configuration? This is easy if I depend on a specific base package, but how does this work in your model? For example, if I have a package that depends on a library that is an optional part of the base system, how do I express that pkg needs to either refuse to install it, or install a userland pkg that includes that library in place of my existing version as part of the install process? More importantly for the container use case, if I want to take a completely empty jail and do pkg ins nginx (for example), what does the maintainer of the nginx port need to do to express the minimum set of the base system that needs to be installed to allow nginx to work? One of the goals for the pkg base concept was to allow this kind of use case, easily creating a minimal environment required to run a single service. With a monolithic base package set, you're going to need some mechanism other than packages to express the specific base subset package that you need and I think that you need to justify why this mechanism is better than using small individual packages. Will it not be maintainer's nightmare to take care of all the dependencies on the base packages for each port we have in the ports tree? No more than it is today. Remember, people have been doing this sort of thing for decades. If the folks at Red Hat, Oracle (formerly Sun), and IBM can do it, I'm sure we can too. The dependency lists will be longer. We may require dependency lists that allow the choice of one of many prereqs or coreqs. They are experts and they are paid for their work. I am not. I am maintaining a few packages and the reality is I don't know what they need in base. Till these days I don't care about this kind of dependency. I am not system developer or programmer and I think there are more than just me who see this as a kind of problem. So in this case, pkg base gives me nothing but more work on those packages. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CFT: FreeBSD Package Base
David Chisnall wrote on 2019/04/30 10:22: On 29/04/2019 21:12, Joe Maloney wrote: With CFT version you chose to build, and package individual components such as sendmail with a port option. That does entirely solve the problem of being able to reinstall sendmail after the fact without a rebuild of the userland (base) port but perhaps base flavors could solve that problem assuming flavors could extend beyond python. This sounds very much like local optimisation. It's now easy to create a custom base image. Great. But how do I express dependencies in ports on a specific base configuration? This is easy if I depend on a specific base package, but how does this work in your model? For example, if I have a package that depends on a library that is an optional part of the base system, how do I express that pkg needs to either refuse to install it, or install a userland pkg that includes that library in place of my existing version as part of the install process? More importantly for the container use case, if I want to take a completely empty jail and do pkg ins nginx (for example), what does the maintainer of the nginx port need to do to express the minimum set of the base system that needs to be installed to allow nginx to work? One of the goals for the pkg base concept was to allow this kind of use case, easily creating a minimal environment required to run a single service. With a monolithic base package set, you're going to need some mechanism other than packages to express the specific base subset package that you need and I think that you need to justify why this mechanism is better than using small individual packages. Will it not be maintainer's nightmare to take care of all the dependencies on the base packages for each port we have in the ports tree? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Mailx Question
Software Info wrote on 2019/04/09 23:09: Hi All Since mailx is built into FreeBSD I decided to try asking this question here. I have a text file with about 30 email addresses. The file will change every day. I want an easy commandline way to read the file and blind copy send an email to the addresses in the file. So far, I have this working with just a plain send using the command below. mailx -s "Test Emails" -b `cat mylist.txt` < body.txt -r "No-Reply" Of course, when I use a plain send, everybody sees everybody’s email address so I would love to be able to do a blind copy send. Would anyone be able to assist me with this? It may depend on your MTA (Sendmail, Postfix, Exim etc.) "You must specify direct recipients with -s, -c, or -b." -b bcc-addr Send blind carbon copies to bcc-addr list of users. The bcc-addr argument should be a comma-separated list of names. You should replace newlines with comma: cat mylist.txt | tr "\n" "," Maybe something like this will work for you: mail -s "Test E-mails" -b `cat mylist.txt | tr "\n" ","` my-gene...@example.com < body.txt Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bhyve zfs resizing
tech-lists wrote on 2019/03/19 01:23: Am I correct? In that I should have used UFS in the guest rather than zfs? Or was it the encryption? As Alan already wrote - you can use ZFS inside of the guest but I would never choose ZFS in zvol backed guest. I prefere UFS. It is faster and does not need so much memory as ZFS does. My VirtualBox and Bhyve guests are small. Sometimes <1GB of RAM. Sometimes 2GB of RAM and that is very small for ZFS. May be you can try to limit ZFS ARC size in /etc/sysctl.conf or in /boot/loader.conf vfs.zfs.arc_max Choose about 1/4 of your guest's RAM size and test it again. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bhyve zfs resizing
tech-lists wrote on 2019/03/18 16:25: On Mon, Mar 18, 2019 at 09:08:31AM -0600, Alan Somers wrote: Do you mean using a zvol as the backing store for a VM? If so, then: 1) Yes. You can just do "zfs set volsize" on the host. 2) In theory no, but the guest may need to be rebooted to notice the change. And I'm not sure if the current bhyve code will expose the new size without a reboot or not. 3) Sure. But after you expand the zvol (or before you shrink it), you'll have to change the size of the guest's filesystem using the guest's native tools. I did it 2 month ago on FreeBSD 11.2. On the host with running guest: # zfs set volsize=200G tank1/vol1/bhyve/kotel/disk1 Even if I unmounted disk in the guest it still does not see the new size until I rebooted the guest. After reboot of the guest, you will see corrupted GPT: # gpart show -p vtbd1 => 40 209715120vtbd1 GPT (200G) [CORRUPT] 40 8 - free - (4.0K) 48 1024 vtbd1p1 freebsd-boot (512K) 1072976 - free - (488K) 2048 203423744 vtbd1p2 freebsd-ufs (97G) 2034257926289368 - free - (3.0G) And after running recover, the guest will see the added space # gpart recover vtbd1 vtbd1 recovered # gpart show -p vtbd1 => 40 419430320vtbd1 GPT (200G) 40 8 - free - (4.0K) 48 1024 vtbd1p1 freebsd-boot (512K) 1072976 - free - (488K) 2048 203423744 vtbd1p2 freebsd-ufs (97G) 203425792 216004568 - free - (103G) After this, the partition can finally be enlarged # gpart resize -a 1M -s 197G -i 2 vtbd1 # growfs /vol0 Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: more fun, upgrading from 10.3-STABLE 10.4-RELENG to 11.2-RELENG - kernel panic
Lee Damon wrote on 2019/03/02 01:36: On 3/1/19 15:38 , Miroslav Lachman wrote: Did you tried to boot "safe mode"? (selectable in boot menu). I completely forgot about safe mode. Yep. It boots. I'm going to finish the freebsd-update process then reboot into safe mode again. I'm out of time to work on this today and am only in this lab on Fridays so I'll have to pick up working on this problem next Friday. Glad to know something finally works :) You can look in to /boot/menu-commands.4th there is definition what Safe Mode disable : safemode_enabled? ( -- flag ) s" kern.smp.disabled" getenv -1 <> dup if swap drop ( c-addr flag -- flag ) then ; : safemode_enable ( -- ) s" set kern.smp.disabled=1" evaluate s" set hw.ata.ata_dma=0" evaluate s" set hw.ata.atapi_dma=0" evaluate s" set hw.ata.wc=0" evaluate s" set hw.eisa_slots=0" evaluate s" set kern.eventtimer.periodic=1" evaluate s" set kern.geom.part.check_integrity=0" evaluate ; You can play with these items one by one to find what is the root cause in your case. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: more fun, upgrading from 10.3-STABLE 10.4-RELENG to 11.2-RELENG - kernel panic
Lee Damon wrote on 2019/03/02 00:06: Darn it. I get the same kernel panic with that one. I'm compiling locally but I don't expect that to make any difference. I'll need to go pawing through the release notes and see if there are any references to deprecated hardware that might be involved. I'm attaching a copy of dmesg output from a successful boot into 10.4-STABLE. The kernel panic appears to happen around 15% of the way into the output, around I am running 11.2 on SunFire X2100 M2 but according to your dmesg it uses different chips. X2100 M2 has nVidia nForce MCP55 chipset for ATA devices, nfe for 2 NICs and Broadcom bge for the other 2 NIC's. Did you tried to boot "safe mode"? (selectable in boot menu). Or you can try to disable / enable some settings in the BIOS. Something related to USB or onboard VGA etc. may help. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: more fun, upgrading from 10.3-STABLE 10.4-RELENG to 11.2-RELENG - kernel panic
Lee Damon via freebsd-stable wrote on 2019/03/01 22:53: After discussion with Bob Bishop (thanks for the help!) I've tried to do the following to upgrade one of the old boxes I mentioned previously. cd /usr/src tar ... . rm -rf .??* * svn checkout httpg://svn.freebsd.org/base/releng/10.3 /usr/src compile, installkernel, installworld... Now that the host is running RELENG the next step was to update from 10.4 to 11.2 via freebsd-update freebsd-update freebsd-install freebsd-update upgrade -r 11.2-RELEASE freebsd-update install so far, so good. Now it all falls apart shutdown -r now ... why isn't the host coming back? Oh look, kernel panic. Fatal trap 12: page fault while in kernel mode cpuid = 1; apci id = 01 fault virtual address = 0x84 fault code = supervisor read data, page not present I went back from freebsd-update to source upgrades few years ago and now use exclusively source builds (build it on powerful build machine and distribute it to clients thru NFS so clients can just run make installkernel and make installworld) because I was bitten by failed freebsd-update upgrade many times... Google searches find references to the same panic type in VMs running 11.1, including https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220923 The differences are, that's 11.1 not 11.2 (I would presume the fix made it into 11.2 but maybe not) and most notably, that's against VMs and the host I'm doing this on is bare iron (Sun x4500). Still, I gave the two entries in /boot/loader.conf a try, no joy. Exactly the same panic. Recording the boot with slow-mo shows the panic happening just after the USB devices are enumerated by the kernel. It never even tries to mount root. I am able to boot to kernel.old, which appears to be my old 10.4-STABLE kernel. So now I'm kind of stuck. The update has already modified the config files as part of the first pass so rolling back may be a problem and moving forward seems unwise. I have only one x4500 but I have three x4540s running 11.2-STABLE (also installed from source) just fine. Anyone have any brilliant suggestions? I'm thinking of trying to compile 11.2-RELENG in /usr/src so I can try installing that kernel but that'll take several hours at least (it's an old box). If you can boot with the old 10.4 kernel and go online, just fetch kernel.txz from the net: http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/11.2-RELEASE/kernel.txz and unpack it to /boot/kernel112 then you can try to reboot a manually select to boot this kernel instead of default /boot/kernel. If you cannot access the boot loader prompt you can try "nextboot" command. 1) unpack the kernel 2) set nextboot: nextboot -k kernel112 3) shutdown -r now and hope for a luck If your machine boots fine with 11.2 kernel, you can fetch sources and rebuild kernel and userland for 11.2 as usual. Or you can try to fetch and unpack base.txz http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/11.2-RELEASE/base.txz over your current files. It can make a mess but you can always clean it with "make delete-old & make delete-old-libs" Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: source upgrade FBSD10 -> 11 (then 12)
Lee Damon wrote on 2019/02/28 17:18: I have three old FBSD 10 boxes that I need to upgrade. Ordinarily I do this by building a new box with the latest OS then migrating services and data. Unfortunately I don't have that option this time, the upgrade has to happen in-place. My plan is to go from 10 to 11 then from 11 to 12. I was looking at the "Upgrading FreeBSD" part of https://www.freebsd.org/releases/11.1R/installation.html#upgrade but unfortunately it seems to be missing a critical URL or two: "The procedure for doing a source code based update is described in and ." I tracked down where I think it points and the instructions appear to be just for same-version updates. Can I safely move /usr/src out of the way then check out the stable/11 and compile/install it or are there other things I need to do? The upgrade procedure is the same for major upgrade (10.x to 11.x ) as for minor upgrade (10.3 to 10.4). It is recommended to upgrade to the latest 10.x then to 11.x but sometimes I did source upgrade with skipping the whole branch - from 8.4 to 10.1 or 10.2. It worked with one exception but this must be tested first. If you plan to upgrade from 10.x to 11.2 then everything you need is described in /usr/src/Makefile Just checkout the sources in to /usr/src as usual and then For individuals wanting to upgrade their sources (even if only a delta of a few days): 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. & 4. can be combined by using the "kernel" target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `mergemaster' (you may wish to use -i, along with -U or -F). 9. `make delete-old' 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) I always skip step 5. doing all without reboot but beware of dragons! On upgrade from latest 10 (10-STABLE or 10.4-RELEASE) you may see notices on "make installkernel" phase: kldxref: unknown metadata record 4 in file atacard.ko kldxref: unknown metadata record 4 in file atp.ko They can be safely ignored. More details about the upgrade process https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading via source build, 10.4->11.2
George Mitchell wrote on 2018/12/05 14:24: On 12/4/18 9:35 PM, Warner Losh wrote: On Tue, Dec 4, 2018, 7:25 PM George Mitchell kldxref /boot/kernel kldxref: unknown metadata record 4 in file atacard.ko kldxref: unknown metadata record 4 in file atp.ko kldxref: unknown metadata record 4 in file atp.ko [...etc...] Should I have started with "make buildworld," or would that have bombed out even worse? Do I reboot and "make buildworld"? Or do I "make buildworld" now, while still running 10.4? -- George Just ignore the warnings. They are harmless. Warner [...] Thanks, that's what I expected. But what I really need to know is whether to make buildworld under 10.4 or 11.2. Or do I do it twice? And presumably I can't run mergemaster until after buildworld. I did upgrade from 10.4 to 11.2 on all our machines, just one builworld, buildkernel on shared build server (NFS exported /usr/obj + /usr/src), then installkernel, mergemaster -p, installworld, mergemaster, shutdown -r now. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
sync command runs for hours after upgrade to 11.2
19368 18.3 0.042322048 - R09:10 75:03.78 sync mrtg 25043 18.0 0.042322048 - R09:35 61:45.86 sync The same script is used on each of our servers without any problem. This machine is running Apache and PHP without any problems. Web is still responding even if the system load is about 60: last pid: 59734; load averages: 61.76, 59.62, 57.24 up 2+12:33:30 12:42:31 387 processes: 64 running, 318 sleeping, 5 zombie CPU: 14.1% user, 0.0% nice, 85.7% system, 0.1% interrupt, 0.1% idle Mem: 1006M Active, 9907M Inact, 9056M Laundry, 2703M Wired, 1405M Buf, 1224M Free Swap: 16G Total, 63M Used, 16G Free The one thing that can be of some coincidence is rsync backup which is running in the time between 6 - 17h. Can anybody help where should I look to solve this problem? # uname -srmi FreeBSD 11.2-RELEASE-p4 amd64 GENERIC /dev/mirror/gm0root on / (ufs, local, noatime) /dev/mirror/gm0usr on /usr (ufs, local, noatime, soft-updates) /dev/mirror/gm0var on /var (ufs, local, noatime, nosuid, soft-updates) /dev/mirror/gm0tmp on /tmp (ufs, local, noatime, noexec, nosuid, soft-updates) /dev/mirror/gm0vol0 on /vol0 (ufs, local, noatime, noexec, nosuid, soft-updates) /dev/mirror/gm0vol1 on /vol1 (ufs, local, noatime, noexec, nosuid, soft-updates) No ZFS involved. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: changes in iostat output in 11.x vs 10.x
Will Andrews wrote on 2018/08/20 15:33: On Sun, Aug 19, 2018 at 9:30 AM, John-Mark Gurney wrote: Miroslav Lachman wrote this message on Sun, Aug 19, 2018 at 02:29 +0200: I upgraded one of our servers from 10.4 to 11.2 and scripts using output of "iostat -x" are not working anymore. A checked the output of iostat and it is different. Looks like this was changed in r277566[1] by will. I've cc'd him. There is no documentation change associated w/ this change. [1] https://svnweb.freebsd.org/base?view=revision&revision=277566 Ah, yes, that should have been accompanied by a man page update. My bad, I'll fix it. ms/t is indeed what used to be svc_t. Thank you for the clarification. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
changes in iostat output in 11.x vs 10.x
I upgraded one of our servers from 10.4 to 11.2 and scripts using output of "iostat -x" are not working anymore. A checked the output of iostat and it is different. # on 10.4 # iostat -w 5 -c 2 -x ada0 ada1 extended device statistics device r/s w/skr/skw/s qlen svc_t %b ada0 51.5 28.3 1381.4 539.70 9.7 33 ada1 51.4 28.2 1381.5 539.70 10.1 34 extended device statistics device r/s w/skr/skw/s qlen svc_t %b ada0 0.2 6.4 2.4 136.50 2.9 2 ada1 0.0 5.8 0.0 136.50 3.4 2 # on 11.2 # iostat -w 5 -c 2 -x ada0 ada1 extended device statistics device r/s w/s kr/s kw/s ms/r ms/w ms/o ms/t qlen %b ada0 6 24 35.9697.9 2 177 30 6 ada1 6 23 34.9697.9 2 177 30 6 extended device statistics device r/s w/s kr/s kw/s ms/r ms/w ms/o ms/t qlen %b ada0 0 21 0.0776.6 0 096 20 5 ada1 0 21 0.0776.6 0 0 100 20 5 But I cannot find the explanation of new columns. The manpage seems the same for 10.4 and 11.2 The extended iostat device display, with the -x flag specified, shows the following statistics: r/s read operations per second w/s write operations per second kr/skilobytes read per second kw/skilobytes write per second qlentransactions queue length svc_t average duration of transactions, in milliseconds %b % of time the device had one or more outstanding transac- tions But there is no svc_t column anymore and there are ms/r ms/w ms/o and ms/t columns not mentioned in man page. Is it a documentation bug? Is ms/t the same what was previously known as svc_t? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jail related inconsistencies in FreeBSD tools parameters
James Gritton wrote on 2018/06/26 20:42: On 2018-06-23 12:58, Eitan Adler wrote: [...] I was thinking of a more generic one that does id or name. Now that I think about it a bit more, C makes this kind of thing impossible to do usefully. That said, I'll still review and commit any patches to existing tools to make them behave consistently. Yes, jail_getid(3) works with either a numeric ID or a name. I've added a patch to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229266 for the four programs I've found that need help. I've tested the easy ones (cpuset and sockstat). Thank you very much. I really appreciate your neverending work on jails! I hope it will be committed soon. Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jail related inconsistencies in FreeBSD tools parameters
James Gritton wrote on 2018/06/23 17:30: On 2018-06-22 16:03, Miroslav Lachman wrote: Chris H wrote on 2018/06/22 23:46: On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.f...@quip.cz> said I don't know if it is better to discuss it in jail@ or stable@ list so a do cross-post. FreeBSD has many jail aware utilities but they are inconsistent in taking JID as parameter. For example "sockstat" takes -j JID "Show only sockets belonging to the specified jail ID" and it means numeric ID only. On the other hand "ps" takes -J JID "This may be either the jid or name of the jail. Use -J 0 to display only host processes." The same apply for "top", it understands jid as a number or name of the jail too. Then again "cpuset" takes only numerical ID of the jail... Shouldn't it be consistent across all FreeBSD base utilities so all of them can use numerical ID and name? Good idea! Are you offering to create a patch? ;-) It'd be my guess that given they weren't all created at the same time, nor the same individual; that (quite probably?) the "jail" additions were also added at different times, and by different people. So I'd imagine that unless someone with a commit bit decides one day they'd like to take that on. Someone(tm) maybe you? will need to propose a patch. :-) If I can understand C sources I will create the patch by myself instead of just posting here. Unfortunately I am able to code in sh, php and a bit of javascript and perl but no C. :) Miroslav Lachman Sure, a PR would be handy for this - it's a pretty simple thing to add, and consistency would indeed be a good move. PR 229266 created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229266 Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jail related inconsistencies in FreeBSD tools parameters
Chris H wrote on 2018/06/22 23:46: On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.f...@quip.cz> said I don't know if it is better to discuss it in jail@ or stable@ list so a do cross-post. FreeBSD has many jail aware utilities but they are inconsistent in taking JID as parameter. For example "sockstat" takes -j JID "Show only sockets belonging to the specified jail ID" and it means numeric ID only. On the other hand "ps" takes -J JID "This may be either the jid or name of the jail. Use -J 0 to display only host processes." The same apply for "top", it understands jid as a number or name of the jail too. Then again "cpuset" takes only numerical ID of the jail... Shouldn't it be consistent across all FreeBSD base utilities so all of them can use numerical ID and name? Good idea! Are you offering to create a patch? ;-) It'd be my guess that given they weren't all created at the same time, nor the same individual; that (quite probably?) the "jail" additions were also added at different times, and by different people. So I'd imagine that unless someone with a commit bit decides one day they'd like to take that on. Someone(tm) maybe you? will need to propose a patch. :-) If I can understand C sources I will create the patch by myself instead of just posting here. Unfortunately I am able to code in sh, php and a bit of javascript and perl but no C. :) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
jail related inconsistencies in FreeBSD tools parameters
I don't know if it is better to discuss it in jail@ or stable@ list so a do cross-post. FreeBSD has many jail aware utilities but they are inconsistent in taking JID as parameter. For example "sockstat" takes -j JID "Show only sockets belonging to the specified jail ID" and it means numeric ID only. On the other hand "ps" takes -J JID "This may be either the jid or name of the jail. Use -J 0 to display only host processes." The same apply for "top", it understands jid as a number or name of the jail too. Then again "cpuset" takes only numerical ID of the jail... Shouldn't it be consistent across all FreeBSD base utilities so all of them can use numerical ID and name? Should I file a PR for it? Miroslav Lachman PS: I am on FreeBSD 10.4 so I don't know if something is different in newer branches ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iostat busy value calculation
Warner Losh wrote on 2018/06/20 18:13: On Wed, Jun 20, 2018 at 8:55 AM, Miroslav Lachman <000.f...@quip.cz <mailto:000.f...@quip.cz>> wrote: I would like to know how the value of disk "busy" is calculated? I want to use values from iostat in the monitoring (zabbix). iostat shows averages by default and the last column is "busy %", but the first output contains averages from the system boot til now. %busy comes from the devstat layer. It's defined as the percent of the time over the polling interval in which at least one transaction was awaiting completion by the lower layers. It's an imperfect measure of how busy the drives are (in ye-olden days, before tagged queuing and NCQ, it was OK because you had THE transaction pending and it was a good measure of how utilized things were. Now with concurrent I/O in flash devices, it's only an imperfect approximation). Yes, I am aware of this issue. This percentage is just "is it slightly loaded or heavily loaded" indicator. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iostat busy value calculation
Holger Kipp wrote on 2018/06/20 17:37: Dear Miroslav, looking at the manpage for iostat I see: %b % of time the device had one or more outstanding transactions tsvc_t/i total duration of transactions per time period, in seconds sb/itotal time the device had one or more outstanding transac- tions per time period, in seconds So calculating the percentage using sb/i should be fairly easy. If I understand it correctly, then it cannot be calculated from numbers between two independent runs of "iostat -I -x" because it gives me sb/i average from the boot time, so the calculated %b will be overall average instead of average between two runs after 60 seconds. The only possible way to calculated is to run "iostat -I -x -c 2 -w 60" where the sb/i value of the second line will be average of these last 60 seconds. But it also means monitoring probe will wait 60 seconds to get this value (each time) so it is the same problem as I described in my original post with "iostat -x". Miroslav Lachman Am 20.06.2018 um 16:55 schrieb Miroslav Lachman <000.f...@quip.cz<mailto:000.f...@quip.cz>>: I would like to know how the value of disk "busy" is calculated? I want to use values from iostat in the monitoring (zabbix). iostat shows averages by default and the last column is "busy %", but the first output contains averages from the system boot til now. # iostat -x -t da extended device statistics device r/s w/skr/skw/s qlen svc_t %b ada0 2.5 13.849.0 287.90 45.7 2 ada1 2.6 13.851.7 287.90 39.6 2 I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 seconds because it means monitoring needs to wait 20 seconds on each run. I can use absolute values from iostat. This output is without any delay and the monitoring SW can calculate averages between two runs. But the last column is no busy %, it is sb/i. # iostat -I -x -t da extended device statistics device r/i w/i kr/i kw/i qlen tsvc_t/i sb/i ada0 7403218.0 40825749.0 144647824.0 849655694.00 2204904.2 73121.8 ada1 7537423.0 40825749.0 152643874.5 849655694.00 1914301.0 69996.5 So the question is - If I want to plot "busy %" in the graph - how the "busy" value in the first example is calculated? Is it possible to calculate it from the numbers that I have from "iostat -I -x" and the know time interval between two runs? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
iostat busy value calculation
I would like to know how the value of disk "busy" is calculated? I want to use values from iostat in the monitoring (zabbix). iostat shows averages by default and the last column is "busy %", but the first output contains averages from the system boot til now. # iostat -x -t da extended device statistics device r/s w/skr/skw/s qlen svc_t %b ada0 2.5 13.849.0 287.90 45.7 2 ada1 2.6 13.851.7 287.90 39.6 2 I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 seconds because it means monitoring needs to wait 20 seconds on each run. I can use absolute values from iostat. This output is without any delay and the monitoring SW can calculate averages between two runs. But the last column is no busy %, it is sb/i. # iostat -I -x -t da extended device statistics device r/i w/i kr/i kw/i qlen tsvc_t/i sb/i ada0 7403218.0 40825749.0 144647824.0 849655694.00 2204904.2 73121.8 ada1 7537423.0 40825749.0 152643874.5 849655694.00 1914301.0 69996.5 So the question is - If I want to plot "busy %" in the graph - how the "busy" value in the first example is calculated? Is it possible to calculate it from the numbers that I have from "iostat -I -x" and the know time interval between two runs? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
error and warnings on buildworld of 10.4
I noticed these warnings and error when I buildworld the update from 10.4-p8 to 10.4-p9 ===> usr.bin/truss (depend) env MACHINE=amd64 CPP="cpp " /bin/sh /usr/src/usr.bin/truss/../kdump/mkioctls return /usr/obj/usr/src/tmp/usr/include > ioctl.c :1:10: fatal error: 'altq/altq.h' file not found #include ^ 1 error generated. In file included from /usr/src/usr.bin/kdump/kdump.c:57: /usr/obj/usr/src/tmp/usr/include/sys/umtx.h:124:6: warning: implicit declaration of function 'atomic_cmpset_acq_long' is invalid in C99 [-Wimplicit-function-declaration] if (atomic_cmpset_acq_long(&umtx->u_owner, UMTX_UNOWNED, id) == 0) ^ /usr/obj/usr/src/tmp/usr/include/sys/umtx.h:151:6: warning: implicit declaration of function 'atomic_cmpset_rel_long' is invalid in C99 [-Wimplicit-function-declaration] if (atomic_cmpset_rel_long(&umtx->u_owner, id, UMTX_UNOWNED) == 0) ^ 2 warnings generated. cc -O2 -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump -I/usr/src/usr.bin/kdump/../.. -I. -DPF -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -c ioctl.c -o ioctl.o In file included from ioctl.c:52: /usr/obj/usr/src/tmp/usr/include/dev/lmc/if_lmc.h:939:13: warning: no previous extern declaration for non-static variable 'ssi_cables' [-Wmissing-variable-declarations] const char *ssi_cables[] = ^ 1 warning generated. buildworld continued and I was able to run installworld so it seems "everything" works, but I think there should not be these errors. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Notification for gmirror failures
Andrea Brancatelli wrote on 2018/05/08 09:28:
Hi,
out of curiosity, does any kind of GMirror-failure notification tools
exist?
Either native... SNMP... external ports... whatever?
I don't know any daemon like solution so I wrote some simple shell
script. Its used on all our machines. It should be run be cron in some
sane interval (like each 5 or 10 minutes)
#!/bin/sh
## $Id: check_gmirror.sh 8c1f418ba7f5 2017-06-15 12:36 +0200 lachman $
export PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin"
mailto="y...@example.com"
subject_pref="$(hostname) gmirror"
notify_state="/var/run/${0##*/}.notified"
cmd_out=$(gmirror status -s)
components="$(echo "$cmd_out" | grep -F -v COMPLETE)"
if [ -n "$components" ]; then
if [ ! -f "$notify_state" ]; then
subject="$subject_pref FAILED - $(date '+%Y-%m-%d %H:%M:%S')"
echo "$cmd_out" | sed -E 's/(SYNCHRONIZING,) [0-9]+%/\1 x%/' >
"$notify_state"
echo "$cmd_out" | mail -s "$subject" "$mailto"
echo "$subject" | logger
else
subject="$subject_pref FAILED - $(date '+%Y-%m-%d %H:%M:%S')"
echo "$cmd_out" | sed -E 's/(SYNCHRONIZING,) [0-9]+%/\1 x%/' >
"$notify_state.now"
diff -u -b -B "$notify_state" "$notify_state.now" >
"$notify_state.diff"
if [ -s "$notify_state.diff" ]; then## if diff is not empty
cat "$notify_state.diff" | mail -s "$subject" "$mailto"
echo "$subject additional failure occurred" | logger
cp "$notify_state.now" "$notify_state"
fi
rm "$notify_state.now" "$notify_state.diff"
fi
else
if [ -f "$notify_state" ]; then
rm "$notify_state"
subject="$subject_pref now OK - $(date '+%Y-%m-%d %H:%M:%S')"
echo "$cmd_out" | mail -s "$subject" "$mailto"
echo "$subject" | logger
fi
fi
We have similar script for checking ZFS too.
Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Ancient FreeBSD update path
Kurt Jaeger wrote on 2018/01/19 15:24: Hi! I have a couple of ancient FreeBSD install that I have to bring into this century (read either 10.4 or 11.1) :-) I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD 9.3-RELEASE-p53. What upgrade strategy would you suggest? The best way is to update stepwise using freebsd-update, so: 8.0 -> 8.3 -> 9.1 -> 9.3 -> 10.1 -> 10.3 I would recommend source upgrade instead of binary freebsd-update. It is more predictable then freebsd-update if you are updating sooo old system Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10 -> 11)? Boiling water on the HDs? :-) Stepwise. Huge jumps have too many rough edges. I did upgrade from 8.4 to 10.2 or 10.3, not sure. There was some make warning in make installworld phase so I did "make installworld" twice to be sure everything is OK. There is (maybe) simpler way - download (or create own) tar balls of base and kernel of your target version (10.4 or 11.1), unpack it over old system (in single user) then you can use make delete-old if you will have /usr/src with updated source. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
cannot access Areca controller after OS upgrade to 10.4-RELEASE
Hello, We have machine with Areca controller: arcmsr0: > mem 0xde00-0xde0f,0xde11-0xde11,0xde10-0xde10 irq 17 at device 0.0 on pci2 Areca RAID adapter0: ARC-1200 F/W version V1.50 2012-01-04 smartmontools worked on device arcmsr0 for years, but after system upgrade from 10.3 to 10.4-RELEASE smartmontools does not return results, it hangs indefinitely. Smartmontools packages are built on our Poudriere with OS version 10.4 so it should match. We use smartctl with this params: # smartctl -A -d areca,2 /dev/arcmsr0 smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.4-RELEASE amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Nothing more is displayed. Pressing Ctrl+T gives me load: 3.01 cmd: smartctl 25305 [running] 71.45r 3.09u 68.25s 100% 4204k load: 3.01 cmd: smartctl 25305 [running] 74.96r 3.26u 71.58s 100% 4204k I tried to run areca-cli but it also shows nothing. OS is running from RAID device da0 fine, but controller info is inaccessible. Was there some changes between 10.3 / 10.4? What can I do to debug this problem? Kind regards Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350]
Rafal Lukawiecki wrote on 2017/08/09 14:47: Apologies if this is the wrong way to approach the FreeBSD community wisdom: I am new here, please forgive. I am unable to boot/install FreeBSD-11.1-RELEASE-amd64-memstick.img (dated 2017-July-21) on a brand-new HPE MicroServer Gen10 containing an AMD Opteron X3421. Boot hangs very early in the process. I have described the issue, and all remedies that I have tried, in detail on the forum (https://forums.freebsd.org/threads/61936/) and I have logged a bugzilla bug [221350]. It has been suggested to me that FreeBSD might not yet support this new AMD processor, or that it has issues with the chipset. As this is equipment from a major vendor, I wonder if it is likely that it would be supported at some stage in the *near* future. Although I am somewhat new to FreeBSD, I have 30+ years of dev/OS/crypto/AI experience (way back from System V) and I would be willing and hopefully able to help debug this issue if it is at all likely that I could get support for it from the FreeBSD developers. May I politely ask if in your opinion this equipment is likely to be supported soon? If not, I will return it to the vendor and use something a little older. If this is the wrong place to ask, please kindly direct me to the correct mailing list. The full details with boot console outputs: https://forums.freebsd.org/threads/61936/ Bugzilla bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 I suggest you to test booting with fresh image of CURRENT (12.0). You can find it on ftp.freebsd.org /pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/12.0 Or you can try to boot some older ISO like 10.3. I remember some regression years ago with booting problem on newer version. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Little issue with Jails
Software Information wrote on 2017/07/11 19:01:
Hi All
I am using FreeBSD 11 and have created a new jail using the following steps
1. make buildworld DESTDIR=/here/is/the/jail
2. make installworld DESTDIR=/here/is/the/jail
3. make distribution DESTDIR=/here/is/the/jail
4. mount -t devfs devfs /here/is/the/jail/dev
I have the following in my host rc.conf
jail_enable="YES" # Set to NO to disable starting of any jails
jail_list="www" # Space separated list of names of jails
Note: Jail names in jail_list should contain alphanumeric characters only.
For each jail listed in jail_list, a group of rc.conf(5) settings, which
describe the particular jail, should be added:
jail_www_rootdir="/usr/jail/www" # jail's root directory
jail_www_hostname="jailname.org" # jail's hostname
jail_www_ip="IP_Address" # jail's IP address
jail_www_devfs_enable="YES" # mount devfs in the jail
On the host, I did sysctl security.jail.allow_raw_sockets=1
In /etc/jail.conf, in the config section for that jail, I entered the
line *allow.raw.sockets
= 1 *
and I also did an *echo 'security.jail.allow_raw_sockets=1' >>
/etc/sysctl.conf *inside the jail.
From what I can tell, I should be able to ping inside the jail now but it
still doesn't work. Does anyone see anything I may have left out?
I recommend you to use jail.conf only and do not set jail variables in
rc.conf. It is not good to mix these two.
Put jail_enable="YES" in to rc.conf and then this in to jail.conf:
## Typical static defaults:
## Use the rc scripts to start and stop jails. Mount jail's /dev.
exec.start = "/bin/sh /etc/rc";
exec.stop = "/bin/sh /etc/rc.shutdown";
exec.clean;
exec.system_user = "root";
exec.jail_user = "root";
mount.devfs;
devfs_ruleset = 4;
enforce_statfs = 1;
allow.set_hostname = 0;
allow.sysvipc = 0;
allow.raw_sockets = 0;
## Dynamic wildcard parameter:
## Base the path off the jail name.
path= "/usr/jail/$name";
exec.consolelog = "/var/log/jail/$name.console";
mount.fstab = "/etc/fstab.$name";
## Jail www
www {
host.hostname = "jailname.example.com";
ip4.addr = 10.10.10.10;
allow.raw_sockets = 1;
}
Then you can run this jail by command:
# service jail start www
Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.3 to 11.1 upgrade
Zoran Kolic wrote on 2017/06/20 17:12: Generally (and previously) the advice is to go via the next major version so you should go: 9.3 -> 10.x -> 11.x not 9.3 -> 11.x Exactelly what I want to avoid. People successfuly upgraded, without branch 10. In the past I did 8.4 to 10.3, but not by freebsd-update. We are using make installkernel + make installworld method. 9.3 to 11.1 can work similarly. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Missing units in df -h output
Today I noticed missing units (G) in the output of 'df -h' command if size is exactly 1000G This is on FreeBSD 10.3-RELEASE-p18 amd64 GENERIC /# df -h /vol0/remote_backup/rico Filesystem SizeUsed Avail Capacity Mounted on tank0/vol0/remote_backup/rico1.4T1000443G69% /vol0/remote_backup/rico The same without -h # df /vol0/remote_backup/rico Filesystem 1K-blocks Used Avail Capacity Mounted on tank0/vol0/remote_backup/rico 1513215636 1048349068 46486656869% /vol0/remote_backup/rico I don't know if the G suffix is stripped by formatting to columns / size of field is limited to 4 characters if '-h' is used or anything else. The FS is ZFS if this matters. Is this known issue? Should I file PR for this? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Jailed periodic daily scripts smashing CPU
Dustin Wenz wrote on 2017/02/16 22:47: I have a number of servers with roughly 60 jails running on each of them. On these hosts 60 is way more than we have on our jailers. Daily / security scripts are very disk IO intensive so we end up with changing time in /etc/crontab in each jail for periodic tasks. The best way is to randomize these times on jail creation time. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Boot partition size
Aristedes Maniatis wrote on 2017/01/30 04:41: Note that this page: https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror needs to be adjusted. This line: gpart add -b 34 -s 128k -t freebsd-boot ad0 needs to instead be gpart add -a 4k -s 512k -t freebsd-boot ad0 I don't have edit rights. Probably someone needs to clean up and merge many of these pages: https://wiki.freebsd.org/RootOnZFS/ I changed the page, now it has 512k for boot partition. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [ZFS] files in a weird situtation
David Marec wrote on 2016/12/18 09:30:
On 18.12.2016 01:38, Adam Vande More wrote:
I am unable to understand what your intent is here. If you wish to
delete it, you can do:
find . -inum 10552574 -exec rm {} \;
It fails on «No such file or directory».
This file missing, not much works.
I have installed a copy into `/usr/lib` to make the system run again.
So, I can't install a new world: `install -C` fails in the same way.
Then you can boot from recovery media like mfsBSD and unpack good known
distribution from kernel.txz and base.txz (or do make installkernel &&
make installworld from NFS mounted /usr/src and /usr/obj).
But if dataset in question is somehow corrupted maybe you need to make
different dataset, extract all files, remove old dataset and rename this
new dataset.
If this is pool error than it will be better to scratch it and start
again from backups.
Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zpool get all: Assertion failed / Abort (core dumped)
Steven Hartland wrote on 2016/12/02 02:06: Are you sure your kernel and world are in sync? Yes, built from sources on our build server and then distributed by NFS to all machines: # freebsd-version -u 10.3-RELEASE-p12 # freebsd-version -k 10.3-RELEASE-p12 On 01/12/2016 23:53, Miroslav Lachman wrote: There is some minor problem with "zpool get all" command if one of two pools is unavailable: # zpool get all Assertion failed: (nvlist_lookup_nvlist(config, "feature_stats", &features) == 0), file /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_config.c, line 250. Abort (core dumped) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
zpool get all: Assertion failed / Abort (core dumped)
There is some minor problem with "zpool get all" command if one of two pools is unvailable: # zpool get all Assertion failed: (nvlist_lookup_nvlist(config, "feature_stats", &features) == 0), file /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_config.c, line 250. Abort (core dumped) # zpool list NAMESIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT ssdtank1 - - - - - - - UNAVAIL - tank0 1.80T 1.08G 1.80T-0%0% 1.00x ONLINE - I understand that it cannot work properly but I think it should not core dumped. Pool details: # zpool status pool: ssdtank1 state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-3C scan: none requested config: NAME STATE READ WRITE CKSUM ssdtank1 UNAVAIL 0 0 0 mirror-0UNAVAIL 0 0 0 17880119912861428605 UNAVAIL 0 0 0 was /dev/gpt/ssd0tank1 17492271345202510424 UNAVAIL 0 0 0 was /dev/gpt/ssd1tank1 pool: tank0 state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM tank0 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk0tank0 ONLINE 0 0 0 gpt/disk1tank0 ONLINE 0 0 0 errors: No known data errors # uname -srmi FreeBSD 10.3-RELEASE-p12 amd64 GENERIC Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Dying jail
Peter wrote on 2016/10/28 14:28: Eugene Grosbein wrote: Hi! Recently I've upgraded one of my server running 9.3-STABLE with jail containing 4.11-STABLE system. The host was source-upgraded upto 10.3-STABLE first and next to 11.0-STABLE and jail configuration migrated to /etc/jail.conf. The jail kept intact. "service jail start" started the jail successfully but "service jail restart" fails due to jail being stuck in "dying" state for long time: "jls" shows no running jails and "jls -d" shows the dying jail. Same issue here. During upgrade to 10 I wrote a proper jail.conf, and, as this is now a much more transparent handling, I also began to start+stop my jails individually w/o reboot. I found the same issue: often jails do not want to fully terminate, but stay in the "dying" state - sometimes for a minute or so, but sometimes very long (indefinite). It seems this is not related to remaining processes or open files (there are none) but to network connections/sockets which are still present. Probably these connections can be displayed with netstat, and probably netstat -x shows some decreasing counters associated with them - I have not yet found the opportunity to figure out what they exactly mean, but anyway it seems like there may be long times involved (hours? forever?), unless one finds the proper connection and terminates both ends. There seems to be no other way to deliberately "kill" such connections and thereby terminate the jail, so the proposal to let it have a new number might be the only feasible approach. (I dont like it, I got used to the numbers of my jails.) I am no sure where but I think it was discussed in jail@ mailing list that keeping the same JID is not recommended. Or recycling freed JID. It was few years ago when I talked about this with BZ. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: boot0cfg on does not set default selection on gmirror device
Ian Smith wrote on 2016/10/21 16:43: On Fri, 21 Oct 2016 13:39:57 +0200, Patrick M. Hausen wrote: > Hi, all, > > we are repeatedly bitten by the following misbehaviour of boot0cfg: > > root@hd45:/usr/local # boot0cfg -s 1 mirror/m0 > root@hd45:/usr/local # boot0cfg -v mirror/m0 > # flag start chs type end chs offset size > 1 0x80 1: 0: 1 0xa5 1022:254:6316065 16418430 > 2 0x00 1023: 0: 1 0xa5 1020:254:63 16434495 16418430 > 3 0x00 1021: 0: 1 0xa5768:254:63 32852925 1920667140 > > version=1.0 drive=0x80 mask=0xf ticks=182 bell= (0x7) > options=packet,update,nosetdrv > default_selection=F2 (Slice 2) > > So, while it should have set the default to slice 1, it simply didn't. boot0cfg isn't mirror-aware as such and thinks it's using BIOS services to write to a specific drive, and likely did write to one of the disks, but it seems gmirror isn't updating both disks' MBRs - which might not be too surprising. Does it work 'sometimes'? We are using gmirror for whole drives mirroring from the time when it was introduced. It was always working with MRB/BSD. gmirror label gm0 ada0 ada1 And then you can use fdisk + bsdlabel or gpart to create slices and partitions and set it bootable on /dev/mirror/gm0. I didn't tried it with FreeBSD 10.3, but it works with 8.x (we skipped 9.x and all 8.x boxes were upgraded to 10.2 then 10.3) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs, a directory that used to hold lot of files and listing pause
Eugene M. Zheganin wrote on 2016/10/20 15:47: Hi. I have FreeBSD 10.2-STABLE r289293 (but I have observed this situation on different releases) and a zfs. I also have one directory that used to have a lot of (tens of thousands) files. I surely takes a lot of time to get a listing of it. But now I have 2 files and a couple of dozens directories in it (I sorted files into directories). Surprisingly, there's still a lag between "ls" and an output: [...] I've seen this situation before, on other servers, so it's not the first time I encounter this. However, it's not 100% reproducible (I mean, if I fill the directory with dozens of thousands of files, I will not certainly get this lag after the deletion). What about snapshots? Are there any snapshots on this filesystem? Or scrub running in the background? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 11.0 Install Question
Matthew Seaman wrote on 2016/10/19 11:08: On 2016/10/19 09:55, Matt Smith wrote: On Oct 19 10:38, Miroslav Lachman wrote: Jonathan Haack wrote on 2016/10/19 10:09: Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, required by "pkg" Do not panic, just run pkg-static to upgrade pkg it-self /usr/local/sbin/pkg-static install -f pkg I think that these instructions should be in the announcement release notes as this question comes up a lot. The notes just say something like "upgrade all your packages". Most people will then just try and run pkg upgrade and get that error without knowing how to solve it. It's not intuitive unless you have come across this before. pkg(8) does have a built-in warning when it detects an OS major version upgrade, which is to do a forced upgrade of pkg(8) so it matches the ABI versions of system shlibs. Did that warning appear in this case? I think it is not shown if pkg is missing some libraries. It is shown when OS major version changes and you run pkg befor old libraries are deleted or if you run pkg-static: pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 11.0 Install Question
Jonathan Haack wrote on 2016/10/19 10:09: Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, required by "pkg" Do not panic, just run pkg-static to upgrade pkg it-self /usr/local/sbin/pkg-static install -f pkg Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: moving ezjail-based jails from 10.3 host to 11.0 host
Marko Cupać wrote on 2016/10/17 17:43: [...] Now, to give answer to my own question: everything works fine, after - of course - reinstalling all the packages with `pkg-static upgrade -f'. Reinstalling all packages? So you didn't just move jails from one host to another but you upgraded them to 11.0 also? Because I had feeling that you want just to move them to another machine. And if you just move them (completely with shared basejail) you don't need to reinstall packages. As Oliver said you can use rsync to transfer them without need to compress + scp + uncompress. It is much faster transfer than making archives. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: omitting make installkernel in an upgarde between 2 x 10-stable
Matt Smith wrote on 09/04/2016 18:21: On Sep 04 16:35, Julian H. Stacey wrote: Hi, Reference: From:"Julian H. Stacey" Date:Sun, 04 Sep 2016 13:37:26 +0200 "Julian H. Stacey" wrote: Hi stable@ people In a jail, uname -r 10.3-RELEASE-p4, I started cd /usr/src ; make buildworld, then realised per https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I will not be able to make installkernel ; reboot preceeding make installworld Am I on route to shooting myself in the foot ? It survived. No shot foot :-) It should work in most cases but there are always some edge cases where it can fail. Just to let you know. I have done this for years on versions 4 through to 10 and never had a single problem. Only on minor version upgrades though from say 10.2 to 10.3. My procedure is: make -j4 buildworld && make -j4 buildkernel make installkernel make installworld mergemaster shutdown -r now make delete-old make delete-old-libs I do this because I don't have a keyboard or monitor on the machine during normal use. This has *always* worked fine. However for a major version upgrade from say 10.x to 11.x I have always done it the correct and proper way using single user mode via the console. I never did it in single user. There were some cases where it emitted warnings in the case of upgrade from 8.4 to 10.2 but it was fixed by second run of installkernel && installworld before "shutdown -r now" and then everything booted fine. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mrsas(4)
Eugene M. Zheganin wrote on 07/29/2016 15:41: Hi. I'm experiencing some weird troubles with an LSI MegaRAID SAS9341-4i controller: sometimes, all of a sudden, it reports that disk was reattached. I'm using zfs, and a redundant pool, so, besides the fact that it's bad by itself, everything should continue to work, but instead my FreeBSD starts to livelock, and all disk/zfs commands stop working - they just hang (however, I'm able to log in, launch gstat and other utilities, and most of the services seem to be unaffected, however, iSCSI target starts to behave weirdly too). I wrote a letter to the LSI support, but I guess they will first ask me to try the latest driver, which for some reason isn't commited in the tree yet. So, two questions: - why the latest driver (6.710.11.00) isn't in the main tree, it's from december 2015, so at least it seems like it should have been made it to the 11.x. In 11.x I still see the 06.709.07.00-fbsd ? may be I don't unerstand something. - has anyone seen anything similar on mrsas ? I'm kinda open to the ideas. To be honest, I suspect the controller and the firmware, because with factory-default firmware version I had seen all sorts of madness, including disk detaching after requesting SMART data with smartmontools. This was reproducible and solved with the firmware update, but considering the amount of fixes that each new version does contain, I suppose there's many of the bugs that left unfixed. mrsas is very strange so I moved to mfi driver for Dell PowerEdge T130 with PERC H330. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200993 Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pkg(8) still not part of stable/11 (yet)???
Harry Schmalzbauer wrote on 07/28/2016 19:52: Hello, I just tried 11-beta2 – as usual, many thanks for all your hard work, Devs and REs! I'm very concerned that there's still just a bootstrap-pkg :-( [...] Please, don't ship FreeBSD 11 without a full version of pkg(8) in the base! There are no plans to have pkg in base - not until base will be packaged too. (there are good reasons for this) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 10.3 slow boot on Supermicro X11SSW-F
Kurt Jaeger wrote on 07/14/2016 18:11: Hi! I installed FreeBSD 10.3 on brand new machine Supermicro X11SSW-F. It sits on top of 4x 1TB Samsung SSDs on ZFS RAIDZ2. The booting is painfully slow from BTX to menu to kernel loading. I have the same problem on a Supermicro X11SSH-LN4F. Progress indicated by \ | / - characters is changing by speed of 1 character per 2 seconds. The whole boot process takes about 10 minutes. I found this blog post solving the same problem http://smyck.net/2016/06/15/freebsd-slow-zfs-bootloader/ I'll test that solution. Thanks for the pointer! If there will not be 10.4 Release, there is nothing to fix, because 11.0 works, I know... But still - is this something already known and fixed in 11 loader or is it something fixed by coincidence? Can it be covered by some regression test? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 10.3 slow boot on Supermicro X11SSW-F
Steven Hartland wrote on 06/28/2016 16:43: Does adding the following to /boot/loader.conf make any difference? hw.memtest.tests="0" No it doesn't help. BTX loader it-self is slow as hell and this settings can't affect BTX. Or am I wrong? Booting is stil about 10 minutes with 10.3 loader and hw.memtest.tests="0" in loader.conf Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 10.3 slow boot on Supermicro X11SSW-F
I installed FreeBSD 10.3 on brand new machine Supermicro X11SSW-F. It sits on top of 4x 1TB Samsung SSDs on ZFS RAIDZ2. The booting is painfully slow from BTX to menu to kernel loading. Progress indicated by \ | / - characters is changing by speed of 1 character per 2 seconds. The whole boot process takes about 10 minutes. I found this blog post solving the same problem http://smyck.net/2016/06/15/freebsd-slow-zfs-bootloader/ It seems there is some bug in loader in 10.3. If /boot/pmbr, /boot/gptzfsboot and /boot/zfsloader are replaced by files from 11-CURRENT snapshot (from ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/11.0-CURRENT/base.txz) the booting speed is back to normal. Is it know problem? What was changed in loader between 10.3 and 11? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSHd in FreeBSD 10.3 complains about PrintLastLog
Miroslav Lachman wrote on 04/05/2016 03:04:
I had "PrintLastLog yes" in my sshd_config for many years but after
upgrade to 10.3 I got this error message:
/etc/ssh/sshd_config line 112: Unsupported option PrintLastLog
It is confusing because "#PrintLastLog yes" is still included in default
sshd_config file and mentioned in manpage.
Is it error in default config or error in sshd? What should be fixed?
Now I found in /usr/src/crypto/openssh/servconf.c
#ifdef DISABLE_LASTLOG
{ "printlastlog", sUnsupported, SSHCFG_GLOBAL },
#else
{ "printlastlog", sPrintLastLog, SSHCFG_GLOBAL },
#endif
Does it means that new sshd in FreeBSD 10.3 was (un)intentionally
compiled with "DISABLE_LASTLOG" (--disable-lastlog)
Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
SSHd in FreeBSD 10.3 complains about PrintLastLog
I had "PrintLastLog yes" in my sshd_config for many years but after upgrade to 10.3 I got this error message: /etc/ssh/sshd_config line 112: Unsupported option PrintLastLog It is confusing because "#PrintLastLog yes" is still included in default sshd_config file and mentioned in manpage. Is it error in default config or error in sshd? What should be fixed? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: intr using Swap
Doug Hardie wrote on 02/18/2016 07:50: On 17 February 2016, at 17:45, Lowell Gilbert wrote: Doug Hardie writes: [...] Your observations are more useful, but I'm still not sure they indicate a problem that needs to be solved. There are clearly cases where significant quantities of swap can get used up storing copies of clean pages backing files on disk. Unless that slows down bringing in new pages that need to be read or written, I don't think that's a problem. Well, the problem is quite significant for me in that eventually the system runs out of swap and starts killing processes. Its not quite random, but I haven't spent much time trying to figure out how it selects those to kill. The specific system unfortunately is remote (about a 3 hour drive) and when sshd gets killed, I have no option other than having someone go on site to reboot it. Was sshd ever killed? I think FreeBSD has some "exceptions" implemented and some processes have higher value - not to be killed so easily. I had some system without swap and there were many processes killed every few days, but never sshd. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: make installworld creates empty dirs which are deleted by make delete-old
Miroslav Lachman wrote on 01/16/2016 14:28: Philippe Michel wrote on 01/16/2016 13:51: On Sat, 16 Jan 2016, freebsd-stable-requ...@freebsd.org wrote: I updated the server 3 times in one week (to 10.2-p8, -p9, -p10). Those directories were deleted by delete-old # make -DBATCH_DELETE_OLD_FILES delete-old >>> Removing old files (only deletes safe to delete libs) >>> Old files removed >>> Removing old directories /usr/share/doc/atf /usr/share/atf /usr/include/atf-c++ /usr/include/atf-c >>> Old directories removed To remove old libraries run 'make delete-old-libs'. By after next installworld, they are back. You build world WITHOUT_TESTS=true, don't you ? There are many of these flags that are somehow missed when creating directories at install. I don't use WITHOUT flags for buildworld / installwordl. The only WITHOUT is one for kernel: WITHOUT_KERNEL_SYMBOLS=yes [...] I think some similar cases were fixed a few months ago by NGie Cooper but it was apparently those he stumbled on by himself or some specific bug reports rather than the start of a more exhaustive sweep. I suppose opening a PR could have helped but I procrastinated :-(. OK, I will open PR for this today. Thank you for your suggestions. I found a half year old PR for this https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201072 Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: make installworld creates empty dirs which are deleted by make delete-old
Philippe Michel wrote on 01/16/2016 13:51: On Sat, 16 Jan 2016, freebsd-stable-requ...@freebsd.org wrote: I updated the server 3 times in one week (to 10.2-p8, -p9, -p10). Those directories were deleted by delete-old # make -DBATCH_DELETE_OLD_FILES delete-old >>> Removing old files (only deletes safe to delete libs) >>> Old files removed >>> Removing old directories /usr/share/doc/atf /usr/share/atf /usr/include/atf-c++ /usr/include/atf-c >>> Old directories removed To remove old libraries run 'make delete-old-libs'. By after next installworld, they are back. You build world WITHOUT_TESTS=true, don't you ? There are many of these flags that are somehow missed when creating directories at install. I don't use WITHOUT flags for buildworld / installwordl. The only WITHOUT is one for kernel: WITHOUT_KERNEL_SYMBOLS=yes Full content of src.conf and make.conf root@sm-reserve ~/# cat /etc/src.conf ## src.conf WITHOUT_KERNEL_SYMBOLS=yes root@sm-reserve ~/# cat /etc/make.conf ## make.conf WITH_PKGNG= yes SVN_UPDATE=yes SVN="/usr/local/bin/svnup" SVNFLAGS="" WITH_GHOSTSCRIPT_VER=9 DEFAULT_VERSIONS= perl=5.20 mysql=5.5m php=55 python=2.7 apache=2.4 ## https://wiki.freebsd.org/Ports/Options/OptionsNG ## OptionsNG sets DOCS, EXAMPLES and NLS as default - we do not need them OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS ## cd /usr/ports/www/apache22 && make print-closest-mirrors MASTER_SITE_APACHE_HTTPD?= http://apache.miloslavbrada.cz/httpd/ http://mirror.hosting90.cz/apache/httpd/ ftp://mirror.hosting90.cz/apache/httpd/ http://www.eu.apache.org/dist/httpd/ ## closest PHP mirror MASTER_SITE_PHP= http://cz.php.net/%SUBDIR%/ FWIW, with more WITHOUT flags set to true, my own list of directories created again and again is : Removing old directories /usr/share/snmp/mibs /usr/share/snmp/defs /usr/share/snmp /usr/share/examples/pf /usr/share/examples/ipfilter /usr/share/examples/hast /usr/share/examples/bhyve /usr/share/doc/smm/07.lpd /usr/share/doc/atm /usr/share/doc/atf /usr/share/atf /usr/libexec/lpr/ru /usr/libexec/lpr /usr/include/netnatm/sig /usr/include/netnatm/saal /usr/include/netnatm/msg /usr/include/netnatm/api /usr/include/netgraph/bluetooth/include /usr/include/netgraph/bluetooth /usr/include/krb5 /usr/include/kadm5 /usr/include/gpib /usr/include/dev/ieee488 /usr/include/bsnmp /usr/include/atf-c++ /usr/include/atf-c /etc/bluetooth /etc/autofs Old directories removed I think some similar cases were fixed a few months ago by NGie Cooper but it was apparently those he stumbled on by himself or some specific bug reports rather than the start of a more exhaustive sweep. I suppose opening a PR could have helped but I procrastinated :-(. OK, I will open PR for this today. Thank you for your suggestions. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
make installworld creates empty dirs which are deleted by make delete-old
I updated the server 3 times in one week (to 10.2-p8, -p9, -p10). make check-old lists these directories on each update # make check-old >>> Checking for old files >>> Checking for old libraries >>> Checking for old directories /usr/include/atf-c /usr/include/atf-c++ /usr/share/atf /usr/share/doc/atf To remove old files and directories run 'make delete-old'. To remove old libraries run 'make delete-old-libs'. Those directories were deleted by delete-old # make -DBATCH_DELETE_OLD_FILES delete-old >>> Removing old files (only deletes safe to delete libs) >>> Old files removed >>> Removing old directories /usr/share/doc/atf /usr/share/atf /usr/include/atf-c++ /usr/include/atf-c >>> Old directories removed To remove old libraries run 'make delete-old-libs'. By after next installworld, they are back. I think there is some bug (leftover) in make install / mtree or something like this and those directories should not be created any more. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: A recent 10.2-STABLE no longer builds on a no-exec /usr/src file system
Mark Martinec wrote on 11/26/2015 19:31: Up to about a week ago building world on FreeBSD 10.2-STABLE went just fine. Today after svn update the build fails: # make buildworld [...] CC='cc ' mkdep -f .depend.getprotoent_test -a -I/usr/src/lib/libc/tests/net -I/usr/src/lib/libnetbsd -I/usr/src/contrib/netbsd-tests -std=gnu99 /usr/src/contrib/netbsd-tests/lib/libc/net/t_getprotoent.c echo getprotoent_test: /usr/obj/usr/src/tmp/usr/lib/libc.a /usr/obj/usr/src/tmp/usr/lib/private/libatf-c.a >> .depend.getprotoent_test (cd /usr/src/lib/libc/tests/net && make -f /usr/src/lib/libc/tests/net/Makefile _RECURSING_PROGS= SUBDIR= PROG=ether_aton_test DEPENDFILE=.depend.ether_aton_test .MAKE.DEPENDFILE=.depend.ether_aton_test depend) /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr /usr/src/sys/net/if_ethersubr.c aton_ether_subr.c make[7]: exec(/usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr) failed (Permission denied) *** Error code 1 Stop. make[7]: stopped in /usr/src/lib/libc/tests/net *** Error code 1 It turns out that our file system /usr/src had an "exec" flag turned off, so now running a command: /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr fails with "Permission denied". It would be valuable if building a system on an exec-protected src file system would continue to be possible. Not sure if the /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr is the only such new command breaking the build. Anyway, a simple workaround is to run shell from a command line instead of as a shebang, i.e.: # /bin/sh /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr instead of: # /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr I was puzzled by similar thing years ago. I was using /var/db and /tmp mounted with noexec. And then there was some changes. Ports need /var/db with exec because of some script in /var/db/pkg and /tmp must have exec too for buildworld or installworld (I don't remember it well, now I always do mount -u -o current,exec /tmp before build + install world and kernel) Anyway - it would be better to not have these partitions mounted with exec. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su on 10.2: TERM: Undefined variable
Michael B. Eichorn wrote on 11/23/2015 05:32: On Sun, 2015-11-22 at 19:43 -0500, Brandon Allbery wrote: On Sun, Nov 22, 2015 at 6:31 PM, Erich Dollansky < erichsfreebsdl...@alogt.com> wrote: this is a bit strange. TERM should be always define to tell the applications the capabilities of your terminal. Things run from crontab don't have a terminal. Indeed cron only sets SHELL HOME PATH and USER I note the error message looks like csh; check the target user's .cshrc. but we are running from cron which defaults to sh inside a script with a #!/bin/sh and the call is su -m which should leave the environment unmodified and use the current shell (presumably still sh) as the login shell. Also www has a home of /nonexistant, no .cshrc file to be had. Maybe freebsd-update IDS is in order? We don't use freebsd-update. All our machines are updated / upgraded from central build server by "make installkernel && make installworld" throught NFS mounted /usr/src and /usr/obj I will try this script in clean FreeBSD 10.2 install in VirtualBox and will report results later. Thank you for your time! Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su on 10.2: TERM: Undefined variable
Erich Dollansky wrote on 11/23/2015 00:31: Hi, On Sun, 22 Nov 2015 14:04:25 +0100 Miroslav Lachman <000.f...@quip.cz> wrote: Miroslav Lachman The only workaround I found is adding export TERM="" at the top of the script. this is a bit strange. TERM should be always define to tell the applications the capabilities of your terminal. When X is running, it is normally set to xterm, if nothing is available - or you do not know what is available - set it to vt100. Of course, the best would be to find out why it is not set on your machine. TERM is not set or is empty if script runs from crontab. I think this is normal. Michael's test didn't print value of $TERM too, but his su didn't complained about "Undefined variable". If I run this script in ssh session it prints "screen", because I am using screen. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su on 10.2: TERM: Undefined variable
Miroslav Lachman wrote on 11/22/2015 12:03: Michael B. Eichorn wrote on 11/21/2015 21:42: On Sat, 2015-11-21 at 13:31 +0100, Miroslav Lachman wrote: I noticed some weird behavior of "su" command in shell scripts running from cron after upgrade from FreeBSD 8.4 to 10.2. If I have this in script su -m www -c 'ls -l' then I get "TERM: Undefined variable" on the stderr if this script is run from cron. It works fine on FreeBSD 8.4 Is it intentional behavior? Miroslav Lachman I cannot reproduce your problem. I used the following script: #!/bin/sh echo "BEGIN TEST" echo $TERM su -m www -c 'ls -l' echo $TERM echo "END TEST" crontab is: *****/root/test.sh and the result is: BEGIN TEST total 520765 -rw-r--r-- 1 root wheel 724002816 Aug 12 11:45 FreeBSD-10.2- RELEASE-amd64-disc1.iso -rwxr-xr-x 1 root wheel 90 Nov 21 15:33 test.sh END TEST # freebsd-version 10.2-RELEASE-p7 It's a strange. I tried it on another machine which was installed as 10.1 and upgraded to 10.2-p5 - and I got Undefined variable again: BEGIN TEST TERM: Undefined variable. total 8984 drwxr-xr-x 2 root wheel 1536 Aug 12 13:48 bin -rw--- 1 root wheel 9134080 Nov 22 00:06 dns-terror.core -rw-r--r-- 1 root wheel 836 Nov 5 10:39 extensions.ini drwxr-xr-x 3 root wheel 512 Jul 29 17:49 settings drwxr-xr-x 8 root wheel 512 Aug 9 04:59 settings_atago drwxr-xr-x 2 root wheel 512 Aug 9 03:12 skel_devel -rwxr--r-- 1 root wheel 90 Nov 22 11:52 term_test.sh END TEST Miroslav Lachman The only workaround I found is adding export TERM="" at the top of the script. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su on 10.2: TERM: Undefined variable
Michael B. Eichorn wrote on 11/21/2015 21:42: On Sat, 2015-11-21 at 13:31 +0100, Miroslav Lachman wrote: I noticed some weird behavior of "su" command in shell scripts running from cron after upgrade from FreeBSD 8.4 to 10.2. If I have this in script su -m www -c 'ls -l' then I get "TERM: Undefined variable" on the stderr if this script is run from cron. It works fine on FreeBSD 8.4 Is it intentional behavior? Miroslav Lachman I cannot reproduce your problem. I used the following script: #!/bin/sh echo "BEGIN TEST" echo $TERM su -m www -c 'ls -l' echo $TERM echo "END TEST" crontab is: * * * * * /root/test.sh and the result is: BEGIN TEST total 520765 -rw-r--r-- 1 root wheel 724002816 Aug 12 11:45 FreeBSD-10.2- RELEASE-amd64-disc1.iso -rwxr-xr-x 1 root wheel 90 Nov 21 15:33 test.sh END TEST # freebsd-version 10.2-RELEASE-p7 It's a strange. I tried it on another machine which was installed as 10.1 and upgraded to 10.2-p5 - and I got Undefined variable again: BEGIN TEST TERM: Undefined variable. total 8984 drwxr-xr-x 2 root wheel 1536 Aug 12 13:48 bin -rw--- 1 root wheel 9134080 Nov 22 00:06 dns-terror.core -rw-r--r-- 1 root wheel 836 Nov 5 10:39 extensions.ini drwxr-xr-x 3 root wheel 512 Jul 29 17:49 settings drwxr-xr-x 8 root wheel 512 Aug 9 04:59 settings_atago drwxr-xr-x 2 root wheel 512 Aug 9 03:12 skel_devel -rwxr--r-- 1 root wheel 90 Nov 22 11:52 term_test.sh END TEST Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
su on 10.2: TERM: Undefined variable
I noticed some weird behavior of "su" command in shell scripts running from cron after upgrade from FreeBSD 8.4 to 10.2. If I have this in script su -m www -c 'ls -l' then I get "TERM: Undefined variable" on the stderr if this script is run from cron. It works fine on FreeBSD 8.4 Is it intentional behavior? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS on labelled partitions
Patrick M. Hausen wrote on 11/17/2015 09:08: Hi, all, Am 16.11.2015 um 22:19 schrieb Freddie Cash : You label the disks as they are added to the system the first time. That way, you always know where each disk is located, and you only deal with the labels. we do the same for obvious reasons. But I always wonder about the possible downsides, because ZFS documentation explicitly states: ZFS operates on raw devices, so it is possible to create a storage pool comprised of logical volumes, either software or hardware. This configuration is not recommended, as ZFS works best when it uses raw physical devices. Using logical volumes might sacrifice performance, reliability, or both, and should be avoided. (from http://docs.oracle.com/cd/E19253-01/819-5461/gbcik/index.html) Can anyone shed some lght on why not using raw devices might sacrifice performance or reliability? Or is this just outdated folklore? It was on Solaris but not on FreeBSD. If you were using partitions on Solaris the drive cache was disabled (or something like that, I am not 100% sure) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: trouble upgrade jails to 10.2 (make distrib-dirs)
Aristedes Maniatis wrote on 11/14/2015 14:22: On 15/11/2015 12:14am, Miroslav Lachman wrote: I am getting a failure running mergemaster as per the FreeBSD handbook. I'm a bit lost as to what the error is telling me to do. What was the method used to upgrade host system and jail? Did you used freebsd-update or make installworld? freebsd-update from 10.1 to 10.2. The you are using wrong method to upgrade jail. You should use freebsd-update to upgrade jails too. Mergemaster is supposed to be used only with make installworld method. It cannot work withous sources in /usr/src/ Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: trouble upgrade jails to 10.2 (make distrib-dirs)
Aristedes Maniatis wrote on 11/14/2015 11:08: I am getting a failure running mergemaster as per the FreeBSD handbook. I'm a bit lost as to what the error is telling me to do. What was the method used to upgrade host system and jail? Did you used freebsd-update or make installworld? # mergemaster -U -D /jails/anu_6002 realpath: /usr/src: No such file or directory This means you don't have /usr/src so the mergemaster cannot make files in /var/tmp/temproot because these files are created from /usr/src So make sure you have mounted /usr/src/ with source files for current version of the system (the version you need to update to) and then try this cd /usr/src mergemaster -F -v -i -P -U -t /var/tmp/mergemaster/anu_6002 -d -D /jails/anu_6002 Miroslav Lachman *** The directory specified for the temporary root environment, /var/tmp/temproot, exists. This can be a security risk if untrusted users have access to the system. Use 'd' to delete the old /var/tmp/temproot and continue Use 't' to select a new temporary root directory Use 'e' to exit mergemaster Default is to use /var/tmp/temproot as is How should I deal with this? [Use the existing /var/tmp/temproot] d *** Deleting the old /var/tmp/temproot *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot make: don't know how to make distrib-dirs. Stop make: don't know how to make distrib-dirs. Stop *** FATAL ERROR: Cannot 'cd' to and install files to the temproot environment ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stable/10: high load average when box is idle
Miroslav Lachman wrote on 10/29/2015 12:47: Jeremy Chadwick wrote on 10/29/2015 11:09: [...] I've seen it on both bare-metal and VMs. Please see c#8 in the ticket; there's an itemised list of where I've seen it, but I'm sure it's not limited to just those. OK, I have read your c#8 and did some tests on our affected VMs. With sysctl kern.eventtimer.periodic=1 it is better. Where previously load were about 0.40 is 0.15 now. One of these three systems is FreeBSD 10.2 and on this machine the positive effect of kern.eventtimer.periodic=1 is more visible - load is now 0.00 - 0.05. I don't know if this is some coincidence or something is different in 10.2. Settings of kern.eventtimer is the same on all VMs kern.eventtimer.et.LAPIC.flags: 7 kern.eventtimer.et.LAPIC.frequency: 35071418 kern.eventtimer.et.LAPIC.quality: 600 kern.eventtimer.et.i8254.flags: 1 kern.eventtimer.et.i8254.frequency: 1193182 kern.eventtimer.et.i8254.quality: 100 kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.choice: LAPIC(600) i8254(100) RTC(0) kern.eventtimer.singlemul: 4 kern.eventtimer.idletick: 0 kern.eventtimer.timer: LAPIC kern.eventtimer.periodic: 1 Just for the record - I added graphs of CPU load from these three VMs FreeBSD 10.1 http://imagebin.ca/v/2Kkyq29M13d3 FreeBSD 10.1 http://imagebin.ca/v/2KkzUccxJEoE FreeBSD 10.2 http://imagebin.ca/v/2Kl00mS4RQ3n And coresponding CPU idle percentages FreeBSD 10.1 http://imagebin.ca/v/2Kl0R0U1pRhg FreeBSD 10.1 http://imagebin.ca/v/2Kl0cYiB0mS4 FreeBSD 10.2 http://imagebin.ca/v/2Kl0lIipTKXc As I mentioned the difference with / without kern.eventtimer.periodic=1 is more visible on FreeBSD 10.2. The flat line on the graphs is interval where I disabled almost all services - crontab too - so no measurements in this time. Effect of kern.eventtimer.periodic=1 is visible from 18:00 when I started all usual services. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
