Re: Deprecating base system ftpd?

[Patrick M. Hausen]

Hi all,

> Am 03.04.2021 um 22:39 schrieb Ed Maste :
> I'm happy to make a port for it if anyone needs it. Comments?

A bit late to the party, but my take is: please just don't.

I absolutely freaked out when Apple removed the telnet and ftp clients
from Mac OS and I needed to reinstall them via MacPorts.

People who manage any larger collection of networking gear *depend*
on these outdated but simple services. Client and server side alike.

TFTP is not going away, neither is FTP. I'm dead serious. Remote media
via Supermicro IPMI in 2021? SMB1. Firmware updates for my UPS? FTP.
Scanner/printer/fax all-in-one thingy? Uploads received fax transmissions
via FTP. PBX? Uploads usage reports via FTP. This stuff is here to stay.
In local networks, of course.

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 ...

Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusio

[Patrick M. Hausen]

Hi Warner,

> Am 09.03.2021 um 22:00 schrieb Warner Losh :One issue you 
> may run into is the size of the partition. If it is tiny,

> you'll likely have to create a new ESP. Using /boot/boot1.efi may help and
> can be used in the last step instead of loader.efi, but it's much less
> flexible than loader.efi.

What precisely is the difference between boot1.efi and loader.efi?
Practically from a sysadmin point of view? I have been using boot1.efi
exclusively the last couple of years to boot EFI based systems with ZFS ...

Thanks!
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: LUA ERROR: memory allocation error: block too big

[Patrick M. Hausen]

Hi all,

to add to the argument made by Kyle:

> Am 03.06.2020 um 14:56 schrieb Kyle Evans :
> As an aside, I'd appreciate it if other folks in this thread could
> simply stop dumping all over the many many many hours of work that
> were put into getting lua into shape to replace the high-quality forth
> that was already in place. The reality is that lua won a popularity
> contest long ago [outside of a FreeBSD context][ and lowers the barrier
> to being able to hack on our loader menus, which should be viewed as a
> great thing.

I was equally annoyed at first because I happen to know a good deal of Forth
(and use HP calculators ;-) and my reasoning was like „Lua is just as exotic as 
Forth
so people need to learn the basics of a new language, anyway - why make *me*
relearn everything?“

But in private conversation at one EuroBSDCon I learned that the „bus factor“
of the old bootloader (i.e. how many people have to be overrun by a bus to
make that part of the project unmaintainable because there is zero knowledge
left) was probably 2.

Which is a perfectly good reason to replace a piece of software with a new one
that hopefully more people understand. As for the choice of language I am 
actually
pretty agnostic and willing to learn whatever is needed to get a particular 
task done.

Just my 2ct.
Patrick
-- 
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

___
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-Announce] FreeBSD 12.0 end-of-life

[Patrick M. Hausen]

Hi all,

> Am 18.02.2020 um 18:44 schrieb Pete French :
> Both the DRM issue and VirtualBox are fixed by making sure you recompile and 
> install the kernel modules from the source in /usr/ports when you upgrade the 
> OS, or if 'pkg upgrade' overwrites them. Its a bit annnoying, but hardly a 
> showstopper I find.

`pkg lock` after installing from ports is your friend ;-)

Kind regards,
Patrick
-- 
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

___
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: RELENG_10 to RELENG11 buildworld no possible ?

[Patrick M. Hausen]

Hi all,

> Am 08.07.2019 um 08:30 schrieb Thomas Mueller :
> Or maybe via 11.2R, if that can be built from RELENG_10?

I just completed a successful build of RELENG_11_2 on a
RELENG_10_4 system …

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: fsck vs zvol

[Patrick M. Hausen]

Hi all,


> Am 12.06.2019 um 03:04 schrieb O'Connor, Daniel :
> I have a small UFS partition that is the sysvol for Samba 4 (otherwise it 
> doesn't work due to ACL issues).

AFAIK this was fixed by iX Systems for Samba 4.9:

https://jira.ixsystems.com/browse/NAS-100698

You might want to check if they upstreamed it or if the patch can be
incorporated in the FreeBSD port if not.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

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.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

Hi!

> Am 30.04.2019 um 18:07 schrieb Walter Cramer :
> With even a 1Gbit ethernet connection to your main system, savvy use of (say) 
> rsync (net/rsync in Ports), and the sort of "know your data / divide & 
> conquer" tactics that Karl mentions, you should be able to complete initial 
> backups (on both backup servers) in <1 month.  After that - rsync can 
> generally do incremental backups far, far faster.

ZFS can do incremental snapshots and send/receive much faster than rsync
on the file level. And e.g. FreeNAS comes with all the bells and whistles 
already
in place - just a matter of point and click to replicate one set of datasets on 
one
server to another one …

*Local* replication is a piece of cake today, if you have the hardware.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

Hi!

> Am 01.05.2019 um 02:14 schrieb Michelle Sullivan :
> And the irony is the FreeBSD policy to default to zfs on new installs using 
> the complete drive.. even when there is only one disk available and 
> regardless of the cpu or ram class...  with one usb stick I have around here 
> it attempted to use zfs on one of my laptops.

But *any* filesystem other than ZFS on a single disk and non-ECC memory is 
worse!

So what’s gained by defaulting back to UFS in these cases?

There’s the edge case of embedded/very low memory systems but people who
build these probably know what they are doing? And of course I use UFS in VMs
running on a host with ZFS … depending on whether I need the 
snapshot/replication
features in the guest or not.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

Some updates:

https://www.ixsystems.com/community/threads/nvme-problems-are-there-nightlies-based-on-12-stable-already.75685
https://jira.ixsystems.com/browse/NAS-101427

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

Hi!

> Am 15.04.2019 um 10:51 schrieb Patrick M. Hausen :
> Now, RELENG_12 kernel, 11.2-RELEASE userland:
> 
> root@hurz:/var/tmp # uname -a
> FreeBSD hurz 12.0-STABLE FreeBSD 12.0-STABLE r346220 GENERIC  amd64
> root@hurz:/var/tmp #  dd if=/dev/urandom of=hurz bs=10m
> 
> Result:
> 
> no problems, not with two of these jobs running in parallel, not with a zpool 
> scrub at the same time …

After they ran for half an hour I find these in /var/log/messages:

Apr 15 11:03:54 hurz kernel: nvme2: Missing interrupt
Apr 15 11:07:07 hurz kernel: nvme3: Missing interrupt
Apr 15 11:09:47 hurz kernel: nvme4: Missing interrupt

They are the only occurrences. The system does not seem to hang or otherwise
misbehave ...

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

> Am 15.04.2019 um 08:46 schrieb Patrick M. Hausen :
> So I’ll test RELENG_12 next. If that works, I can probably craft
> a FreeNAS 11.2 installation with a 12 kernel. I would be hesitating to run
> HEAD in production, though.

root@hurz:/var/tmp # uname -a
FreeBSD hurz 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 04:32:14 
UTC 2018 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
root@hurz:/var/tmp # dd if=/dev/urandom of=hurz bs=10m

Result:

Apr 15 09:56:07 hurz kernel: nvme4: resetting controller
Apr 15 09:56:07 hurz kernel: nvme3: resetting controller
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:126 nsid:1 lba:188361216 
len:208
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 cid:126 
cdw0:0
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:127 nsid:1 lba:188368784 
len:64
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 cid:127 
cdw0:0
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:125 nsid:1 lba:188371408 
len:48
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 cid:125 
cdw0:0
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:124 nsid:1 lba:188371456 
len:16
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 cid:124 
cdw0:0
[…]


Now, RELENG_12 kernel, 11.2-RELEASE userland:

root@hurz:/var/tmp # uname -a
FreeBSD hurz 12.0-STABLE FreeBSD 12.0-STABLE r346220 GENERIC  amd64
root@hurz:/var/tmp #  dd if=/dev/urandom of=hurz bs=10m

Result:

no problems, not with two of these jobs running in parallel, not with a zpool 
scrub at the same time …


I uploaded a complete dmesg of the system running RELENG_12:
https://cloud.hausen.com/s/5dRMsewCtDFHRYA

Is there anything else I should send? pciconf, nvmecontrol …?

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

Hi!

> Am 14.04.2019 um 23:33 schrieb Patrick M. Hausen :
> Since the system runs well with RELENG_11 and only 4 drives
> and there is this question about the cabling and shared resources
> I will try to set up a system with 5 drives, each of them *without*
> another one in a „pair“ sharing the same MB connector.

So much for that theory: with 5 drives arranged in that way I get the
errors even during installation.

https://cloud.hausen.com/s/2myrX2Jr3fgLWGj
https://cloud.hausen.com/s/yryckgp56sH2CRe

So I’ll test RELENG_12 next. If that works, I can probably craft
a FreeNAS 11.2 installation with a 12 kernel. I would be hesitating to run
HEAD in production, though.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

Alright ...

> Am 13.04.2019 um 02:37 schrieb Warner Losh :
> > There's been some minor improvements in -current here. Any chance you could 
> > experimentally try that with this test? You won't get as many I/O abort 
> > errors (since we don't print those), and we have a few more workarounds for 
> > the reset path (though honestly, it's still kinda stinky).
> 
> HEAD or RELENG_12, too?
> 
> HEAD is preferred, but any recent snapshot will do.

I could not reproduce the problem for a couple of hours with
an otherwise identical system but only 4 of these Intel drives.

Now the same test system with 6 drives just as our FreeNAS boxes
- instantly reproducible.

I’ll upgrade to HEAD and see if that changes anything.

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

Hi Warner,

thanks for taking the time again …

> OK. This means that whatever I/O workload we've done has caused the NVME card 
> to stop responding for 30s, so we reset it.

I figured as much ;-)

> So it's an intel card.

Yes - I already added this info several times. 6 of them, 2.5“ NVME „disk 
drives“.

> OK. That suggests Intel has a problem with their firmware.

I came across this one:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713

Is it more probable that Intel has got buggy firmware here than that
„we“ are missing interrupts?

The mainboard is the Supermicro H11SSW-NT. Two NVME drive bays share
a connector on the mainboard:

NVMe Ports ( NVMe 0~7, 10, 11, 14, 15)

The H11SSW-iN/NT has tweleve (12) NVMe ports (2 ports per 1 Slim SAS 
connector) on the motherboard.
These ports provide high-speed, low-latency PCI-E 3.0 x4 connections 
directly from the CPU to NVMe Solid
State (SSD) drives. This greatly increases SSD data- throughput 
performance and significantly reduces PCI-E
latency by simplifying driver/software requirements resulting from 
direct PCI-E interface from the CPU to the NVMe SSD drives.

Is this purely mechanical or do two drives share PCI-E resources? Which would 
explain
why the problems always come in pairs (nvme6 and nvme7, for example).

This afternoon I set up a system with 4 drives and I was not able to reproduce 
the problem.
(We just got 3 more machines which happened to have 4 drives each and no M.2 
directly
on the mainboard).
I will change the config to 6 drives like with the two FreeNAS systems in our 
data center.

> [… nda(4) ...]
> I doubt that would have any effect. They both throw as much I/O onto the card 
> as possible in the default config.

I found out - yes, just the same.

> There's been some minor improvements in -current here. Any chance you could 
> experimentally try that with this test? You won't get as many I/O abort 
> errors (since we don't print those), and we have a few more workarounds for 
> the reset path (though honestly, it's still kinda stinky).

HEAD or RELENG_12, too?

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o and controller resets

[Patrick M. Hausen]

Hi all,

my problems seem not to be TRIM related after all … and I can now
quickly reproduce it.

=
root@freenas01[~]# sysctl vfs.zfs.trim.enabled
vfs.zfs.trim.enabled: 0
=
root@freenas01[~]# cd /mnt/zfs
root@freenas01[/mnt/zfs]# dd if=/dev/urandom of=hurz bs=10m
^C — system freezes temporarily
=
Apr 12 13:42:16 freenas01 nvme6: resetting controller
Apr 12 13:42:16 freenas01 nvme6: aborting outstanding i/o
Apr 12 13:42:16 freenas01 nvme6: WRITE sqid:1 cid:117 nsid:1 lba:981825104 
len:176
Apr 12 13:42:16 freenas01 nvme6: ABORTED - BY REQUEST (00/07) sqid:1 cid:117 
cdw0:0
Apr 12 13:42:49 freenas01 nvme6: resetting controller
Apr 12 13:42:50 freenas01 nvme6: aborting outstanding i/o
Apr 12 13:42:50 freenas01 nvme6: WRITE sqid:1 cid:127 nsid:1 lba:984107936 
len:96
Apr 12 13:42:50 freenas01 nvme6: ABORTED - BY REQUEST (00/07) sqid:1 cid:127 
cdw0:0
Apr 12 13:43:35 freenas01 nvme6: resetting controller
Apr 12 13:43:35 freenas01 nvme6: aborting outstanding i/o
Apr 12 13:43:35 freenas01 nvme6: WRITE sqid:1 cid:112 nsid:1 lba:976172032 
len:176
Apr 12 13:43:35 freenas01 nvme6: ABORTED - BY REQUEST (00/07) sqid:1 cid:112 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: resetting controller
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:111 nsid:1 lba:976199176 
len:248
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:111 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:102 nsid:1 lba:976199432 
len:248
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:102 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:112 nsid:1 lba:976199680 len:8
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:112 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:105 nsid:1 lba:976199752 
len:64
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:105 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:122 nsid:1 lba:976199816 
len:64
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:122 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:103 nsid:1 lba:976199688 
len:64
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:103 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:126 nsid:1 lba:976200136 
len:56
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:126 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:106 nsid:1 lba:976200192 len:8
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:106 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:107 nsid:1 lba:976200200 
len:64
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:107 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:127 nsid:1 lba:976200264 
len:64
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:127 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:113 nsid:1 lba:976200328 
len:120
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:113 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:108 nsid:1 lba:976200448 
len:72
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:108 
cdw0:0
Apr 12 13:44:06 freenas01 nvme7: aborting outstanding i/o
Apr 12 13:44:06 freenas01 nvme7: WRITE sqid:1 cid:116 nsid:1 lba:976200520 
len:64
Apr 12 13:44:06 freenas01 nvme7: ABORTED - BY REQUEST (00/07) sqid:1 cid:116 
cdw0:0
=
root@freenas01[~]# nvmecontrol identify nvme6
Controller Capabilities/Features

Vendor ID:  8086
Subsystem Vendor ID:8086
Serial Number:  BTLJ90230EC61P0FGN
Model Number:   INTEL SSDPE2KX010T8
Firmware Version:   VDV10131
Recommended Arb Burst:  0
IEEE OUI Identifier:e4 d2 5c
Multi-Interface Cap:00
Max Data Transfer Size: 131072
Controller ID:  0x00

Admin Command Set Attributes

Security Send/Receive:   Not Supported
Format NVM:  Supported
Firmware Activate/Download:  Supported
Namespace Managment: Supported
Abort Command Limit: 4
Async Event Request Limit:   4
Number of Firmware Slots:1
Firmware Slot 1 Read-Only:   No
Per-Namespace SMART Log: 

Re: Rare NVME related freeze at boot (was: Re: NVME aborting outstanding i/o)

[Patrick M. Hausen]

Hi!

> Am 05.04.2019 um 16:36 schrieb Warner Losh :
> What normally comes after the nvme6 line in boot? Often times it's the next 
> thing after the last message that's the issue, not the last thing.

nvme7 ;-)

And I had hangs at nvme1, nvme3, … as well.

Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

Rare NVME related freeze at boot (was: Re: NVME aborting outstanding i/o)

[Patrick M. Hausen]

Hi all,

in addition to the aborted commands every dozen of system boots or so
(this order of magnitude) the kernel simply hangs during initialisation of
one of the NVME devices:

https://cloud.hausen.com/s/TxPTDFJwMe6sJr2

The particular device affected is not constant.

A power cycle fixes it, the system has not shown hangs/freezes during
multiuser operation, yet.


Any ideas?
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o

[Patrick M. Hausen]

Hi all,

> Am 04.04.2019 um 17:11 schrieb Warner Losh :
> There's a request that was sent down to the drive. It took longer than 30s to 
> respond. One of them, at least, was a trim request.
> […]

Thanks for the explanation.

This further explains why I was seeing a lot more of those and the system
occasionally froze for a couple of seconds after I increased these:

vfs.zfs.vdev.async_write_max_active: 10
vfs.zfs.vdev.async_read_max_active: 3
vfs.zfs.vdev.sync_write_max_active: 10
vfs.zfs.vdev.sync_read_max_active: 10

as recommended by Allan Jude reasoning that NVME devices could work on
up to 64 requests in parallel. I have since reverted that change and I am
running with the defaults.

If I understand correctly, this:

> hw.nvme.per_cpu_io_queues=0

essentially limits the rate at which the system throws commands at the devices. 
Correct?

So it’s not a real fix and there’s nothing fundamentally wrong with the per CPU 
queue or
interrupt implementation. I will look into new firmware for my Intel devices and
try tweaking the vfs.zfs.vdev.trim_max_active and related parameters.

Out of curiosity: what happens if I disable TRIM? My knowledge is rather 
superficial
and I just filed that under „TRIM is absolutely essential lest performance will
suffer severely and your devices die - plus bad karma, of course …“ ;-)

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o

[Patrick M. Hausen]

> Am 04.04.2019 um 16:51 schrieb Chuck Tuffli :
> nvmecontrol identify nvme7

Controller Capabilities/Features

Vendor ID:  8086
Subsystem Vendor ID:8086
Serial Number:  BTLJ90230F1R1P0FGN
Model Number:   INTEL SSDPE2KX010T8
Firmware Version:   VDV10131
Recommended Arb Burst:  0
IEEE OUI Identifier:e4 d2 5c
Multi-Interface Cap:00
Max Data Transfer Size: 131072
Controller ID:  0x00

The server is a Supermicro AS-1113S-WN10RT


Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: NVME aborting outstanding i/o

[Patrick M. Hausen]

Hi,

> Am 04.04.2019 um 10:37 schrieb Patrick M. Hausen :
> But:
> 
>   root@freenas01[~]# sysctl hw.nvme.per_cpu_io_queues
>   sysctl: unknown oid 'hw.nvme.per_cpu_io_queues'
>   root@freenas01[~]# sysctl hw.nvme.min_cpus_per_ioq
>   sysctl: unknown oid 'hw.nvme.min_cpus_per_ioq'
>   root@freenas01[~]# sysctl hw.nvme.force_intx
>   sysctl: unknown oid 'hw.nvme.force_intx'

Looks like these can be set via loader.conf and reboot although
they are not visible in the running system. Even when set they
are not visible afterwards ...

hw.nvme.per_cpu_io_queues=0

seems to cure the NVME errors. I’m still curious about the root
problem here, bit at least I can now continue to use the machines
for some real loads.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

NVME aborting outstanding i/o

[Patrick M. Hausen]

Hi all,

I’m currently doing some load tests/burn in for two new servers.
These feature all NVME SSDs and run FreeNAS, i.e. FreeBSD 11.2-STABLE.

pcib17:  at device 3.2 numa-domain 1 on pci15
pcib17: [GIANT-LOCKED]
pci17:  numa-domain 1 on pcib17
nvme7:  mem 0xeca1-0xeca13fff at device 0.0 
numa-domain 1 on pci17

When putting some moderate i/o load on the system, the log fills with these
messages:

nvme7: aborting outstanding i/o
nvme7: DATASET MANAGEMENT sqid:41 cid:91 nsid:1
nvme7: ABORTED - BY REQUEST (00/07) sqid:41 cid:91 cdw0:0

There has been some discussion of this on on the iX Systems forum as well as 
various
FreeBSD media and one person suggested setting:

hw.nvme.per_cpu_io_queues=0


This is where I need some help now. This is from the manpage for nvme(4):

--
To force a single I/O queue pair shared by all CPUs, set the following
tunable value in loader.conf(5):

  hw.nvme.per_cpu_io_queues=0

To assign more than one CPU per I/O queue pair, thereby reducing the
number of MSI-X vectors consumed by the device, set the following tunable
value in loader.conf(5):

  hw.nvme.min_cpus_per_ioq=X

To force legacy interrupts for all nvme driver instances, set the
following tunable value in loader.conf(5):

  hw.nvme.force_intx=1

Note that use of INTx implies disabling of per-CPU I/O queue pairs.
--

But:

root@freenas01[~]# sysctl hw.nvme.per_cpu_io_queues
sysctl: unknown oid 'hw.nvme.per_cpu_io_queues'
root@freenas01[~]# sysctl hw.nvme.min_cpus_per_ioq
sysctl: unknown oid 'hw.nvme.min_cpus_per_ioq'
root@freenas01[~]# sysctl hw.nvme.force_intx
sysctl: unknown oid 'hw.nvme.force_intx'


Where do I go from here?

Thanks!
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling
___
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: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

[Patrick M. Hausen]

Hello,

I don’t know if this is related or not, but when I compile
the Nextcloud client port

https://svnweb.freebsd.org/ports/head/deskutils/nextcloudclient/

on 11.2 by setting

DEFAULT_VERSIONS+=ssl=openssl111

it dumps core, too.

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Binary update to -STABLE? And if so, what do I get?

[Patrick M. Hausen]

Good morning,

> Am 14.02.2019 um 19:11 schrieb Kevin Oberman :
> Far and away the biggest is the requirement to build from sources. It's not
> a big deal for me, but if I still had many systems to deal with, that would
> be a pain.
> […]
> The bottom line is that the only real reasons I see for not running stable
> is the lack of binary updates, and issues with systems being slightly out
> of sync if all are not updated to the same SVN revision at all times. Those
> are very big reasons for many.

We build from sources centrally, then zfs send/receive /usr/src and
/usr/obj to all of the machines, then just do the install(kernel|world)
part on all of them.

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: issue upgradning src

[Patrick M. Hausen]

Hi!

> Am 05.12.2018 um 16:45 schrieb Maciej Jan Broniarz :
> I want to upgrade my 12.0-ALPHA8 to the latest release, yet I am unable to 
> update from source:
> [...]
> #freebsd-update fetch

freebsd-update upgrade -r 12.0-RC3

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

Memory error logged in /var/log/messages

[Patrick M. Hausen]

Hi all,

one of our production servers, 11.2p3 is logging this every couple of minutes:

Nov 19 11:48:06 ph002 kernel: MCA: CPU 0 COR (5) OVER MS channel 3 memory error
Nov 19 11:48:06 ph002 kernel: MCA: Address 0x1f709a48c0
Nov 19 11:48:06 ph002 kernel: MCA: Misc 0x9001040188c
Nov 19 11:48:06 ph002 kernel: MCA: Bank 12, Status 0xcc00010c000800c3
Nov 19 11:48:06 ph002 kernel: MCA: Global Cap 0x07000c16, Status 
0x
Nov 19 11:48:06 ph002 kernel: MCA: Vendor "GenuineIntel", ID 0x406f1, APIC ID 0

Address and core varies but it is always bank 12.

It seems like applications are unaffected, we use, of course ECC memory.

Is the OS able to work around these errors and just notifies us or is in-memory
data already getting corrupted?

I’m at a bit of a loss identifying which DIMM might be the cause so I contacted 
Supermicro
support. They answered:

> We can't really answer this, we do not know how various OS's map the memory 
> slots.
> Our advise is always to look at IPMI, but if that doesn't log any issues then 
> we're not sure you're looking at a hardware issue.
> 
> But assuming the OS looks at the ranks of a module as a bank and you use dual 
> rank memory then it should logically point at DIMMC2.

They are right on the IPMI (I told them when opening the case) - there’s 
nothing at all
in the event log.

Can they be correct that it might not even be a hardware issue?
If not how can I be sure which DIMM is to blame? Spare parts are ready but I’d 
like to
have a rather short maintenance break outside regular business hours.

I’ll attach a dmesg.boot. HW is a X10DRW-NT mainboard, SYS-1028R-WTNRT server 
platform.

Thanks for any hints,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling
Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.2-RELEASE-p3 #4 r338821: Thu Sep 20 12:26:41 CEST 2018
r...@backupr05.karlsruhe.punkt.de:/usr/obj/usr/src/sys/VIMAGE amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 
6.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Xeon(R) CPU E5-2630L v4 @ 1.80GHz (1800.04-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
  
Features=0xbfebfbff
  
Features2=0x7ffefbff
  AMD Features=0x2c100800
  AMD Features2=0x121
  Structured Extended 
Features=0x21cbfbb
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 274873712640 (262140 MB)
avail memory = 267225935872 (254846 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 40 CPUs
FreeBSD/SMP: 2 package(s) x 10 core(s) x 2 hardware threads
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 24-47 on motherboard
ioapic2  irqs 48-71 on motherboard
SMP: AP CPU #1 Launched!
SMP: AP CPU #29 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #35 Launched!
SMP: AP CPU #17 Launched!
SMP: AP CPU #24 Launched!
SMP: AP CPU #14 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #19 Launched!
SMP: AP CPU #11 Launched!
SMP: AP CPU #33 Launched!
SMP: AP CPU #12 Launched!
SMP: AP CPU #26 Launched!
SMP: AP CPU #25 Launched!
SMP: AP CPU #18 Launched!
SMP: AP CPU #23 Launched!
SMP: AP CPU #21 Launched!
SMP: AP CPU #34 Launched!
SMP: AP CPU #39 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #30 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #37 Launched!
SMP: AP CPU #13 Launched!
SMP: AP CPU #27 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #36 Launched!
SMP: AP CPU #28 Launched!
SMP: AP CPU #38 Launched!
SMP: AP CPU #22 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #15 Launched!
SMP: AP CPU #20 Launched!
SMP: AP CPU #32 Launched!
SMP: AP CPU #16 Launched!
SMP: AP CPU #31 Launched!
SMP: AP CPU #10 Launched!
SMP: AP CPU #9 Launched!
SMP: AP CPU #8 Launched!
Timecounter "TSC" frequency 1800041380 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x8102d580, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
vtvga0:  on motherboard
cryptosoft0:  on motherboard
acpi0: <> on motherboard
acpi0: Power Button (fixed)
cpu0:  numa-domain 0 on acpi0
cpu1:  numa-domain 0 on acpi0
cpu2:  numa-domain 0 on acpi0
cpu3:  numa-domain 0 on acpi0
cpu4:  numa-domain 0 on acpi0
cpu5:  numa-domain 0 on acpi0
cpu6:  numa-domain 0 on acpi0
cpu7:  numa-domain 0 on acpi0
cpu8:  numa-domain 0 on acpi0
cpu9:  numa-domain 0 on 

Re: ctld(8) 11.2-release lockup with w2k16 [Was: Re: ctld(8), multiple 'portal-group' on same socket (individual 'discovery-auth-group' restrictions)]

[Patrick M. Hausen]

Hi, all,

> Am 25.08.2018 um 15:04 schrieb Harry Schmalzbauer :
> [...]
> This is with 11.2 release.
> It's a ESXi guest, which I used severla years with previous FreeBSD versions 
> without such massive iSCSI performance problems.
> 
> Using the same /dev/zvol with istgt(1) on the same 11.2-release VM also 
> solves the performance issue.
> 
> Is anybody using ctld(8) in production post 10.x? If so, without observing a 
> similar regression?

Unfortunately I cannot directly help you here. My only iSCSI target server is
still on 10.4 ...

But a suggestion:

Install the latest BETA of FreeNAS (11.2-BETA2), and try if that shows the same
problems. It's based on 11.2-STABLE. If not, the FreeNAS source tree and/or the
community might prove helpful. Heck, possibly their ctld config contains some
tuning your's doesn't. Communication is via forum instead of mailing lists,
but they are a generally kind bunch of guys.

I figure the number of actual users of iSCSI might be larger in that community.

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Spectre/Meltdown mitigation in 11.1-p10 bogging down zfs send/receive?

[Patrick M. Hausen]

Hi!

> Am 14.05.2018 um 17:35 schrieb Patrick M. Hausen <hau...@punkt.de>:
> Possibly we are on the wrong track altogether.

We were - please just forget it ...

ZFS scrub running during our activity ... everybody who already put
more than five minutes of thought into this deserves a beer at the next
EuroBSDCon ;-)

Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

Spectre/Meltdown mitigation in 11.1-p10 bogging down zfs send/receive?

[Patrick M. Hausen]

Hey guys,

as some might know we run our hosting products in ZFS and iocage based
jails. The backup concept relies on recurring local snapshots and a copy of
these on one (more planned) central storage server. The storage server
does essentially nothing but run zfs receive for each dataset on each
hosting node. 12x spinning rust and 128G of RAM. Lots of space ;-)

In preparation of rolling out (among other patches) the Meltdown and Spectre
mitigation fixes and microcode updates we already ran benchmarks that
measured our primary applications - the TYPO3 and Neos CMS. We did not
see much of an impact.

We updated that central storage system last Friday.

Today we provisioned a new server meaning a new hosting hardware and
a couple of jails on that one. The new system already has got all the latest
patches.
Part of the provisioning process is creating an initial snapshot of every 
dataset
and sending an initial copy to the storage server, so we can send nightly
incrementals.

That step took surprisingly long for the first of the new jails.

At least an order of magnitude, I cannot provide exact measurements yet,
because this is all part of rather complex Ansible task and it really caught us 
by
surprise.

We already received a couple of warnings from the Icinga service monitoring
the nightly replication runs - we still need to investigate this. We suspect 
they
ran slower than usual, too.

To narrow down the cause of the problem we tried this in chronological order:

1. storage server (receiving end):

Disable microcode update and hw.ibrs_active still slow
Disable vm.pmap.pti still 
slow

2. new jail host (sending end):

Disable both
fast
Re-enable microcode update and hw.ibrs_active   still fast
Re-enable vm.pmap.pti   still 
fast

Reboot as necessary, of course. And we double checked the current value
of the respective sysctls before running the tests.

That last step is *quite* unexpected, because it just does not make sense to me.


Does anybody know what impact the fixes, both PTI and IBRS are *expected*
to have on bulk zfs send/receive operations from/to two different hosts?

Possibly we are on the wrong track altogether. We suspected the CPU fixes
because of the general "what did you change last" approach ...


Thank you very much
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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

[Patrick M. Hausen]

Hi all,


> Am 08.05.2018 um 09:28 schrieb Andrea Brancatelli :
> out of curiosity, does any kind of GMirror-failure notification tools
> exist? 

http://soren.klintrup.dk/gmirror

We use it in production. Works as designed.

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: another question about zfs compression numbers

[Patrick M. Hausen]

Hi all,

> Am 04.04.2018 um 09:21 schrieb Eugene M. Zheganin :
> I'm just trying to understand these numbers:
> 
> file size is 232G, it's actual size on the lz4-compressed dataset is 18G, so 
> then why is the compressratio only 1.86x ? And why logicalused is 34.2G ? On 
> one hand, 34.2G exactlyfits to the 1.86x compresstaio, but still I don't get 
> it. dataset is on raidz, 3 spans across 5 disk vdevs, with total of 15 disks 
> if it matters:

A sparse file, possibly? The ZFS numbers refer to blocks. "Skipping" zeroes at 
the
VFS layer is not taken into account as fas as I know. Seriously, how should it?
If I'm not mistaken, ZFS will never get to see these empty blocks.

Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

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

IPv6 connectivity lost when combining if_bridge with a VLAN ...

[Patrick M. Hausen]

Hi all,

a follow-up to my discovery that certain chipsets don't support 100baseTX any 
more. ;-)

We use these servers as jail hosts and use if_bridge with VIMAGE and iocage a 
lot.
Our tried and true setup used to be like this:

-
sysctl net.link.bridge.inherit_mac=1
-
ifconfig_ixl0="up"
ifconfig_ixl1="up"

cloned_interfaces="bridge0 bridge1"
ifconfig_bridge0_name="inet0"
ifconfig_bridge1_name="mgmt0"

ifconfig_inet0="up addm ixl0"
ifconfig_inet0_alias0="inet /24"
ifconfig_inet0_ipv6="inet6 /64 auto_linklocal"

ifconfig_mgmt0="up addm ixl1"
ifconfig_mgmt0_alias0="inet /16"
ifconfig_mgmt0_ipv6="inet6 auto_linklocal"

defaultrouter=""
ipv6_defaultrouter="fe80::11%inet0"
-

So we use link-local v6 addresses for the default gateways in every VLAN.
The last octet in the GW address is simply the VLAN number ...


Now, because I had to run improvised wires to a different switch before
we get to upgrading the entire rack to Gbit connectivity we tried to use
a single cable and a trunk port:

-
sysctl net.link.bridge.inherit_mac=1
-
ifconfig_ixl0="up"

cloned_interfaces="vlan7 vlan11 bridge0 bridge1"

ifconfig_vlan7="up vlan 7 vlandev ixl0"
ifconfig_vlan11="up vlan 11 vlandev ixl0"

ifconfig_bridge0_name="inet0"
ifconfig_bridge1_name="mgmt0"

ifconfig_inet0="up addm vlan7"
ifconfig_inet0_alias0="inet /24"
ifconfig_inet0_ipv6="inet6 /64 auto_linklocal"

ifconfig_mgmt0="up addm vlan11"
ifconfig_mgmt0_alias0="inet /16"
ifconfig_mgmt0_ipv6="inet6 auto_linklocal"

defaultrouter=""
ipv6_defaultrouter="fe80::11%inet0"
-

Nothing overly fancy in my opinion, just an orthogonal combination
of technologies. In principle this seems to work, but ...

- IPv4 connectivity comes up reliably and stays up
- external IPv6 connectivity does not come up at reboot
- I can ping6 the default GW from the machine (link-local address)
- I can ping6 other machines in the same VLAN (global unicast)
- route -6 delete default; route -6 add default fe80::11%inet0 restores 
external connectivity
- external connectivity get's lost again after a couple of hours

Only IPv6 seems to be affected, not IPv4.

Any ideas? ;-)

Thanks,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 11.1 ixl(4) interface does not negotiate at 100 Mbit/s

[Patrick M. Hausen]

Hi all,

> Am 19.03.2018 um 17:37 schrieb Eric Joyner :
> I'm guessing these are 10G copper LOMs using X722; those don't support 100Mb 
> speeds.

Your guess is probably correct. Going to re-wire tomorrow.

Thanks, everyone.
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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.1 ixl(4) interface does not negotiate at 100 Mbit/s

[Patrick M. Hausen]

Hi all,

any ideas why a current RELENG_11_1 system with ixl(4)
onboard interfaces might not negotiate with a switch that
has only fast ethernet?

status: no carrier  on the host
line protocol is down (notconnect)  on the switch

dmesg:
https://imgur.com/9ri9is8


Thanks for any hints,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: iscsi target and VMware/esxi timeouts

[Patrick M. Hausen]

Hello,

> Am 14.11.2017 um 10:08 schrieb Daniel Braniss :
> 
> Hi,
> we are experimenting issues with several esxi’s servers that use freebsd 10.2 
> stable as a iscsi target.
> ie:
> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 
> (iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 
> seconds; dropping connection
> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 
> (iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 
> seconds; dropping connection
> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.205 
> (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 
> seconds; dropping connection
> Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.203 
> (iqn.1998-01.com.vmware:pe-13-60e87d06): no ping reply (NOP-Out) after 5 
> seconds; dropping connection
> Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.205 
> (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 
> seconds; dropping connection
> 
> these are 3 different esxis that almost at the same time the target looses 
> connection to the initiators.
> at the moment most ‘clients’  recover from the scsi error, but older freebsds 
> don’t.
> 
> in any case, increasing the timeout is not helping.
> 
> any clues are welcome :-)
> 
> over the weekend i’m planning to upgrade the target to 11.1 and take for the 
> hills.

Are you using istgt or ctld?

We have did experience similar occasional problems with the former
but never with the latter.

Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: ABI changes within stable branch

[Patrick M. Hausen]

Morning,

> Am 20.09.2017 um 19:27 schrieb Mark Linimon :
> 
> On Tue, Sep 19, 2017 at 10:15:32AM +0200, Kurt Jaeger wrote:
>> A pointer to the official policy would be nice 8-}
> 
> 3rd paragraph of:
> 
>  http://www.freebsd.org/portmgr/policies_eol.html

One comment: it's easy to overlook the implications of the word "supported" in

"Package builds will use the oldest supported minor release within each 
major branch ..."

Thanks for the link.

Patrick
--
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling


signature.asc
Description: Message signed with OpenPGP

Re: ABI changes within stable branch

[Patrick M. Hausen]

Hi!

> Am 20.09.2017 um 04:09 schrieb Aristedes Maniatis :
> At the very least I need to remember to keep poudriere on the x.0 release 
> even after it is EOL,
> until every one of my servers has been upgraded

Not necessarily. You can run build jails with lower OS versions on an up-to-date
poudriere system.

In your specific case just build 11.0 and 11.1 packages (until 11.0 breaks ;-) 
and
use the appropriate package repos on your various servers.

You *cannot* build 11.1 packages on an 11.0 poudriere, at least not reliably.

HTH,
Patrick
--
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling


signature.asc
Description: Message signed with OpenPGP

Re: ABI changes within stable branch

[Patrick M. Hausen]

Hi all,

> Am 19.09.2017 um 10:32 schrieb Aristedes Maniatis :
> Then we have a problem since 
> https://pkg.freebsd.org/freebsd:11:x86:64/latest/All/ has been built on 11.1, 
> not on 11.0 (I just tested it with csync2 which I know fails). Packages there 
> may fail to run on 11.0, but there is no clear indication, just random 
> failures at runtime.
> 
> Maybe we'd need specific 11.0, 11.1, 11.2 releases instead of quarterly 
> releases?

This is precisely what we do on our own poudriere - build the quarterly ports 
branches
on various FreeBSD release versions.

Patrick


signature.asc
Description: Message signed with OpenPGP

Re: Bridged networking regression in 11.0?

[Patrick M. Hausen]

OK, guys, more replying to myswlf ;-)

> Am 30.08.2017 um 12:04 schrieb Patrick M. Hausen <hau...@punkt.de>:
> 
> Hi, all,
> 
>> Am 30.08.2017 um 09:29 schrieb Patrick M. Hausen <hau...@punkt.de>:
>> one of the systems on which we run our jail based "proServer" product failed
>> in a very odd way for the second time with a couple of days between the two
>> incidents.
>> [...]
> 
> We found this open bug:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
> [...]

To me it looks like not much changed in if_bridge.c from RELENG_10_3
to RELENG_11_0 ...

https://svnweb.freebsd.org/base/releng/11.0/sys/net/if_bridge.c?view=diff=303975=296373_format=h

The revisions are the topmost entries in
https://svnweb.freebsd.org/base/releng/11.0/sys/net/if_bridge.c
https://svnweb.freebsd.org/base/releng/10.3/sys/net/if_bridge.c
respectively. Is this the correct/best way to answer the question
what changed?

The only real change relates to IF teardown and we did not change anything
(stop/restart jails) when the outages occured.

So ... the network interface driver? Probably?

ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.1.13-k> port 
0x6020-0x603f mem 0xc7c0-0xc7df,0xc7e04000-0xc7e07fff irq 26 at device 
0.0 numa-domain 0 on pci3
ix0: Using MSIX interrupts with 9 vectors
ix0: Ethernet address: 0c:c4:7a:34:ec:ba
ix0: PCI Express Bus: Speed 5.0GT/s Width x8
ix0: netmap queues/slots: TX 8/2048, RX 8/2048

Patrick



signature.asc
Description: Message signed with OpenPGP

Re: Bridged networking regression in 11.0?

[Patrick M. Hausen]

Hi, all,

> Am 30.08.2017 um 09:29 schrieb Patrick M. Hausen <hau...@punkt.de>:
> one of the systems on which we run our jail based "proServer" product failed
> in a very odd way for the second time with a couple of days between the two
> incidents.
> [...]

We found this open bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606

What puzzles me is the fact that the original reporter
claims that ifconfig down/up fixes the problem temporarily
for him. Which in my case it didn't.

But possibly I should have down/up'ed *all* bridge members
not only the physical IF  ...

Patrick


signature.asc
Description: Message signed with OpenPGP

Bridged networking regression in 11.0?

[Patrick M. Hausen]

Hi, everyone,

one of the systems on which we run our jail based "proServer" product failed
in a very odd way for the second time with a couple of days between the two
incidents.

We run VIMAGE based jails (a lot) and bridge them with the physical interface
of the machine.

-
cloned_interfaces="bridge0 bridge1"

ifconfig_bridge0_name="inet0"
ifconfig_inet0="addm ix0 up"
ifconfig_inet0_alias0="inet 217.29.41.2/24"
ifconfig_inet0_ipv6="inet6 2a00:b580:8000:11:44e8:ab80:816:7869/64 
auto_linklocal"

ifconfig_bridge1_name="mgmt0"
ifconfig_mgmt0="addm ix1 up"
ifconfig_mgmt0_alias0="inet 10.5.105.7/16"
ifconfig_mgmt0_ipv6="inet6 auto_linklocal"
-

The rest is managed by iocage wich creates the needed epair(4) interfaces,
for some reason renames them to "vnetX" and adds them as members to
the bridge.

E.g.
-
[ry93@ph002 ~]$ ifconfig inet0
inet0: flags=8843 metric 0 mtu 1500
ether 02:50:51:fe:cc:00
inet6 fe80::50:51ff:fefe:cc00%inet0 prefixlen 64 scopeid 0x4
inet6 2a00:b580:8000:11:44e8:ab80:816:7869 prefixlen 64
inet 217.29.41.2 netmask 0xff00 broadcast 217.29.41.255
nd6 options=21
groups: bridge
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: vnet0:69 flags=143
ifmaxaddr 0 port 76 priority 128 path cost 2000
[... 50 vnet interfaces following ...]
member: ix0 flags=143
ifmaxaddr 0 port 1 priority 128 path cost 2000
-

When the system fails

- no jail is reachable from the outside via IP
- no jail is reachable from the host via IP
- the host itself is reachable just fine
- when we `iocage console` into a jail it can reach it's own IP addresses but 
nothing "outside"


I tried

- ifconfig ix0 down; ifconfig ix0 up
- ifconfig inet0 down; ifconfig inet0 up # aka bridge0
- iocage stop ; iocage start 

The latter deletes the epair instance connected to the jail and creates a fresh 
one,
then adds it to the bridge. No change in connectivity ... the start of the jail 
takes
"forever" because various processes hang waiting DNS timeouts (no networking ;-)

There's nothing in /var/log/messages or the dmesg buffer that relates to 
networking!
Rebooting the host system "fixes" the situation.


Now I'm well aware that this is too little information to draw some definite 
conclusions.
Hence my first question is: what should I do (commands) when the situation 
arises again
to gather more evidence?

Or maybe we are just lucky and there is a known problem? Yes, I know VIMAGE is 
still
considered experimental. We have been running this in production for months and 
it
looks like it could be related to upgrading host and jails from 10.3 to 11.0 
*or* switching
the old shell based iocage for Brandon's new python based version.
I cannot rule out iocage, yet it's not very probable - this is not a Docker 
like running service
or network component, after all. Once the jails are up, iocage is done ...

An then there's the chance that it is something with the ix driver and the way 
we use the
interface ... so for completeness:
-
ix0:  port 
0x6020-0x603f mem 0xc7c0-0xc7df,0xc7e04000-0xc7e07fff irq 26 at device 
0.0 numa-domain 0 on pci3
ix0: Using MSIX interrupts with 9 vectors
ix0: Ethernet address: 0c:c4:7a:34:ec:ba
ix0: PCI Express Bus: Speed 5.0GT/s Width x8
ix0: netmap queues/slots: TX 8/2048, RX 8/2048
ix0: promiscuous mode enabled
ix0: link state changed to UP
-


As usual thanks for any hints,
Patrick


signature.asc
Description: Message signed with OpenPGP

Re: recommendations for file server based zfs appliance

[Patrick M. Hausen]

Hi Stefan,

> Am 18.08.2017 um 14:35 schrieb Stefan Hagen :
>> What do you mean by "JBOD support"? Disable RAID in the systems BIOS
>> setup, put ZFS on AHCI drives ...
> 
> Activating JBOD deactivates the B120i raid controller. Unfortnately the 
> temperature sensor
> is somehow controlled by the raid controller. So enabling JBOD technically 
> works, but the
> machine is a lot louder than with enabled raid. As a workaround I've built 4 
> raid arrays with one disk each.
> 
> It works, but it doesn't feel right to me.

Weird - the machine seems rather quiet to me, but it's in a separate
room with the laser printers and no one actually working there.

I don't know how to measure noise, unfortunately. I have another
Gen8 at my wife's office for their not-for-profit organisation.
Quiet as a mouse with FreeNAS 11. This time two also very quiet
(most of the time) computer based office desks in that room.

My machine here at my office:

root@filer:~ # ipmitool sensor
UID Light| 0x0| discrete   | 0x0180| na| na| na 
   | na| na| na
Health LED   | 0x0| discrete   | 0x0180| na| na| na 
   | na| na| na
01-Inlet Ambient | 28.000 | degrees C  | ok| na| na| na 
   | na| 42.000| 46.000
02-CPU   | 40.000 | degrees C  | ok| na| na| na 
   | na| 70.000| na
03-P1 DIMM 1-2   | 42.000 | degrees C  | ok| na| na| na 
   | na| 87.000| na
04-HD Max| na || na| na| na| na 
   | na| 60.000| na
05-Chipset   | 63.000 | degrees C  | ok| na| na| na 
   | na| 105.000   | na
06-Chipset Zone  | 48.000 | degrees C  | ok| na| na| na 
   | na| 68.000| 73.000
07-VR P1 Zone| 52.000 | degrees C  | ok| na| na| na 
   | na| 88.000| 93.000
08-Supercap Max  | na || na| na| na| na 
   | na| 65.000| na
09-iLO Zone  | 47.000 | degrees C  | ok| na| na| na 
   | na| 72.000| 77.000
10-PCI 1 | na || na| na| na| na 
   | na| 100.000   | na
11-PCI 1 Zone| 39.000 | degrees C  | ok| na| na| na 
   | na| 64.000| 69.000
12-Sys Exhaust   | 48.000 | degrees C  | ok| na| na| na 
   | na| 68.000| 73.000
13-LOM   | na || na| na| na| na 
   | na| 100.000   | na
Fan 1| 25.088 | percent| ok| na| na| na 
   | na| na| na
Power Supply 1   | 0x0| discrete   | 0x0180| na| na| na 
   | na| na| na
Memory   | 0x0| discrete   | 0x4080| na| na| na 
   | na| na| na

So, temperature sensor working, too. Or are you referring to the
*HDD* temperature? I never put disks to sleep in servers ...

Patrick


signature.asc
Description: Message signed with OpenPGP

Re: recommendations for file server based zfs appliance

[Patrick M. Hausen]

Hi!

> Am 18.08.2017 um 14:03 schrieb Stefan Hagen <freebsd-stable-l...@textmail.me>:
> 
> * Patrick M. Hausen wrote:
>>> Am 18.08.2017 um 11:19 schrieb Pete French <petefre...@ingresso.co.uk>:
>>> The HP micro servers work very well, and you can pick them up remakably 
>>> cheaply [...]
>>> Not sure about ECC memory support there though.
>> 
>> They do support ECC, no problem.
>> 
>> They are available with different CPU configurations from
>> as Pete said remarkably cheap Celeron D based systems
>> up to Xeon CPUs.
> 
> I've just sold my Microserver Gen8 (Xeon) just recently.
> It's a beautiful little machine, but I didn't make me happy in the long run.
> 
> Reasons:
> - Limited to 8GB Ram in total
> - Only 4 HDDs
> - JBOD support is not great
> - Harddrives are never going to sleep (not supported)
> 
> Installing FreeBSD was harder than expected. The machine refused to boot 
> FreeBSD
> from the internal non-raid SATA ports. I didn't try FreeNAS though.

smbios.system.product="ProLiant MicroServer Gen8"
CPU: Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz (2294.80-MHz K8-class CPU)

16 GB RAM, FreeBSD installation was no problem at all.

What do you mean by "JBOD support"? Disable RAID in the systems BIOS
setup, put ZFS on AHCI drives ...

ahci0:  port 
0x10c0-0x10c7,0x10c8-0x10cb,0x10d0-0x10d7,0x10d8-0x10db,0x10e0-0x10ff mem 
0xfacd-0xfacd07ff irq 17 at device 31.2 on pci0
ahci0: [ITHREAD]
ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier supported
ahcich0:  at channel 0 on ahci0
ahcich0: [ITHREAD]
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0:  ATA-8 SATA 3.x device
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)

This is our office file, print and mail server. No FreeNAS this time,
just plain FreeBSD.

Patrick


signature.asc
Description: Message signed with OpenPGP

Re: recommendations for file server based zfs appliance

[Patrick M. Hausen]

Hi all,

> Am 18.08.2017 um 13:58 schrieb Pete French :
> 
>> Maybe the folk that made hardware suggestions can post which net
>> interface(s) they are using and whether they are seeing driver issues?
> 
> The HP boxes have Broadcom ethernet controllers driven with the 'bge'
> driver, and thatw orks fine. I stick to Intel or Broadcom controllers for
> gigabit ether where I have a choice.

The Supermicro system I mentioned features 4 Intel igb(4) interfaces.
I bridge them to save an extra switch in my home network - works great.

BTW: this Supermicro box looks suspiciously similar to at least one
generation of the FreeNAS mini ...

Patrick


signature.asc
Description: Message signed with OpenPGP

Re: recommendations for file server based zfs appliance

[Patrick M. Hausen]

Hi, all,

> Am 18.08.2017 um 11:19 schrieb Pete French :
> The HP micro servers work very well, and you can pick them up remakably 
> cheaply [...]
> Not sure about ECC memory support there though.

They do support ECC, no problem.

They are available with different CPU configurations from
as Pete said remarkably cheap Celeron D based systems
up to Xeon CPUs.

If you want something that conserves power but still features
8 cores, Supermicro has got a small 8-core Atom based
system:
https://www.supermicro.nl/products/system/midtower/5028/SYS-5028A-TN4.cfm

I run this at home and I am really satisfied with it. ECC too, of course.
Capable of running VMs in bhyve ...

I'd suggest just using FreeNAS if you intend to build a file server.
And of course you can always order a preconfigured FreeNAS
mini from iX Systems.

HTH,
Patrick


signature.asc
Description: Message signed with OpenPGP

What is /dev/zfs?

[Patrick M. Hausen]

Hi, folks

any pointer to an explanation would be nice,
there seems to be no zfs(4) manpage ...

Reason for asking: I have a piece of software
that uses 14,000 ioctl() calls on that device during
one execution and I'm asking myself what it tries
to do.

Thanks!
Patrick


signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

[Patrick M. Hausen]

Hello,

> Am 23.05.2017 um 23:10 schrieb jungle Boogie <jungleboog...@gmail.com>:
> 
> Hi Patrick,
> On 23 May 2017 at 05:52, Patrick M. Hausen <hau...@punkt.de> wrote:
>> Hi, all,
>> 
>> just for the record - today I published our own boxesat Hashicorp Atlas:
>> 
>>https://atlas.hashicorp.com/punktde
>> 
>> If you trust me enough, enjoy ;-)
>> 
>> FreeBSD 11.0p10 - we intend to publish updated ones
>> for every FreeBSD update.
>> 
> 
> Thanks for making this.
> 
> Using Windows 7 with VirtualBox version 5.1.22, the VM is in a
> continuous reboot.

My box?

> Are you not experiencing this?

Of course not. Vagrant 1.9.5, Virtualbox 5.1.22, Mac OS.
We are using this box daily ...

Patrick


signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

[Patrick M. Hausen]

Hi, all,

just for the record - today I published our own boxesat Hashicorp Atlas:

https://atlas.hashicorp.com/punktde

If you trust me enough, enjoy ;-)

FreeBSD 11.0p10 - we intend to publish updated ones
for every FreeBSD update.

Kind regards,
Patrick


signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD Vagrant Box Kernel Panic

[Patrick M. Hausen]

Hello,

> Am 10.05.2017 um 21:24 schrieb Robert Simmons :
> It appears that the maintainer of the boxes should create a
> 11.0-RELEASE-p10 box and revoke the -p1 box.

The official Hashicorp boxes have been invoking freebsd-update on startup
for a while, now. So every box automatically updates itself to the latest
patchlevel.

We have started to roll our own boxes, so I'm not perfectly up-to-date.

Patrick


signature.asc
Description: Message signed with OpenPGP

Kernel panic on production system - what now?

[Patrick M. Hausen]

Hi all,

Mar 24 02:39:36 ph001 kernel: kernel trap 12 with interrupts disabled
Mar 24 02:39:36 ph001 kernel: 
Mar 24 02:39:36 ph001 kernel: 
Mar 24 02:39:36 ph001 kernel: Fatal trap 12: page fault while in kernel mode
Mar 24 02:39:37 ph001 kernel: cpuid = 8; apic id = 08
Mar 24 02:39:37 ph001 kernel: fault virtual address = 0x0
Mar 24 02:39:37 ph001 kernel: fault code= supervisor read data, 
page not present
Mar 24 02:39:37 ph001 kernel: instruction pointer   = 
0x20:0x809a4330

I must admit that this is a "first" for me. So where do I go from here?
There is "stuff" in /var/crash that has got the right timestamps, it seems ...

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: boot1.efifat's FAT12 volume label prevents booting (some systems)

[Patrick M. Hausen]

Hi,

> Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer :
>> create the EFI boot volume like this?
>> 
>> gpart add -t efi -l efi -a 512k -s 512k 
>> newfs_msdos /dev/gpt/efi
>> mount_msdosfs /dev/gpt/efi /mnt
>> mkdir -p /mnt/efi/boot
>> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi
> 
> You are missing startup.nsh...
> See
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282

Care to elaborate? This is what we use in production - all
systems booting just fine ;-)

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: boot1.efifat's FAT12 volume label prevents booting (some systems)

[Patrick M. Hausen]

Hi, all,

> Am 06.11.2016 um 18:14 schrieb Dimitry Andric :
> 
> Please do, so it is not forgotten.  It is relatively easy to change the
> volume label, by editing sys/boot/efi/boot1/generate-fat.sh, and then
> regenerating the FAT templates.

Why use the pre-generated image at all when you can easily
create the EFI boot volume like this?

gpart add -t efi -l efi -a 512k -s 512k 
newfs_msdos /dev/gpt/efi
mount_msdosfs /dev/gpt/efi /mnt
mkdir -p /mnt/efi/boot
cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi
umount /mnt


Kind regards,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: boot0cfg on does not set default selection on gmirror device

[Patrick M. Hausen]

Hi, all,

> Am 24.10.2016 um 04:50 schrieb Ian Smith <smi...@nimnet.asn.au>:
> 
> On Sun, 23 Oct 2016 15:53:59 +0200, Patrick M. Hausen wrote:
> 
>> Actual reboot of this production machine in two weeks when we run our
>> regular updates. But I expect that to "just work".
> 
> Warner expected the existing boot0cfg code to "just work" too.  And it 
> does, except that the upgrades to it failed to include a method to fix 
> existing installations retrospectively!

If the boot0 code 2.0 was severely broken, don't you think we would
have noticed? ;-)

One more thing, I just checked: the machines for which it did work
all the time are indeed younger and all have the 2.0 bootcode.

Thanks for your help.
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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

[Patrick M. Hausen]

Hi, Ian,

> Am 22.10.2016 um 05:36 schrieb Ian Smith :
> [...]
> I wonder two things:
> 
> Do 'boot0cfg -v ada0' and 'boot0cfg -v ada1' both report the same?

OK, situation before I try to change anything:

root@hd45:~ # boot0cfg -v mirror/m0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada1
[...]
default_selection=F1 (Slice 1)


Now try to change it to F2 through the mirror device:

root@hd45:~ # boot0cfg -s 2 mirror/m0
# No error message or other indication that something went wrong!

root@hd45:~ # boot0cfg -v mirror/m0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada1
[...]
default_selection=F1 (Slice 1)


> Might it work properly if you upgraded the boot sectors to version 2, 
> which is what you should get if you reinstall from current boot0cfg, 
> presumably without touching the MBR data, but you'll have backups ..

Well ...

root@hd45:~ # boot0cfg -B mirror/m0
root@hd45:~ # boot0cfg -s 2 mirror/m0
root@hd45:~ # 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=2.0  drive=0x80  mask=0xf  ticks=182  bell=# (0x23)
options=packet,update,nosetdrv
volume serial ID b100-808f
default_selection=F2 (Slice 2)

root@hd45:~ # boot0cfg -v ada0
[...]
default_selection=F2 (Slice 2)

root@hd45:~ # boot0cfg -v ada1
[...]
default_selection=F2 (Slice 2)

Revert the change:

root@hd45:~ # boot0cfg -s 1 mirror/m0
root@hd45:~ # boot0cfg -v  mirror/m0
[...]
default_selection=F1 (Slice 1)


That did it! These machines have been in production for some time
starting with FreeBSD 8.x and have been upgraded via NanoBSD style
dd followed by reboot all the time up to 10.3, now. Hence I never touched
the bootcode.

Actual reboot of this production machine in two weeks when we run our
regular updates. But I expect that to "just work".

Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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

[Patrick M. Hausen]

Hi, Warner,

> Am 21.10.2016 um 20:25 schrieb Warner Losh :
> Can you give us the strace output?

amd64 - no strace. I need a hand here, what precisely do I need to enter?

> It looks like it is reading the current blocks, setting the options,
> and then writing it back to the device. If the write back fails, it
> opens the device with geom and sends either the bootcode verb to geom
> (for the PART (aka gpart)) case or the data for the MBR case. strace
> should show that clearly. There's nothing in dmesg, right? Try this
> again but set geom.debug_flags to 128 instead of 16. This will give a
> verbose error in dmesg if there's any errors from the control message.

I set the flag, then tried to change the slice from 1 to 2.
Result:

Dump of gctl request at 0xfe02392bd9e0:
  param:"class" [R5] = "PART"
  param:"arg0" [R10] = "mirror/m0"
  param:"verb" [R9] = "bootcode"
  param:"bootcode" [R512] =  fc 31 c0 8e c0 8e d8 8e d0 bc 00 7c 89 e6 
bf 00 06 b9 00 01 f3 a5 89 fd b1 08 f3 ab fe 45 f2 e9 00 8a f6 46 bb 20 75 08 
84 d2 78 07 80 4e bb 40 8a 56 ba 88 56 00 e8 fc 00 52 bb c2 07 31 d2 88 6f fc 
0f a3 56 bb 73 19 8a 07 bf 87 07 b1 03 f2 ae 74 0e b1 0b f2 ae 83 c7 09 8a 0d 
01 cf e8 c5 00 42 80 c3 10 73 d8 58 2c 7f 3a 06 75 04 72 05 48 74 0d 30 c0 04 
b0 88 46 b8 bf b2 07 e8 a6 00 be 7b 07 e8 b2 00 8a 56 b9 4e e8 8e 00 eb 05 b0 
07 e8 b0 00 30 e4 cd 1a 89 d7 03 7e bc b4 01 cd 16 75 0d 30 e4 cd 1a 39 fa 72 
f2 8a 46 b9 eb 16 30 e4 cd 16 88 e0 3c 1c 74 f1 2c 3b 3c 04 76 06 2c c7 3c 04 
77 c9 98 0f a3 46 0c 73 c2 88 46 b9 be 00 08 8a 14 89 f3 3c 04 9c 74 0a c0 e0 
04 05 be 07 93 c6 07 80 53 f6 46 bb 40 75 08 bb 00 06 b4 03 e8 59 00 5e 9d 75 
06 8a 56 b8 80 ea 30 bb 00 7c b4 02 e8 47 00 72 86 81 bf fe 01 55 aa 0f 85 7c 
ff be 85 07 e8 19 00 ff e3 b0 46 e8 24 00 b0 31 00 d0 eb 17 0f ab 56 0c be 78 
07 e8 eb ff 89 fe e8 03 00 be 85 07 ac a8 80 75 05 e8 04 00 eb f6 24 7f 53 bb 
07 00 b4 0e cd 10 5b c3 8a 74 01 8b 4c 02 b0 01 56 89 e7 f6 46 bb 80 74 13 66 
6a 00 66 ff 74 08 06 53 6a 01 6a 10 89 e6 48 80 cc 40 cd 13 89 fc 5e c3 20 20 
a0 0a 44 65 66 61 75 6c 74 3a a0 0d 8a 00 05 0f 01 06 07 0b 0c 0e 83 a5 a6 a9 
0d 0c 0b 0a 09 08 0a 0e 11 10 01 3f bf 44 4f d3 4c 69 6e 75 f8 46 72 65 65 42 
53 c4 66 bb 44 72 69 76 65 20 b1 01 80 8f b6 00 80 00 01 01 a5 fe ff fe c1 3e 
00 00 7e 86 fa 00 00 00 c1 ff a5 fe ff fc 3f c5 fa 00 7e 86 fa 00 00 00 c1 fd 
a5 fe ff 00 bd 4b f5 01 04 0e 7b 72 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 55 aa
  param:"flags" [R2] = "C"

root@hd45:~ # 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=F1 (Slice 1)

So again, no change.

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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

[Patrick M. Hausen]

Hi, all,

> Am 21.10.2016 um 16:41 schrieb Warner Losh :
> Any chance you can migrate to using gpart? Is boot0cfg still
> referenced in NanoBSD somewhere?

Not in NanoBSD but how would you configure boot0's default
slice with gpart? It doesn't pay attention to the "active" flag.
See Miroslav's mails for all the details.

gpart would only be an option if we did not use the FreeBSD
boot manager. But we need the "F1 ..., F2 ..." prompt, because
being able to roll back to the last known-good system via the
console is the entire point of using this NanoBSD setup.
There's a presentation on the EuroBSDCon 2010 page about
motivation and setup. Wonder who did that talk ... :-)))

BTW: thanks, Miroslav. As for your question: it does work on
the only two systems that use hardware RAID, yet have a
gmirror built of only a single component to get consistent
device names accross all servers.

I'm not quite sure if it works from time to time, I've come to
accept the "kern.geom.debugflags" dance.

I had opened a similar discussion years ago for 7.x/8.x and
I was told that geom was to provide an API for fdisk, boot0cfg
and friends to manipulate the MBR. Because back in the days
boot0cfg and fdisk both threw an error message when trying
to work on a whole-disk mirror.
I thought that was long solved - at least no error, anymore.
But it's still not working in 10.x.

Thanks to all and take care,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

boot0cfg on does not set default selection on gmirror device

[Patrick M. Hausen]

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.

gpart on the other hand works as expected:

root@hd45:/usr/local # gpart set -a active -i 1 mirror/m0
active set on mirror/m0s1
root@hd45:/usr/local # gpart show mirror/m0
=>63  1953525104  mirror/m0  MBR  (932G)
  63   16002 - free -  (7.8M)
   1606516418430  1  freebsd  [active]  (7.8G)
1643449516418430  2  freebsd  (7.8G)
32852925  1920667140  3  freebsd  (916G)
  19535200655102 - free -  (2.5M)

But the "active" flag alone is not enough to convince boot0 to actually boot 
that partition.

Additional info:

root@hd45:/usr/local # uname -a
FreeBSD hd45.hosting.punkt.de 10.3-RELEASE-p10 FreeBSD 10.3-RELEASE-p10 #0 
r306942: Mon Oct 10 10:29:14 UTC 2016 
root@:/usr/obj/nanobsd.hosting/usr/src/sys/GENERIC  amd64
root@hd45:/usr/local # gmirror status
 NameStatus  Components
mirror/m0  COMPLETE  ada0 (ACTIVE)
 ada1 (ACTIVE)


The only way to actually switch the boot0 default selection is:

root@hd45:/usr/local # sysctl kern.geom.debugflags=16
kern.geom.debugflags: 0 -> 16
root@hd45:/usr/local # boot0cfg -s 1 ada0
root@hd45:/usr/local # boot0cfg -s 1 ada1
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=F1 (Slice 1)


Any hints what's going on, here? Obviously it is possible to manipulate
the MBR of a gmirror device - as gpart proves. The boot0cfg pops up
since FreeBSD 8 when we started using a mirrored NanoBSD setup.


Thanks and kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: How to setup ethernet address and IPv4 address on interface?

[Patrick M. Hausen]

Hi, all,

> Am 29.06.2016 um 14:23 schrieb Slawa Olhovchenkov <s...@zxy.spb.ru>:
> 
> On Wed, Jun 29, 2016 at 02:13:59PM +0200, Patrick M. Hausen wrote:
> 
>> What about using a combination of
>> 
>> ifconfig_em1
>> ipv4_addrs_em1
>> 
>> in rc.conf?
> 
> What you mean? I am not rc.conf/network.subr hacker.

ifconfig_em1="ether 00:30:48:63:19:04"
ipv4_addrs_em1="192.168.2.1/24"

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: How to setup ethernet address and IPv4 address on interface?

[Patrick M. Hausen]

Hi!

> Am 29.06.2016 um 14:01 schrieb Slawa Olhovchenkov :
> I am need in one call, multiple commands not allways allowed.
> Using /etc/start_if.$IFNAME produce side effects and can mask errors
> in rc.conf.

What about using a combination of

ifconfig_em1
ipv4_addrs_em1

in rc.conf?

Kind regards
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

State of unionfs?

[Patrick M. Hausen]

Hi, all,

we were looking for a way to get overlay/copy-on-write mounts for
ZFS datasets to ease jail management.

Google turned up this old thread:
https://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009221.html

So, clearly in September 2010 mount_unionfs(8) was not supported
for ZFS datasets.

A quick check on a current RELENG-10.3 system showed that this has
changed .Union-mounting one dataset on top of another does indeed
work at a superficial glance.

Yet the manpage for mount_unionfs(8) still contains this disturbing
note:

BUGS
 THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
 AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM.  USE AT YOUR OWN
 RISK.  BEWARE OF DOG.  SLIPPERY WHEN WET.  BATTERIES NOT INCLUDED.

Is this still the case? Are there alternatives to our approach.

What we would like to implement is e.g. a standard pre-populated /etc for each
jail with only modified files being written to a separate per-jail dataset.
Much like NanoBSD does when populating the /etc mfs at boot.

While we can create a clone from a central snapshot for each jail, the
problem with this way is that we cannot exchange the base snapshot later,
e.g. after a major system update for the jail in question. Which is precisely
the intention in the first place ;-)

Thanks for any hints
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: OpenSSH changes between 10.2 and 10.3 ...

[Patrick M. Hausen]

Hi, all,

> Am 14.04.2016 um 12:20 schrieb Eugene Grosbein :
> 
> It does change for me. And helps. Make double sure you have added 
> KexAlgorithms
> to system wide defaults section of ssh_config and not after limiting "Host" 
> directive,
> or similar.

Thanks for that hint - much ado about nothing, sorry.
My statement went into "Host ..." section by accident.

Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

OpenSSH changes between 10.2 and 10.3 ...

[Patrick M. Hausen]

Hi, all,

minor problem/annoyance here:

root@noc:/etc/ssh # ssh admin@10.4.0.62
Unable to negotiate with 10.4.0.62 port 22: no matching key exchange method 
found. Their offer: diffie-hellman-group1-sha1,none
root@noc:/etc/ssh # uname -a
FreeBSD noc.pluspunkthosting.de 10.3-RELEASE FreeBSD 10.3-RELEASE #3: Wed Apr 
13 14:46:57 CEST 2016 
r...@noc.pluspunkthosting.de:/usr/obj/usr/src/sys/GENERIC  amd64

Of course I was able to find http://www.openssh.com/legacy.html myself.

FreeBSD 10.2 uses OpenSSH 6.6.x while 10.3 imported 7.2.
So far so good.

The recommended method from the document above works on the
command line:

ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 admin@10.4.0.62

But if I add

KexAlgorithms +diffie-hellman-group1-sha1

to /etc/ssh/ssh_config, that does not change anything. Oddly enough,
checking which algorithms are supported gives the same result
regardless of any configuration options:

root@noc:/etc/ssh # ssh -Q kex
diffie-hellman-group1-sha1
diffie-hellman-group14-sha1
diffie-hellman-group-exchange-sha1
diffie-hellman-group-exchange-sha256
ecdh-sha2-nistp256
ecdh-sha2-nistp384
ecdh-sha2-nistp521
curve25519-sha...@libssh.org

So, diffie-hellman-group1-sha1 is supported but not used unless
specified on the command line? And there is no way to override that
*globally*? This is an isolated management network with IPMI
interfaces - we won't be getting updates for all of these machines'
IPMI firmware ...

Am I stuck with writing shell aliases or putting the config in each and
every user's private ~/.ssh/config?

Thanks for any hints,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: Best practices for ZFS setup for a strictly SSD based system?

[Patrick M. Hausen]

Hi, all,

> Am 10.02.2016 um 11:15 schrieb krad :
> 
> Dont forget alignment and ashift. You may also want to test compression as 
> well. IF you have spare cpu cycles I would imagine the systems cpu will 
> handle it faster than any onboard ssd compression. Benchmarking would be of 
> use here though.

Correct. Just for the record: since 10.2 the FreeBSD installer does the right 
thing [tm].

ashift=12 and partitions are 1M aligned.

Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

Best practices for ZFS setup for a strictly SSD based system?

[Patrick M. Hausen]

Hi, all,

while there is quite a bit of documentation on how to improve ZFS performance
by using a combination of rotating disks and SSDs, I have not found much about
an SSD only setup.

We are planning to try a hosting server with 8 SATA SSDs with ZFS. Things I am
not at all sure about:

*   Does the recommended limit of 6 disks for a RAIDZ2 still
hold? 2x 4 disks is quite a bit of overhead, could I use all 8
in one vdev and get away with it?
(The maximum of 6 recommendation is in some old Sun doc)

*   Will e.g. MySQL still profit from residing on a mirror
instead of a RAIDZ2, even if all disks are SSDs?

*   Does a separate ZIL and/or ARC cache device still
make sense?

Any pointers or direct help greatly appreciated. Or should I take this to 
freebsd-fs@?

Thanks and best regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: Best practices for ZFS setup for a strictly SSD based system?

[Patrick M. Hausen]

Hi!

> Am 09.02.2016 um 17:32 schrieb Alan Somers :
> [...]
> http://blog.delphix.com/matt/2014/06/06/zfs-stripe-width/
> 
>> 
>> *   Will e.g. MySQL still profit from residing on a mirror
>>instead of a RAIDZ2, even if all disks are SSDs?
> 
> Yes, because a mirrored vdev has as many read IOPs as all of its disks
> combined.  So a RAID10 of SSDs will have many read IOPs indeed.

Ah … yes. Now I remember :)

> […]
> Will MySQL access its files in fixed-size records?  If so, you can set
> the recsize filesystem property accordingly.  If not, you should
> probably leave recsize at the default.  If you profile MySQL's disk
> accesses and determine that there is a dominant recordsize, then go
> ahead and set ZFS's recsize to the next highest power of two.
> 
> As usual, disable atime.

We already knew these. But thanks a lot for the vdev setup
hints! So it will be a mirror for OS and DB and a 4+2 raidz2
for the rest of the data.

Our MySQL zvols are currently set up like this:

DB files:
recordsize=16k
atime=off
primarycache=metadata

InnoDB log files:
recordsize=128k
(rest inherited from above)

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

NSS changes in releng/10.2?

[Patrick M. Hausen]

Hi, all,

I just upgraded an older system from 8.4 to 10.2 in a single go.
No unexpected problems, until I tried to use "su":

$ su -
su: Sorry

Well, I *am* a member of the wheel group:

$ id
uid=10093(ry93) gid=10001(intern) 
groups=10001(intern),0(wheel),10002(entwickler)

Hmmm ... we pull all this information from LDAP. My nsswitch.conf has always 
been:

group: files cache ldap
passwd: files cache ldap

Without the "compat" entries. 

Let's check the groups:

$ pw group show -a
wheel:*:0:
wheel:*:0:ry22,ry96,ry90,ry93 

Before the update the members were merged. The first line is coming from 
/etc/group,
the second from LDAP. I do have to remove the "root" member in /etc/group from 
wheel
on all systems for LDAP information to be merged in, even on the older systems. 
But for
some reason that seems not to be sufficient, anymore. 

If I put myself (ry93) in the file, everything works as expected.


Another way I tried was this for nsswitch.conf:

group: compat
group_compat: cache ldap

and then the traditional "+:*:0:" entry in /etc/group. The outcome of "id" and 
"su -" is
precisely the same as above. I am shown to be a member of group wheel, yet su
won't let me.

Any ideas?

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

PAM changes? (was: Re: NSS changes in releng/10.2?)

[Patrick M. Hausen]

Hi, all,

sorry for not trying this earlier and now replying to myself, but I'm
slowly making progress isolating the problem.

> Am 23.11.2015 um 15:42 schrieb Patrick M. Hausen <hau...@punkt.de>:
> 
> Hi, all,
> 
> I just upgraded an older system from 8.4 to 10.2 in a single go.
> No unexpected problems, until I tried to use "su":
> 
>   $ su -
>   su: Sorry
> 
> Well, I *am* a member of the wheel group:
> 
>   $ id
>   uid=10093(ry93) gid=10001(intern) 
> groups=10001(intern),0(wheel),10002(entwickler)
> 
> Hmmm ... we pull all this information from LDAP. My nsswitch.conf has always 
> been:
> 
>   group: files cache ldap
>   passwd: files cache ldap

And this part seems to be just as valid and working as before. I had the 
implicit
assumption that su(1) was using something like getgroups() to determine if I am
a member of "wheel" - which it doesn't. I even hacked up 5 lines of C to quickly
get my supplementary group list and lo and behold:

$ ./groups 
10002
0
10001

So, it is not NSS' or LDAP's fault.


I just looked at the source for su(1) and it looks like it uses PAM to check if
I am authorized to su to root:

   retcode = pam_authenticate(pamh, 0);
if (retcode != PAM_SUCCESS) {
syslog(LOG_AUTH|LOG_WARNING, "BAD SU %s to %s on %s",
username, user, mytty);
errx(1, "Sorry");

My /etc/pam.d/system looks like this:

--- system ---
#
# $FreeBSD: releng/10.2/etc/pam.d/system 197769 2009-10-05 09:28:54Z des $
#
# System-wide defaults
#

# auth
authsufficient  pam_opie.so no_warn no_fake_prompts
authrequisite   pam_opieaccess.so   no_warn allow_local
#auth   sufficient  pam_krb5.so no_warn try_first_pass
#auth   sufficient  pam_ssh.so  no_warn try_first_pass
authsufficient  /usr/local/lib/pam_ldap.so  no_warn 
try_first_pass
authrequiredpam_unix.so no_warn try_first_pass 
nullok

# account
#accountrequiredpam_krb5.so
account requiredpam_login_access.so
account required/usr/local/lib/pam_ldap.so  
ignore_authinfo_unavail ignore_unknown_user
account requiredpam_unix.so

# session
#sessionoptionalpam_ssh.so  want_agent
session requiredpam_lastlog.so  no_fail

# password
#password   sufficient  pam_krb5.so no_warn try_first_pass
passwordrequiredpam_unix.so no_warn try_first_pass
--

And /etc/pam.d/su like this:

--- su ---
#
# $FreeBSD: releng/10.2/etc/pam.d/su 219663 2011-03-15 10:13:35Z des $
#
# PAM configuration for the "su" service
#

# auth
authsufficient  pam_rootok.so   no_warn
authsufficient  pam_self.so no_warn
authrequisite   pam_group.sono_warn group=wheel 
root_only fail_safe ruser
authinclude system

# account
account include system

# session
session requiredpam_permit.so
--

Any changes that I missed on the way from 8.4 to 10.2? Unfortunately
I do not have an older 10.x system that runs with an Active Directory 
connection.
Only 8.4 ones - this one was the first to finally get updated to a current 
FreeBSD
version.

As I stated this PAM configuration works as intended on 8.4. I generated the
10.2 files above by running mergemaster.


Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

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

ZFS on labelled partitions (was: Re: LSI SAS2008 mps driver preferred firmware version)

[Patrick M. Hausen]

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?

Thanks,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: zfs, mc, mcview and files opening

[Patrick M. Hausen]

Hi, all,


> Am 10.11.2015 um 12:54 schrieb Eugene M. Zheganin :
> 
> Hi,
> 
> on 10.11.2015 15:05, Trond Endrestøl wrote:
>> I blame file(1), it's hopelessly slow. mcview uses file(1) to deduce
>> if it should just display the damn file or run the file through some
>> filter. Maybe an option in mc/mcview to disable the use of file(1) is
>> an acceptable compromise.
> Yeah, you seem to be right. /usr/bin/time -h file /var/log/maillog gives
> same time of 37-40 seconds to process the file.
> The main answer is now why file(1) is that slow ? I tested it on files
> of about same size and UFS - there's no lag at all.
> 
> Is it worth to report this in bugzilla ?

Could it be this problem you are experiencing?

http://freebsd.1045724.n5.nabble.com/file-1-command-very-slow-td6037309.html

Kind regards,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Swap Questions

[Patrick M. Hausen]

HI!

 Am 14.08.2015 um 15:15 schrieb Tim Daneliuk tun...@tundraware.com:
 
 I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that has
 512M of memory and 1G of swap partition.  I am seeing a ton of errors like
 this:
 
 [...]
 So, I added this to fstab (after creating /usr/swap0):

Did you create it with dd or just with touch? You need to create a
file that actually occupies the disk blocks with dd.

HTH
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
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: [SOLVED][BUG??] Unattended install using bsdinstall and ZFS

[Patrick M. Hausen]

Hi, Claus,

 Am 29.05.2015 um 19:17 schrieb Claus Andersen c...@wheel.dk:
 
 Hi!
 
 A quick re-cap: Want to do an unattended FreeBSD install using bsdinstall and 
 ZFS. I now have a workaround and consider crying wol^H^H^Hbug.
 
 The following minimal install script works as expected for UFS:
 [...]
 Hours later I have figure out the following which works(tm):
 
 install-zfs2.txt
   DISTRIBUTIONS=kernel.txz base.txz
   RELEASE=10.1
   export ZFSBOOT_DISKS=da0 da1
   export ZFSBOOT_VDEV_TYPE=mirror
   export nonInteractive=YES
 
   #!/bin/sh
   echo Ready for post installation damage...

Thanks for your detailled report. I can confirm your findings and I was able to 
do an unattended install using these settings:

DISTRIBUTIONS=base.txz doc.txz games.txz kernel.txz lib32.txz
INTERFACES=em0
export ZFSBOOT_DISKS=da0 da1
export ZFSBOOT_VDEV_TYPE=mirror
export ZFSBOOT_FORCE_4K_SECTORS=1
export ZFSBOOT_SWAP_SIZE=8g
export ZFSBOOT_SWAP_MIRROR=1
export ZFSBOOT_POOL_CREATE_OPTIONS=-O compress=lz4 -O checksum=fletcher4
export nonInteractive=YES

Yet, there are still 2 things that prevent a truly unattended installation. 
First, at least for me,
the installer alway displays a dialog with debug messages which needs to be 
explicitly
confirmed at the end of the installation. This is not the case if I use UFS. 
With UFS it just
reboots into the freshly installed system.

I could work around that one by explicitly calling reboot at the end of the 
shell script
part of installerconfig.

Second, if you do remote installation via IPMI and serial console over IP, the 
standard install
environment copied from CD calls this code in /etc/rc.local:

[...]
else
# Serial or other console
echo
echo Welcome to FreeBSD!
echo
echo Please choose the appropriate terminal type for your system.
echo Common console types are:
echoansi Standard ANSI terminal
echovt100VT100 or compatible terminal
echoxtermxterm terminal emulator (or compatible)
echocons25w  cons25w terminal
echo
echo -n Console type [vt100]: 
read TERM
TERM=${TERM:-vt100}
fi 

IMHO hardwiring this is not a good idea. Can be solved by simply commenting out 
the unwanted
parts, but this should be configurable in installerconfig. Currently it quite 
defeats the purpose of
*unattended* installations. At least I expect power on, get some coffee, login 
via ssh into newly
installed system ;-)

Kind regards
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: svn - but smaller?

[Patrick M. Hausen]

Hi,

Am 09.04.2013 um 17:05 schrieb Patrick M. Hausen hau...@punkt.de:
 PORTSSUPFILE= -b base/head -l /usr/ports

ports/head, of course.

Regards
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: svn - but smaller?

[Patrick M. Hausen]

Hi, all,

first a big big thank you to John an all others involved for all the work.

A bit more slowly than cvsup but definitely a lot more convenient than
using plain subversion. Part of the slow performance may be due to the
fact that there is no local German svn mirror, yet. I'll try with my own mirror
in a couple of days.

I immediately asked myself: how can I set this up so I can use make update
like I'm used to? SVN_UPDATE looks for a .svn directory, so it cannot work with
svnup.

Here's how:

root@gordon:/ # cat /etc/make.conf 
SUP_UPDATE= yes
SUP=/usr/local/bin/svnup
SUPHOST=svn0.us-east.freebsd.org
SUPFLAGS=
SUPFILE=-b base/stable/9 -l /usr/src
PORTSSUPFILE=   -b base/head -l /usr/ports

OK, this gives a big warning banner and it's an abuse of a mechanism intended
for another utility … but it works nonetheless ;-)

I therefore propose an extension to /usr/src/Makefile.inc1 like this:

update:
.if defined(SVNUP_UPDATE)
@echo --
@echo  Running ${SVNUP}
@echo --
.if defined(SVNUPFLAGS)
@${SVNUP} ${SVNUPFLAGS} -h ${SVNUPHOST}
.endif
…

Just a rough sketch - I can put more thought into this if nobody else is already
working on it.

Best regards,
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Poudriere questions

[Patrick M. Hausen]

Hi!

Am 21.02.2013 um 11:44 schrieb Guido Falsi m...@madpilot.net:
 Just to be sure, are you putting these lines in poudriere's make.conf for 
 your jail?

Yes, sure.

nanobsd# cat /usr/local/etc/poudriere.d/make.conf 
PROXY=on
PROXY_HTTP=on
SUEXEC=on
SUEXEC_DOCROOT=/var/apache
SUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log

I'm toying with just the Apache package at the moment. Once I get that built 
successfully
with my customizations, I will move on.

 make -DBATCH SUEXEC_DOCROOT=/var/apache 
 SUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log install


nanobsd# make -DBATCH SUEXEC_DOCROOT=/var/apache 
SUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log install
...
nanobsd# /usr/local/sbin/suexec -V
 -D AP_DOC_ROOT=/var/apache
 -D AP_GID_MIN=1000
 -D AP_HTTPD_USER=www
 -D AP_LOG_EXEC=/var/apache/GLOBAL/suexec_log
 -D AP_SAFE_PATH=/usr/local/bin:/usr/bin:/bin
 -D AP_UID_MIN=1000
 -D AP_USERDIR_SUFFIX=public_html

Yes! :-) OK, now now we are back to Poudriere again. Next I'll try to pass
the enable/disable stuff via OptionsNG and then put only the pathnames into
make.conf.

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Poudriere questions

[Patrick M. Hausen]

Hi, all,

Am 21.02.2013 um 09:54 schrieb Guido Falsi m...@madpilot.net:
 Sorry, I forgot to mention: no tabs. tabs have a spacial meaning to make.
 They mean a shell command follows and should be used only in make targets.

I *should* have guessed as much ;-) Of course tabs are syntactically relevant.
Thanks again.

Patrick-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Poudriere questions

[Patrick M. Hausen]

Hi, Guido,

hope you have a couple of more minutes ...

After the first failure with the make.conf syntax I just put the options in 
unconditionally,
to try if they end up in the final Apache package.

Nope:

Server version: Apache/2.2.23 (FreeBSD)
Server built:   Feb 21 2013 08:56:52
Server's Module Magic Number: 20051115:31
Server loaded:  APR 1.4.6, APR-Util 1.4.1
Compiled using: APR 1.4.6, APR-Util 1.4.1
Architecture:   64-bit
Server MPM: Prefork
  threaded: no
forked: yes (variable process count)
Server compiled with
 -D APACHE_MPM_DIR=server/mpm/prefork
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses disabled)
 -D APR_USE_FLOCK_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT=/usr/local
 -D SUEXEC_BIN=/usr/local/bin/suexec
 -D DEFAULT_PIDLOG=/var/run/httpd.pid
 -D DEFAULT_SCOREBOARD=logs/apache_runtime_status
 -D DEFAULT_LOCKFILE=/var/run/accept.lock
 -D DEFAULT_ERRORLOG=logs/error_log
 -D AP_TYPES_CONFIG_FILE=etc/apache22/mime.types
 -D SERVER_CONFIG_FILE=etc/apache22/httpd.conf

No PROXY_HTTP, no SUEXEC_DOCROOT ...


OK, tried manually wihtout Poudriere:

cd /usr/ports/www/apache22
make deinstall
rm -r /var/db/ports/apache22
make clean
make -DBATCH -DPROXY=on -DPROXY_HTTP=on -DSUEXEC=on 
-DSUEXEC_DOCROOT=/var/apache -DSUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log 
install

Result:

nanobsd# httpd -V
Server version: Apache/2.2.23 (FreeBSD)
Server built:   Feb 21 2013 10:05:05
Server's Module Magic Number: 20051115:31
Server loaded:  APR 1.4.6, APR-Util 1.4.1
Compiled using: APR 1.4.6, APR-Util 1.4.1
Architecture:   64-bit
Server MPM: Prefork
  threaded: no
forked: yes (variable process count)
Server compiled with
 -D APACHE_MPM_DIR=server/mpm/prefork
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses disabled)
 -D APR_USE_FLOCK_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT=/usr/local
 -D SUEXEC_BIN=/usr/local/bin/suexec
 -D DEFAULT_PIDLOG=/var/run/httpd.pid
 -D DEFAULT_SCOREBOARD=logs/apache_runtime_status
 -D DEFAULT_LOCKFILE=/var/run/accept.lock
 -D DEFAULT_ERRORLOG=logs/error_log
 -D AP_TYPES_CONFIG_FILE=etc/apache22/mime.types
 -D SERVER_CONFIG_FILE=etc/apache22/httpd.conf


So it seems like the method I used for years does not work anymore now that
we have OptionsNG :-( I already spent quite some time searching the 
documentation
for a way to specify these options, without success so far.


Next try:

make config, enable PROXY, PROXY_HTTP, SUEXEC, then specify the rest on the 
command
line when building:

make -DBATCH -DSUEXEC_DOCROOT=/var/apache 
-DSUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log install

Result:

Proxy modules installed, suexec binary installed, but:

nanobsd# /usr/local/sbin/suexec -V
 -D AP_DOC_ROOT=/usr/local/www/data
 -D AP_GID_MIN=1000
 -D AP_HTTPD_USER=www
 -D AP_LOG_EXEC=/var/log/httpd-suexec.log
 -D AP_SAFE_PATH=/usr/local/bin:/usr/bin:/bin
 -D AP_UID_MIN=1000
 -D AP_USERDIR_SUFFIX=public_html


*gnagnagna* ... I'm running out of ideas here.


But this is definitely no Poudriere related question, anymore. Thanks for your 
help.
If you have a pointer to something I might have missed regarding OptionsNG, that
would be great.


Kind regards
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Poudriere questions

[Patrick M. Hausen]

Good morning,

Am 20.02.2013 um 18:28 schrieb Guido Falsi m...@madpilot.net:
 There is no per port file, but, bbeing make.conf a file sourced by make, you 
 can use make syntax:
 
 .if ${.CURDIR:M*www/apache22*}
   SUEXEC_DOCROOT=/foo/bar
 .endif


Now that I gave that a try it seems like there's something missing:

/etc/make.conf, line 5: Unassociated shell command PROXY=on
/etc/make.conf, line 6: Unassociated shell command PROXY_HTTP=on
/etc/make.conf, line 7: Unassociated shell command SUEXEC=on
/etc/make.conf, line 8: Unassociated shell command 
SUEXEC_DOCROOT=/var/apache
/etc/make.conf, line 9: Unassociated shell command 
SUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log

That's my make.conf:

.if ${.CURDIR:M*www/apache22*}
PROXY=on
PROXY_HTTP=on
SUEXEC=on
SUEXEC_DOCROOT=/var/apache
SUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log
.endif

Thanks
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Poudriere questions

[Patrick M. Hausen]

Hello,

we use NanoBSD to build the software installations for our hosting platform
and I'm trying to better automate the process of building packages.

Poudriere looked like an interesting tool to me, so I tried it. Quite painless,
but two questions currently remain:

To me it looks like Poudriere populates the build jail/chroot from release
tarballs fetched from an FTP server - but I'd rather use, say, 8.3p6 as
the build platform as well as the one at runtime. At ~300+ installed ports
I simply do not know if anything links statically against base system libraries
and I want to catch all security updates included in RELENG_X_Y.
How would I go about that?

Second, how do I specify build time options that are not available via the
dialog most ports use for make config? Currently we use an ad hoc shell
script that simply installs all the ports I want, and the line for e.g. Apache 
reads:

cd /usr/ports/www/apache22  make -DBATCH -DPROXY=on -DPROXY_HTTP=on 
-DSUEXEC=on -DSUEXEC_DOCROOT=/var/apache 
-DSUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log install

I can enable all options that simply taken an on setting, but what about
the paths for suexec? Obviously they are critical to the operation of our 
servers.

If this is the wrong list, I can of course take the discussion to -ports or
anything else more appropriate. The Poudriere wiki doesn't mention
external ressources besides IRC.

Thanks 
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Poudriere questions

[Patrick M. Hausen]

Hello,

Am 20.02.2013 um 18:07 schrieb Guido Falsi m...@madpilot.net:
 I'm not sure I get what you ask. You can make poudriere fetch sources from 
 any subversion branch/tag and compile those
 instead of using the distribution files. For example:
 
 poudriere jail -c -j 91releng -v releng/9.1 -m svn
 
 will fetch sources from the 9.1 security fix branch with all the latest 
 security fixes, compile those and crate a new jail.

That was precisely what I was looking for - thanks.

 I think your best bet is using customized make.conf files in 
 /usr/local/etc/poudriere.d.
 This is documented well in the CUSTOMIZATION section of the poudriere(8) man 
 page.

And pray that no other software package besides Apache uses an option named
SUEXEC_DOCROOT and I want a different value for that one ... ;-)

Is there no way to specify make variables that need values in the port specific
options file?

But here, too - thanks for the hint. That _should_ work in my case, though it is
not generally applicable.

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Poudriere questions

[Patrick M. Hausen]

Hi, Guido,

Am 20.02.2013 um 18:28 schrieb Guido Falsi m...@madpilot.net:
 Is there no way to specify make variables that need values in the port 
 specific
 options file?
 
 There is no per port file, but, bbeing make.conf a file sourced by make, you 
 can use make syntax:
 
 .if ${.CURDIR:M*www/apache22*}
   SUEXEC_DOCROOT=/foo/bar
 .endif


That will not just do fine, but really great. Since I have only one target 
platform
to build for, a central place to keep configuration is preferred, anyway.

Though I'm a seasoned admin, I did not know make was that capable. So two
reasons to say thanks. Case closed. ;-)

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: svn - but smaller?

[Patrick M. Hausen]

Hi, all,

Am 24.01.2013 um 15:20 schrieb Gyrd Thane Lange gyrd...@thanelange.no:
 It is not a well publicized fact, but I understand that the base utility 
 freebsd-update(8) through it's freebsd-update.conf(5) is able to pull the 
 base sources (/usr/src/) only instead of also updating your binaries.
 
 less /etc/freebsd-update.conf
 
  # Components of the base system which should be kept updated.
  Components src world kernel
 
 The above setting is the default, but you may easily leave out everything but 
 src. (Caveat: I have not tried it myself yet.)
 It also have some optional settings for preserving local changes to the 
 source instead of blowing them away (default).
 
 This will allow you to use the sources for a custom build and install 
 yourself.


I tried that and found that at least /usr/src/UPDATING was not touched by 
freebsd-update.
See e4e97bb3-4535-4e9f-ad78-e16a94f75...@punkt.de on this list.

Any hints welcome - must have been doing someting wrong.

Thanks
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Does / Is anyone maintaining CVS for FreeBSD?

[Patrick M. Hausen]

Hi, all,

Am 03.01.2013 um 19:21 schrieb Matthew Seaman m.sea...@infracaninophile.co.uk:
 On 03/01/2013 17:48, Patrick M. Hausen wrote:
 I'm a bit reluctant to installing svn on every system that needs source
 updates. Are there more lightweight ways?
 
 freebsd-update(8)
 
 which is what 'make update' will run by default and in the absence of
 any configuration to use other mechanisms.


Sorry for being too terse in my first post. Seems like I should have a closer
look at freebsd-update. Of course I have lines like this in my /etc/make.conf
on each machine that I update from sources:

SUP_UPDATE= yes
SUP=/usr/bin/csup
SUPFLAGS=   -g -L 2
SUPHOST=cvsup2.de.freebsd.org
SUPFILE=/usr/share/examples/cvsup/standard-supfile
PORTSSUPFILE=   /usr/share/examples/cvsup/ports-supfile

And yes, guilty of never ever re-evaluating that mechanism since FreeBSD 2.x.
The only change I ever made was replacing cvsup with csup, once the latter
became available. And I did not know make update had a default without
any configuration.
That's why I ask stupid questions about whatever it is people use nowadays.

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Does / Is anyone maintaining CVS for FreeBSD?

[Patrick M. Hausen]

Hi, all,

Am 04.01.2013 um 10:42 schrieb Chris Rees utis...@gmail.com:
 Is there a problem with using freebsd-update for your sources too?

I don't know - yet. First question that comes up, after reading the manpages
and freebsd-update.conf(5):

datatomb2# uname -r
8.3-RELEASE-p4
datatomb2# grep Components /etc/freebsd-update.conf 
...
Components src
...

First naive try:

datatomb2# cd /usr/src/
datatomb2# make update
# nothing happens

Next try:

datatomb2# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from update4.FreeBSD.org... done.
Fetching metadata signature for 8.3-RELEASE from update4.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 6 patches done.
Applying patches... done.
Fetching 6 files... done.

The following files will be updated as part of updating to 8.3-RELEASE-p5:
/usr/src/contrib/bind9/bin/named/query.c
/usr/src/contrib/bind9/lib/dns/include/dns/rdata.h
/usr/src/contrib/bind9/lib/dns/master.c
/usr/src/contrib/bind9/lib/dns/rdata.c
/usr/src/contrib/wpa/src/eap_server/eap_tls_common.c
/usr/src/secure/lib/libcrypt/crypt-des.c
/usr/src/sys/amd64/amd64/trap.c
/usr/src/sys/compat/linux/linux_ioctl.c
/usr/src/sys/conf/newvers.sh
/usr/src/sys/netinet/tcp_input.c
/usr/src/sys/netinet6/in6.c
/usr/src/sys/netinet6/ip6_input.c

datatomb2# freebsd-update install
Installing updates... done.

Great, but /usr/src/UPDATING is still at p4 instead of p5???

So - this is definitely no simple plug-in replacement for csup.
And is there a Components ports? Doesn't look like it.

Thanks,
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Does / Is anyone maintaining CVS for FreeBSD?

[Patrick M. Hausen]

Hello,

Am 03.01.2013 um 16:36 schrieb Eitan Adler li...@eitanadler.com:
 CVS/SVN should be considered a development tool.  Users should not see
 the impact of the switch.  In theory.


What is the recommended csup replacement for users that did

cd /usr/src  make update buildworld buildkernel

as their method of keeping the system current?

I'm a bit reluctant to installing svn on every system that needs source
updates. Are there more lightweight ways?

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FreeBSD and IPMI how-to (was Re: su problem)

[Patrick M. Hausen]

Hi, all,


Am 15.06.2012 um 03:27 schrieb Matthew X. Economou:
 Daniel Braniss writes:
 
 just for the record, serial on 8.x works fine! the device naming
 has changed from sio to uart, and maybe some features. We use it
 on all our servers, even redirecting it where possible via
 ILO,IMPI,DRAC.  and is great for debuging or saving long trips :-)
 
 Would some kind soul point me to a howto for configuring IPMI on
 FreeBSD?  I have a Dell PowerEdge 840 that supports IPMI, but I have
 no idea how to set it up - either in the BIOS or in FreeBSD.  I've
 messed around with ipmitools a little, but I haven't gotten it to
 work.


Did you

kldload ipmi
?

What's the output of

dmesg
kldstat

after loading the module?

With the module loaded, you should be able to get something like this:

devel# ipmitool sensor
Ambient  | 23.500 | degrees C  | ok| na| 1.000 | 
6.000 | 37.000| 42.000| na
Systemboard  | 32.000 | degrees C  | ok| na| na| na 
   | 60.000| 65.000| na
CPU1 | 49.000 | degrees C  | ok| na| na| na 
   | 93.000| 97.000| na
CPU2 | 48.000 | degrees C  | ok| na| na| na 
   | 93.000| 97.000| na
...
FAN1 SYS | 6120.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN2 SYS | 6480.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN3 SYS | 6000.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN4 SYS | 6480.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN5 SYS | 6120.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN6 SYS | 6480.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN7 SYS | 6120.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN8 SYS | 6480.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN9 SYS | 6240.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN10 SYS| 6720.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN11 SYS| 6240.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
FAN12 SYS| 6720.000   | RPM| ok| na| 1920.000  | na 
   | na| na| na
PSU1 Power   | 100.000| Watts  | ok| na| na| na 
   | na| na| na
PSU2 Power   | 96.000 | Watts  | ok| na| na| na 
   | na| na| na
Total Power  | 196.000| Watts  | ok| na| na| na 
   | na| na| na
Total Power Out  | 172.000| Watts  | ok| na| na| na 
   | na| na| na
...


Kind regards,
Patrickj
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

ZFS autoexpand when there are 2 raidz2 vdevs

[Patrick M. Hausen]

Hi, all,

during the last couple of years I occasionally increased the capacity
of raidz2 based zpools by replacing one disk at a time and resilvering,
subsequently. After replacing the final disk and a reboot (I guess
zpool export  zpool import would have done the trick, too) the capacity
of the FS on top of that pool was increased according to the size of
the new disk. All of theses systems had a pool built on one single vdev.

Last week I exchanged all disks of one vdev that is part of a 2 vdev
zpool. According to the Solaris documentation I found that should be
possible. I always assumed vdevs were sort of independent of each
other.

My observations:

During resilvering the activity LEDs of all 12 disks were showing heavy
load, not only the ones of the 6 disks being part of the vdev in question.

After exchanging all 6 disks the capacity stayed the same. I tried

zpool export, zpool import
reboot
zpool scrub

to no avail.

datatomb2# zpool status sx40
  pool: sx40
 state: ONLINE
 scan: scrub repaired 0 in 3h32m with 0 errors on Sat Jun  2 00:41:38 2012
config:

NAME STATE READ WRITE CKSUM
sx40 ONLINE   0 0 0
  raidz2-0   ONLINE   0 0 0
gpt/sx40-disk0   ONLINE   0 0 0
gpt/sx40-disk1   ONLINE   0 0 0
gpt/sx40-disk2   ONLINE   0 0 0
gpt/sx40-disk3   ONLINE   0 0 0
gpt/sx40-disk4   ONLINE   0 0 0
gpt/sx40-disk5   ONLINE   0 0 0
  raidz2-1   ONLINE   0 0 0
gpt/sx40-disk6   ONLINE   0 0 0
gpt/sx40-disk7   ONLINE   0 0 0
gpt/sx40-disk8   ONLINE   0 0 0
gpt/sx40-disk9   ONLINE   0 0 0
gpt/sx40-disk10  ONLINE   0 0 0
gpt/sx40-disk11  ONLINE   0 0 0

errors: No known data errors

datatomb2# zpool get all sx40
NAME  PROPERTY   VALUE   SOURCE
sx40  size   10.9T   -
sx40  capacity   78% -
sx40  altroot-   default
sx40  health ONLINE  -
sx40  guid   1478259715706579670  default
sx40  version28  default
sx40  bootfs -   default
sx40  delegation on  default
sx40  autoreplaceoff default
sx40  cachefile  -   default
sx40  failmode   waitdefault
sx40  listsnapshots  off default
sx40  autoexpand on  local
sx40  dedupditto 0   default
sx40  dedupratio 1.00x   -
sx40  free   2.31T   -
sx40  allocated  8.57T   -
sx40  readonly   off -

The first 6 disks building raidz2-0 are 2 TB ones, not 1 TB.
The gpt partitions *are* about 2 TB in size.

What am I missing? Any hints welcome. I do have the hardware
to build another device with 6 drives 2 TB and 6 drives 1 TB,
which I planned to hook up to another server. Of course I could
connect it to this one first, build a second pool, copy over the
data ... but I was trying to avoid that in the first place ;-)

Thanks in advance,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ZFS autoexpand when there are 2 raidz2 vdevs

[Patrick M. Hausen]

Hi,

Am 05.06.2012 um 14:28 schrieb Holger Kipp:
 I used
 zpool set autoextend=on tank
 zpool online -e tank da0
 zpool online -e tank da1
 ...
 zpool online -e tank da7
 
 to increase the size of a raidz2
 here from 5+ to 11+TB. Worked without problems.

datatomb2# zpool online -e sx40 gpt/sx40-disk0
...
datatomb2# zpool online -e sx40 gpt/sx40-disk5

datatomb2# zpool get all sx40
NAME  PROPERTY   VALUE   SOURCE
sx40  size   16.3T   -
...

Thanks!

 This was with v28. Please check manages etc. for further explanations.


Done :-) Still puzzled why this worked automagically before. I don't have the
time right now to check the repository for a change that might disable the
automatic expansion of all new devices, but I suspect something like this.
I see how it is safer if you trigger expansion manually. E.g. if you need to use
a bigger temporary disk untill your warranty replacement with the correct size 
arrives.

Best regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Restricting users from certain privileges

[Patrick M. Hausen]

Hi, all,

Am 28.04.2012 um 11:39 schrieb Eugene Grosbein:

 28.04.2012 14:50, Zenny пишет:
 
 try sudo from ports, security/sudo
 
 cheers,
   danny
 
 
 Thanks Daniel, but sudo gives all (not selective) root privileges to the
 user (admin in my case). So this is not what I am trying to achieve in my
 original post.
 
 Please do study sudo real power :-)
 It can give selective privileges per-command,
 an d it can also allow one to run some command with some arguments only
 and not with others. Or, without any arguments only - as you tune
 its sudoers configuration file.


Just make sure none of the permitted commands has got the
feature of starting a shell ;-))

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Support for IPSec NAT-T in transoprt mode

[Patrick M. Hausen]

Hi, all,

Am 14.04.2012 um 18:59 schrieb Bjoern A. Zeeb:
 No FreeBSD tree shipped does
 support transport mode at this time.

I remember that I ran a Soekris device with RELENG_6 NanoBSD
to drive my VPN connection via transport mode.
Racoon for IKE, standard IPSEC as shipped with RELENG_6.

Was is removed afterwards?

Regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ZFS NFS

[Patrick M. Hausen]

Hello,

Am 16.03.2012 um 18:20 schrieb Slawa Olhovchenkov:
 I do NFSv3 export of ZFS.
 root from remote host create files on ZFS witch uid 2^32-2:
 
 # ls -l /usr/ports/packages32/
 total 6
 drwxr-xr-x  2 4294967294  wheel  5 Mar 17 00:57 All
 drwxr-xr-x  2 4294967294  wheel  5 Mar 17 00:57 Latest
 drwxr-xr-x  2 4294967294  wheel  3 Mar 17 00:52 archivers
 drwxr-xr-x  2 4294967294  wheel  4 Mar 17 00:57 lang


Yes? This is expected behaviour of NFS. If you don't want that, try

-maproot=root

either in sharenfs option to zfs or /etc/exports, whichever it is you are using.

HTH,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ZFS NFS

[Patrick M. Hausen]

Hello,

Am 16.03.2012 um 18:42 schrieb Slawa Olhovchenkov:
 On Fri, Mar 16, 2012 at 06:32:43PM +0100, Patrick M. Hausen wrote:
 
 Hello,
 
 Am 16.03.2012 um 18:20 schrieb Slawa Olhovchenkov:
 I do NFSv3 export of ZFS.
 root from remote host create files on ZFS witch uid 2^32-2:
 
 # ls -l /usr/ports/packages32/
 total 6
 drwxr-xr-x  2 4294967294  wheel  5 Mar 17 00:57 All
 drwxr-xr-x  2 4294967294  wheel  5 Mar 17 00:57 Latest
 drwxr-xr-x  2 4294967294  wheel  3 Mar 17 00:52 archivers
 drwxr-xr-x  2 4294967294  wheel  4 Mar 17 00:57 lang
 
 
 Yes? This is expected behaviour of NFS. If you don't want that, try
 
  -maproot=root
 
 either in sharenfs option to zfs or /etc/exports, whichever it is you are 
 using.
 
 hmm...
 nobody:*:65534:65534:Unprivileged user:/nonexistent:/usr/sbin/nologin
 
 65534 != 4294967294 (2^16-2 != 2^32-2)
 
 Also, I am think ZFS+NFS will be wrong for UID2^15.

I admit I overlooked that one (16 vs 32 bits). But if I'm not mistaken, NFS 
does not care
a bit about the name of the user nobody or the UID in /etc/passwd or 
what-have-you.
It simply sets the UID of remote root (UID 0) to the value -1.

And 4294967294 happens to be -1 in 32 bits signed. So - possibly this is built 
into
ZFS this way. I would at least give the sharenfs=... options a try ...

HTH,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ZFS NFS

[Patrick M. Hausen]

Hi, all,

Am 16.03.2012 um 18:51 schrieb Florian Wagner:
 And FreeBSD != Linux. Access from root does not get mapped to nobody.
 See exports(5).


$ man exports
...
 In the absence of -maproot and -mapall options, remote accesses by root
 will result in using a credential of -2:-2.  All other users will be
 mapped to their remote credential.  If a -maproot option is given, remote
 access by root will be mapped to that credential instead of -2:-2.  If a
 -mapall option is given, all users (including root) will be mapped to
 that credential in place of their own.
...

RELENG_8_2

So make that -1 in my last mail a -2. ;-)

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Swap on zvol - recommendable?

[Patrick M. Hausen]

Hi, all,

is it possible to make a definite statement about swap on zvols?

I found some older discussions about a resource starvation
scenario when ZFS arc would be the cause of the system
running out of memory, trying to swap, yet the ZFS would
not be accessible until some memory was freed - leading to
a deadlock.

Is this still the case with RELENG_8? The various Root on
ZFS guides mention both choices (decicated or gmirror
partition vs. zvol), yet don't say anything about the respective
merits or risks. I am aware of the fact that I cannot dump to
a raidz2 zvol ...

Thanks for any hints,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: about thumper aka sun fire x4500

[Patrick M. Hausen]

Hi, all,

Am 17.01.2012 um 18:59 schrieb peter h pe...@hk.ipsec.se:

 I have been beating on of these a few days, i have udes freebsd 9.0 and 8.2
 Both fails when i engage  10 disks, the system craches and messages :
 Hyper transport sync flood will get into the BIOS errorlog ( but nothing 
 will
 come to syslog since reboot is immediate)
 
 Using a zfs radz of 25 disks and typing zpool scrub will bring the system 
 down in seconds.
 
 Anyone using a x4500 that can comfirm that it works ? Or is this box broken ?

Well, I hate to write that, but ... does it work with the vendor supported [tm] 
OS?
If yes, you can rule out a hardware defect. I would at least try Solaris for 
this reason.
If no, the HW is broken and there is no need to look for a fault on FreeBSD's 
side.

Kind regards,
Patrick___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: about thumper aka sun fire x4500

[Patrick M. Hausen]

Hi all,

Am 18.01.2012 um 00:14 schrieb peter h pe...@hk.ipsec.se:
 On Tuesday 17 January 2012 23.15, Ronald Klop wrote:
 On Tue, 17 Jan 2012 18:59:08 +0100, peter h pe...@hk.ipsec.se wrote:
 
 I have been beating on of these a few days, i have udes freebsd 9.0 and  
 8.2
 Both fails when i engage  10 disks, the system craches and messages :
 Hyper transport sync flood will get into the BIOS errorlog ( but  
 nothing will
 come to syslog since reboot is immediate)
 
 Using a zfs radz of 25 disks and typing zpool scrub will bring the  
 system down in seconds.
 
 Anyone using a x4500 that can comfirm that it works ? Or is this box  
 broken ?
 
 Does it work if you make 3 raid groups of 8 disks and 1 spare?
 No, i did not test this.  
 I did some simple ones ( 5 disks in a raidz ) but what i wanted this box
 to do is a more powerful work. For smaller stuff i use simple hardware
 
 I guess i'll buy some supermicro box instead.

But Ronald is right. I apologize for not reading your initial post thoroughly 
and
jumping on your suspicion that the hardware might be to blame.

Did you really create one vdev of 25 disks?

This is strongly discouraged by the documentation provided by Sun/Oracle.

You should (IIRC) never have more than 9 disk in a single vdev. Of course
you can join N vdevs of type, say, raidz2 to a single zpool.

See for example http://forums.freebsd.org/archive/index.php/t-4641.html

I'm writing from my iPad and cannot quickly find the Link to the Sun 
documentation.

Kind regards, HTH,
Patrick___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server

[Patrick M. Hausen]

Hi, all,

Am 15.12.2011 um 12:18 schrieb Michael Ross:
 Following Steven Hartlands' suggestion,
 from one of my machines:
 
 /usr/ports/sysutils/dmidecode/#sysctl -a | egrep hw.vendor|hw.product
 
 /usr/ports/sysutils/dmidecode/#dmidecode -t 2
 # dmidecode 2.11
 SMBIOS 2.6 present.
 
 Handle 0x0002, DMI type 2, 15 bytes
 Base Board Information
Manufacturer: FUJITSU
Product Name: D2759
Version: S26361-D2759-A13 WGS04 GS02
Serial Number: 35838599
Asset Tag: -
Features:
Board is a hosting board
Board is removable
Location In Chassis: -
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0


Without the need to install an additional port:

datatomb2# kenv
…
smbios.bios.reldate=11/03/2011
smbios.bios.vendor=FUJITSU // American Megatrends Inc.
smbios.bios.version=V4.6.4.1 R1.18.0 for D3034-A1x
smbios.chassis.maker=FUJITSU
smbios.chassis.serial=YLAP004857
smbios.chassis.tag=System Asset Tag
smbios.chassis.version=RX100S7R2
smbios.memory.enabled=8388608
smbios.planar.maker=FUJITSU
smbios.planar.product=D3034-A1
smbios.planar.serial=LJ1B-P00996
smbios.planar.version=S26361-D3034-A100 WGS01 GS02
smbios.socket.enabled=1
smbios.socket.populated=1
smbios.system.maker=FUJITSU
smbios.system.product=PRIMERGY RX100 S7
smbios.system.serial=YLAP004857
smbios.system.uuid=f0493081-f5ca-e011-b8a5-a1c4d143da5f
smbios.system.version=GS02
smbios.version=2.7
…

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Hot-changing a failed HDD with ahci.ko

[Patrick M. Hausen]

Hi, all,

while most cheap servers with SATA disks are not really hot-plug
capable, changing a failed disk (either gmirror or zfs) was possible
without a reboot by executing e.g. if ad4 failed:

atacontrol detach ata2
change disks
atacontrol attach ata2

What is the proper equivalent for ahci, ada0 and camcontrol?
Stop unit commands seem not to work with SATA disks, so I
tried:

forcefully unplug broken disk
- system logs about lost device, so far so good
insert new disk
camcontrol reset 1
camcontrol devlist
- disk still not there
camcontrol rescan 1
- command hangs
login to a second session, system still responsive
shutdown -r now
- system panics, eventually reboots

I can provide details about the panic if someone is interested,
but maybe there is a proper procedure already, which I simply missed.

System is RELENG_8_2 amd64.
ahci0: Intel Cougar Point AHCI SATA controller port 
0xf090-0xf097,0xf080-0xf083,0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 
0xfb921000-0xfb9217ff irq 19 at device 31.2 on pci0
ada0 at ahcich0 bus 0 scbus1 target 0 lun 0
ada0: ST31000340NS SN05 ATA-8 SATA 1.x device
ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada1 at ahcich1 bus 0 scbus2 target 0 lun 0
ada1: ST31000340NS SN05 ATA-8 SATA 1.x device
ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Hot-changing a failed HDD with ahci.ko

[Patrick M. Hausen]

Hi!

Am 14.12.2011 um 10:26 schrieb Jeremy Chadwick:
 What is the proper equivalent for ahci, ada0 and camcontrol?
 
 None is needed: yank the disk, reinsert, wait a few seconds, done.
 Validation, with full output, hardware, etc:
 
 http://koitsu.wordpress.com/2010/07/22/freebsd-and-zfs-hot-swapping-sata-disks-with-ahci/

Yank the disk:
(ada0:ahcich0:0:0:0): lost device

Reinsert - nothing happens.

 shutdown -r now
 - system panics, eventually reboots
 
 Before you yanked the disk, were any non-ZFS filesystems mounted?

Yes - my fault. I had an active swap partition on the disk which perfectly
explains the panic.

 You might try booting RELENG_9 (which has ahci.ko as the default, so no
 need to mess about) on a LiveCD or equivalent and attempt the same
 thing.  I'm left wondering if there's some stuff in RELENG_8 (not a typo
 compared to the above RELENG_9 reference) that you do not have in
 RELENG_8_2.

I'll try upgrading to RELENG_8 first and report the results.

Side note:
ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes)

I noticed that while preparing the last mail and removed those little jumpers
limiting my hard drives ;-)

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Hot-changing a failed HDD with ahci.ko

[Patrick M. Hausen]

Hi!

Am 14.12.2011 um 10:52 schrieb Patrick M. Hausen:
 Yes - my fault. I had an active swap partition on the disk which perfectly
 explains the panic.

I replaced that one with a gmirror device, now.

 You might try booting RELENG_9 (which has ahci.ko as the default, so no
 need to mess about) on a LiveCD or equivalent and attempt the same
 thing.  I'm left wondering if there's some stuff in RELENG_8 (not a typo
 compared to the above RELENG_9 reference) that you do not have in
 RELENG_8_2.
 
 I'll try upgrading to RELENG_8 first and report the results.


datatomb2# uname -a
FreeBSD datatomb2.pluspunkthosting.de 8.2-STABLE FreeBSD 8.2-STABLE #0: Wed Dec 
14 12:44:07 CET 2011 
r...@datatomb2.pluspunkthosting.de:/usr/obj/usr/src/sys/GENERIC  amd64

Yank disk:
ada1:GEOM_MIRROR: Device swap: provider ada1p2 disconnected.
(ahcich1:0:0:0): lost device
(ada1:ahcich1:0:0:0): removing device entry

Put it back in:
ada1 at ahcich1 bus 0 scbus2 target 0 lun 0
ada1: ST31000340NS SN05 ATA-8 SATA 2.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)

And I get ZFS v28, too :-))

Thanks and kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: nsswitch problem ...

[Patrick M. Hausen]

Hello,

Am 30.09.2011 um 16:00 schrieb Teratux:
 My nscd daemon is also configured to hold it's cache for a long period of 
 time.
 When I reboot my machine I cannot login ...

reboot == restart of nscd == empty cache, if I'm not mistaken.

If nscd has a persistent storage for cache entries, that would
be news to me. IIRC it uses only memory.

HTH,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org