Re: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks
Hi, all, Am 09.01.2011 um 11:03 schrieb Matthew Seaman: > [*] All of this mathematics is pretty suspect, because if two drives > fail simultaneously in a machine, the chances are the failures are not > independent, but due to some external cause [eg. like the case fan > breaking and the box toasting itself.] In which case, the comparative > chance of whatever it is affecting three or four drives at once renders > the whole argument pointless. I assume you are familiar with these papers? http://queue.acm.org/detail.cfm?id=1317403 http://queue.acm.org/detail.cfm?id=1670144 Short version: as hard disk sizes increase to 2 TB and beyond while the URE rate stays in the order of 1 to 10^14 blocks read, the probability of encountering an URE during rebuild of a single parity RAID approaches 1. 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: 8.1 amd64 lockup (maybe zfs or disk related)
Hello, Jeremy, Am 07.02.2011 um 09:55 schrieb Jeremy Chadwick: > The Wiki is outdated, I'm sorry to say. Given that you have 8GB RAM, I > would recommend these settings. > ... Thank you very much for the insight. A current summary of recommended settings is very much appreciated. Could you add values for amd64 machines with 4 and 16 GB of memory? That would help me a lot. Storage around 4 and 11 TB, respectively. Access pattern: backup storage. 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: 8.1 amd64 lockup (maybe zfs or disk related)
Hello, Am 08.02.2011 um 16:00 schrieb Tom Evans: > My home file server is similar in spec to that - Core 2 Duo, 4 GB RAM > and running 8.2-RC3/amd64, with a pool with two 6 x 1.5 TB raidz > arrays, for a total capacity of ~16 TB. The only ZFS settings I have > changed from default are: > > # Allow prefetch (normally disabled for 4GB or less RAM) > vfs.zfs.prefetch_disable=0 > # Don't let ZFS use UMA, restricts available memory > vfs.zfs.zio.use_uma=0 > > I think vfs.zfs.zio.use_uma defaults to 0 now anyway. > > I've never had a crash related to memory pressure or any other ZFS > issue - it doesn't get that stressed. YMMV! Yes, it may - and it does ;-) With no tuning at all my FreeNAS (FreeBSD 7.3, amd64, 4 GB RAM, 4 TB raidz2) crashes within minutes if I copy larger amounts of data via SMB or AFP to the ZFS. With these settings it's perfectly stable, but I figured from Jeremy's that they might not be optimal: vm.kmem_size_max="1024M" vm.kmem_size="1024M" vfs.zfs.arc_max="100M" vfs.zfs.prefetch_disable="0" And with the very same settings on our bigger backup box I really need to improve performance somehow. We are backing up >50 hosts nightly with Amanda. I got from this post that I definitely should increase memory on this machine: http://constantin.glez.de/blog/2010/06/closer-look-zfs-vdevs-and-performance 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"
Disable probing of bge1?
Hi, all, I just discovered a minor problem when updating some rather dated systems from FreeBSD 6.x to 7.x or 8.x. The servers are Fujitsu Technology Solutions (former Fujitsu-Siemens) RX100 S4. The current generation of the same system is RX100 S6, so this is two generations old. Some of them still run fine in our datacenter, though. While the S5 and S6 series features two gigabit ports and an additional network interface for out of band management (called iRMC, similar to HP's iLO), the S4 has only two gigabit ports and the iRMC interface is piggybacked to one of them. In our standard setup we disable the first interface in the BIOS. If you do this, the physical port is available as a dedicated management interface to the iRMC and only the second IF is probed by FreeBSD 6.x as bge0. Now I try to PXE boot an identically configured system via the remote serial console with FreeBSD 7. Everything runs fine, until the kernel probes the network interfaces. The last thing I see are messages about successful probing of both bge0 and bge1 and then my remote management connection and my console are gone. I have to reset the BMC by literally pulling the power to get the iRMC back. Is it possible to use some device.hints entry to prohibit the probing of bge1? I think that would be the easiest solution to the problem? Other suggestions are of course welcome. I can provide more config details and dmesg output if needed. 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"
ZFS performance as the FS fills up?
Hi, all, we use a big JBOD and ZFS with raidz2 as the target for our nightly Amanda backups. I already suspected that the fact that the FS was > 90% full might be the cause of our backup performance continously decreasing. I just added another vdev - 6 disks of 750 GB each, raidz2 and the FS usage is back to 71% currently. This was while backups were running and write performance instantly skyrocketed compared to the values before. So, is it possible to name a reasonable amount of free space to keep on a raidz2 volume? On last year's EuroBSDCon I got the impression that with recent (RELENG_8) ZFS merges I could get away with using around 90%. 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: Disable probing of bge1?
Hello, Am 07.03.2011 um 13:37 schrieb Tom Evans: > Maybe this loader tunable will help: > hw.bge.allow_asf > Allow the ASF feature for cooperating with IPMI. Can cause sys‐ > tem lockup problems on a small number of systems. Disabled by > default. No - same result: bge0: mem 0xfd21-0xfd21,0xfd20-0xfd20 irq 16 at device 4.0 on pci8 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:0a:e4:82:c1:0f bge0: [ITHREAD] bge1: irq 1 Here the iRMC console is disconnected. Thanks anyway, 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 performance as the FS fills up?
Hello, Am 09.03.2011 um 14:28 schrieb Tom Evans: > I don't think this is accurate. Prefetch was certainly disabled by > default on 8.0 if you had 4GB of RAM or less, requiring the sysctl > vfs.zfs.prefetch_disable=0 to be set if you wanted prefetch and had > 4GB of RAM or less. My configuration is this: JBOD with 24 disks before the performance increase, now 30. 5 vdevs of 6 disks each, raidz2. 16 GB RAM, 8.2 amd64. vm.kmem_size="12288M" vfs.zfs.arc_max="8192M" vfs.zfs.prefetch_disable="1" vfs.zfs.txg.timeout="5" --- net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.sendspace=65536 net.inet.tcp.recvspace=131072 kern.maxvnodes=25 vfs.zfs.txg.write_limit_override=1073741824 After I added the last 6 disks net write performance (that means how quick Amanda fills the current vtape) at least doubled. Without any further Amanda tuning. I am aware that there are many components involved that affect performance, so what would be the best way to measure the ZFS part? Working crystal balls have become rare these days ;-) 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"
ahci.ko in RELENG_8_2, what about atacontrol cap?
Hi, all, On my system using the "old" ATA driver, I can use a command like this to get useful information about my disk drives: nas-pmh# atacontrol cap ad4 Protocol SATA revision 2.x device model ST32000542AS serial number 5XW251QF firmware revision CC34 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 3907029168 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 49344/0xC0C0 automatic acoustic management yes yes 254/0xFE254/0xFE When I switch to the new AHCI driver the drives are connected to the CAM subsystem: nas-pmh# camcontrol devlist at scbus0 target 0 lun 0 (ada0,pass0) at scbus1 target 0 lun 0 (ada1,pass1) at scbus2 target 0 lun 0 (ada2,pass2) at scbus3 target 0 lun 0 (ada3,pass3) at scbus4 target 0 lun 0 (da0,pass4) But: nas-pmh# camcontrol inquiry ada0 nas-pmh# camcontrol readcap ada0 (pass0:ahcich0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 (pass0:ahcich0:0:0:0): CAM status: CCB request was invalid Obvious question: is there a way to get the same information (NCQ support, write cache status, ...) with the new driver? 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: ahci.ko in RELENG_8_2, what about atacontrol cap?
Hello, Am 02.04.2011 um 11:40 schrieb Jeremy Chadwick: > You want "camcontrol identify adaX". DO NOT confuse this with > "camcontrol inquiry adaX" (this won't work). > > identify = for ATA > inquiry = for SCSI Works perfectly, but I just noticed one really odd thing: 1. boot without ahci.ko: nas-pmh# atacontrol cap ad4 ... write cacheyes yes 2. boot with ahci.ko: nas-pmh# camcontrol identify ada0 ... write cacheyes no Well? ;-) The system is a HP NL36 - I just found a couple of articles mentioning that the default setting in the BIOS setup was write cache disabled. I can check that in the next couple of days when I take the machine back to the lab (no monitor/keyboard at my home office). I'd prefer a way to make sure write cache is enabled via some tuning from FreeBSD. The disks are dedicated to a raidz2, so from what I found around the net, write cache should not pose a major problem. Of course, one will lose _some_ data at a power outage - what I want to avoid for home office use is a completely lost file system. Losing the last time machine backup of my Mac is tolerable. 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: ahci.ko in RELENG_8_2, what about atacontrol cap?
Hi, Am 03.04.2011 um 15:36 schrieb Alexander Motin: > I've noticed that some RAID BIOS'es disable write cache on their disks. > ata(4) enabled cache in such cases, but CAM doesn't now. I'll take care of it > for ATA. For now you can manage it via `camcontrol cmd`. I understand. So probably my disks' WC is set to off in the system BIOS setup - wich is changed upon boot by ata, but not by ahci/cam. 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: ahci.ko in RELENG_8_2, what about atacontrol cap?
Hi, all, Am 03.04.2011 um 15:44 schrieb Patrick M. Hausen: > Am 03.04.2011 um 15:36 schrieb Alexander Motin: >> I've noticed that some RAID BIOS'es disable write cache on their disks. >> ata(4) enabled cache in such cases, but CAM doesn't now. I'll take care of >> it for ATA. For now you can manage it via `camcontrol cmd`. > > I understand. So probably my disks' WC is set to off in the > system BIOS setup - wich is changed upon boot by ata, but > not by ahci/cam. I changed the setting in the BIOS setup to "write cache enabled" and presto - write cache with ahci. Thanks for the 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: ZFS directory with a large number of files
Hi, all, Am 05.08.2011 um 17:12 schrieb Christian Weisgerber: > Daniel Kalchev wrote: > >> On 02.08.11 12:46, Daniel O'Connor wrote: >>> I am pretty sure UFS does not have this problem. i.e. once you >>> delete/move the files out of the directory its performance would be >>> good again. >> >> UFS would be the classic example of poor performance if you do this. > > "Classic" indeed. UFS dirhash has pretty much taken care of this > a decade ago. While dirhash is quite an improvement, it is definitely no silver bullet. When I asked Kirk McKusick at last year's EuroBSDCon if having a six-figure number of files in a single directory was a clever idea (I just had a customer who ran into that situation), he just smiled and shook his head. The directory in question was the typo3temp/pics directory that TYPO3 uses to scale images that are part of the website, so they are handed to the browser in exactly the size they are supposed to be rendered. The performance impact was quite heavy, because at some point requests started to pile up, PHP scripts did not finish in time, fcgi slots stayed used ... most of you will know that scenario. At some threshold a machine goes from "loaded, maybe a bit slow, but generally responsive" to "no f*ing way". Best 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: nsswitch problem ...
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"
Hot-changing a failed HDD with ahci.ko
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 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: -> system logs about lost device, so far so good camcontrol reset 1 camcontrol devlist -> disk still not there camcontrol rescan 1 -> command hangs 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: 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: 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: 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
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
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: 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: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server
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"
Re: about thumper aka sun fire x4500
Hi, all, Am 17.01.2012 um 18:59 schrieb peter h : > 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
Hi all, Am 18.01.2012 um 00:14 schrieb peter h : > On Tuesday 17 January 2012 23.15, Ronald Klop wrote: >> On Tue, 17 Jan 2012 18:59:08 +0100, peter h 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"
Swap on zvol - recommendable?
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: ZFS & NFS
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
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 UID>2^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
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"
Re: Support for IPSec NAT-T in transoprt mode
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: Restricting users from certain privileges
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"
ZFS autoexpand when there are 2 raidz2 vdevs
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
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: FreeBSD and IPMI how-to (was Re: su problem)
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"
Re: ZFS and Storage Systems
Hello, On Tue, Oct 12, 2010 at 02:04:54PM +0200, Greg Byshenk wrote: > On Tue, Oct 12, 2010 at 10:33:49AM +0100, Michal wrote: > > http://www.icc-usa.com/storage-35-2u.asp. > > ... > You say "using a FreeBSD box I can set up ZFS over the drives...", which > doesn't make sense, if I undestand the ICC system. The device appears to > be an NAS system, with an OS, not an external disk bay. To me these look like "storage servers", i.e. standard server hardware with room for a lot of hot pluggable drives. This point in their description seems to confirm that: + DSS Lite That's a Linux based commercial NAS system that you install or plug into standard servers to turn them into a NAS. See http://www.open-e.com/ So, IMHO, yes, you should be able to replace that DSS stuff with either stock FreeBSD or preferrably FreeNAS to turn one of these boxes into a ZFS based NAS. I'll check with the supplier before ordering, nonetheless. 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: / full (107% !!)
Morning, On Wed, Oct 13, 2010 at 01:50:31PM +1100, Jeff Dowsley wrote: > Just did a csup and rebuilt world and kernel, as usual. > Rebooted to single user mode, and kicked off the installkernel. > This bombed with an "unable to write to device", and "device full". > On rebooting, df shows / at 107%. You might want to set INSTALL_NODEBUG=yes in /etc/make.conf 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"
ATA error messages
Hi, all, recently I set up a FreeNAS box: FreeBSD freenas.intern.punkt.de 7.3-RELEASE-p3 FreeBSD 7.3-RELEASE-p3 #0: Sun Oct 17 12:57:33 CEST 2010 r...@dev.freenas.org:/usr/obj/freenas/usr/src/sys/FREENAS-amd64 amd64 This is a HP/Compaq Microserver (Proliant N36L). After setting up the system with 4 used 500 GB Seagate drives to find out if FreeNAS would fit our needs, I replaced the drives with WDC RE4 2 TB (WD2002FYPS) and put the system in production to store backups. Yesterday the file system perfomance suddenly came to a crawl and the system log fills with entries like this: ad8: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=3907027968 ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly ... Only one of the for drives shows these timeouts. My question: does this necessarily mean I have an isolated problem with that particular drive, since the other three are running just fine, or could there still be someting more fundamental going on? atapci0: port 0xd000-0xd007,0xc000-0xc003,0xb000-0xb007,0xa000-0xa003,0x9000-0x900f mem 0xfdfffc00-0xfdff irq 19 at device 17.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.20 controller with 4 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ... ad4: 1907729MB at ata2-master SATA300 ad6: 1907729MB at ata3-master SATA300 ad8: 1907729MB at ata4-master SATA300 ad10: 1907729MB at ata5-master SATA300 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: ATA error messages
Hello, On Tue, Oct 26, 2010 at 03:41:40AM -0700, Jeremy Chadwick wrote: > Please install ports/sysutils/smartmontools (version 5.40) and provide > the output from "smartctl -a /dev/ad8". We'll start there. Thanks for the hints, but it looks like the drive just died ... Case closed, I think. Time to apply for an RMA/warranty form. > Also, you might be interested in using ahci.ko (not ataachi.ko) since > your controller supports AHCI. You'd gain NCQ capability and be given > some of the perks of using CAM. Your disks would be renamed from things > like ad4 to ada0 and ad6 to ada1, however. Just FYI. This is unrelated > to your problem though. I'll give that a try once I find out how to do that in FreeNAS. I know about the renaming - no problem. The system is running from flash and the hard disks contain one raidz2 pool. 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"
boot0cfg and gmirror ...
Hi, all, I know about the "foot shooting" prevention in geom(4) when trying to update the MBR of a mounted disk. I have a system with ad4 and ad6 mirrored and fdisk partitions residing on the mirror to be booted alterningly: hd30# gmirror status NameStatus Components mirror/m0 COMPLETE ad4 ad6 hd30# mount /dev/mirror/m0s1a on / (ufs, local, read-only) devfs on /dev (devfs, local) /dev/mirror/m0s3a on /etc (ufs, local) /dev/mirror/m0s3d on /var (ufs, local, soft-updates) hd30# boot0cfg -v /dev/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 0xa5704:254:63 32852925455539140 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) OK, try to switch to slice 2: hd30# boot0cfg -s 2 -v /dev/mirror/m0 boot0cfg: /dev/mirror/m0: Geom not found boot0cfg: /dev/mirror/m0: ioctl DIOCSMBR: Operation not permitted Known one, set debug flags and try again: hd30# sysctl kern.geom.debugflags=0x10 kern.geom.debugflags: 0 -> 16 hd30# boot0cfg -s 2 -v /dev/mirror/m0 boot0cfg: /dev/mirror/m0: Geom not found boot0cfg: /dev/mirror/m0: ioctl DIOCSMBR: Operation not permitted Er ... well, what now? Out of curiosity I tried: hd30# boot0cfg -s 2 -v /dev/ad4 # 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 0xa5704:254:63 32852925455539140 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F2 (Slice 2) hd30# boot0cfg -v /dev/ad6 # 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 0xa5704:254:63 32852925455539140 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) hd30# boot0cfg -s 2 -v /dev/ad6 # 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 0xa5704:254:63 32852925455539140 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F2 (Slice 2) So, with the prevention removed it is possible to write to the single disks, but not to the mirror as a whole. Weird. Any ideas? What bad things can happen if I keep updating the MBRs of both individual disks seperately - besides bad karma and "See? I told you so!" in case I generate an inconsistent state? Thanks, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: boot0cfg and gmirror ...
Hi, all, > hd30# boot0cfg -s 2 -v /dev/mirror/m0 > boot0cfg: /dev/mirror/m0: Geom not found > boot0cfg: /dev/mirror/m0: ioctl DIOCSMBR: Operation not permitted Simple solution: don't use boot0cfg - use fdisk. I get the bogus (?) "Geom not found" message every time, but the active partition seems to be updated correctly. The only dicussion of this topic that I found dates back to 2005: http://freebsd.monkey.org/freebsd-current/200507/msg00156.html Still not quite sure about possible implications, but I am happy as long as it works. Any caveats? Thanks, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: Block device
h, all, On Tue, Nov 04, 2008 at 03:32:01PM +0100, d_elbracht wrote: > Hi list, > > can someone please explain, why > stat -x /dev/da1 > > show the SCSI-Drive as a character-device ? http://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-block.html HTH, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
LSI SAS3442e supported in 6.4 or 7.1?
Hello, seems like I cannot find out if this card is supported or not. LSI provide drivers for Windows and Linux as usual, and mfi(4) doesn't mention that particular one. But possibly it's of the "MegaRAID Firmware Interface" type that mfi(4) supports? Unfortunately for a particular server model this controller is the only one our vendor (Fujitsu Siemens) offers. 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: aliases not working in em0
Hello, On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote: > ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" > ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" I don't know if this can be the cause of your problem, but the /32 netmask for aliases has been deprecated quite a while ago. Try: ipv4_addrs_em0="192.168.112.1/24 192.168.112.181/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 http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aliases not working in em0
Hi, all, On Tue, Jan 20, 2009 at 08:52:18AM -0500, Steve Bertrand wrote: > For how long? On a 7.0-R box, it works ok with a /32 prefix len: > > %ifconfig > re0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:0f:b5:80:53:85 > inet 208.70.104.210 netmask 0xff00 broadcast 255.255.255.192 > inet 208.70.104.211 netmask 0xff00 broadcast 255.255.255.255 Did you manually edit the ifconfig output? The broadcast addresses should both be 208.70.104.255 for the shown prefixes and netmasks. And I don't see a /32 here, either. 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: switching bsdlabel's label
Hello, On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: > I have a certain disk where da0s1a and da0s1d are inverted. By some > reason someone labelled root as 'd' and home as 'a'. > > Can I just > > bsdlabel -n da0s1 > savedabel.txt > > Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) Why not simply use bsdlabel -e da0s1? 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: nss_ldap and multiple group memberships
Hi, all, On Wed, Feb 24, 2010 at 11:23:11AM +0100, Gerrit Kühn wrote: > Is anyone here using nss_ldap and can successfully get it to work with > multiple group memberships? I would really like to get this to work here, > but I only get the primary group: > > penumbra# id gekueh > uid=1030(gekueh) gid=1012(aei) groups=1012(aei) [r...@devel ~]$ uname -a FreeBSD devel.intern.punkt.de 7.2-RELEASE-p6 FreeBSD 7.2-RELEASE-p6 #0: Mon Feb 22 16:17:54 CET 2010 r...@nanobsd.ka.punkt.de:/var/home/nanobsd/obj/dl320-devel/usr/src/sys/GENERIC amd64 [r...@devel ~]$ pkg_info | grep ldap nss_ldap-1.264_3RFC 2307 NSS module openldap-client-2.4.21 Open source LDAP client implementation pam_ldap-1.8.5 A pam module for authenticating with LDAP [r...@devel ~]$ id uid=10093(ry93) gid=10001(intern) groups=10001(intern),0(wheel) LDAP server is Active Directory on Windows 2003 R2. What precisely do you need? Ah, heck, I'll just attach my config files right away. nss_ldap.conf is just a symlink to ldap.conf. I do not remember where that '?one' came from and what precisely it does. Voodoo I copied from some obscure "Howto", I figure. I'd appreciate some feedback on that part ;-) Best regards, 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 # # nsswitch.conf(5) - name service switch configuration file # $FreeBSD: src/etc/nsswitch.conf,v 1.1.8.1 2009/04/15 03:14:26 kensmith Exp $ # group: cache files ldap hosts: files dns networks: files passwd: cache files ldap shells: files services: compat services_compat: nis protocols: files rpc: files uri ldap://pdc.intern.punkt.de base DC=intern,DC=punkt,DC=de ldap_version 3 binddn *** bindpw *** scope sub idle_timelimit 60 pam_login_attribute msSFU30Name pam_filter objectclass=User pam_password ad nss_map_objectclass posixAccount User nss_map_objectclass posixGroup Group nss_base_passwd ou=Mitarbeiter,dc=intern,dc=punkt,dc=de?one nss_base_group ou=Unixgruppen,dc=intern,dc=punkt,dc=de?one nss_map_attribute uid msSFU30Name nss_map_attribute gecos name nss_map_attribute userPassword unixUserPassword nss_map_attribute homeDirectory unixHomeDirectory nss_map_attribute uniqueMember member nss_map_attribute cn sAMAccountName nss_map_attribute uniquemember msSFU30PosixMember ___ 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: Multi node storage, ZFS
Hi, all, On Wed, Mar 24, 2010 at 11:45:25PM +, Michal wrote: > I am thinking a cheap solution but one that > has IO throughput, redundancy and is easy to manange and expand across > multiple nodes Fast, reliable, cheap. Pick any two. IMHO this is just as true today as it was twenty years ago. 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: gmirror(8) rebuild speed
Hello, On Thu, Apr 22, 2010 at 06:59:54PM +1000, Andrew Reilly wrote: > To make it slower, I assume? When is that a good idea? When the rebuild is bringing your production system to a crawl and you are willing to face the tradeoff - hopefully because you have an additional backup for the worst case. 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"
Bypassing boot0/1/2?
Hi, all, I have two brand new systems on my desk with Adaptec 5404 SAS RAID cards. I booted an install CD from an USB drive and could install on the RAID 10 just finde. Both 7.3 and an 8.0 snapshot from April. Amd64, of course. Now something weird happens when I boot from hard disk. The "boot:" prompt appears to be waiting for me to hit unconditionally. The system does not autoboot by itself. If I install the bootmanager (boot0cfg -B) instead of a standard MBR, the result is the same. The "F1" prompt times out and switches to the next stage, then it's waiting again for me to press a key. When I do that, the audible alarm of the RAID HA goes off and the loading of /boot/loader and the kernel (?) takes "forever" - around five minutes, during which the HA beeps the entire time. Once the FreeBSD boot menu (former "Beastie" menu) appears, everything is silent, again, and the rest of the boot process continues normally. The system, once booted, is running perfectly fine. I tried to replace the first stages of the FreeBSD boot loader with Grub, loading /boot/loader as the next stage - same result. I can boot any current FreeBSD from any external device, normally - but not from the internal RAID volume. As I see this, I could try to skip as much as possible of the standard boot process by using a "dangerously dedicated" disk if that is still supported? Would there be a chance that this might help? We used dedicated disks for years with FreeBSD 2, 3 and 4, but stopped using them around 5, IIRC. Or, if all else fails, I could boot everything up to /boot/loader from a flash module and direct it to the kernel on hard disk. Not pretty, but probably workable. Any suggestions are very welcome. 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"
Documentation of NO_* knobs
Hi, all, is there an exhaustive list of all possible NO_* knobs for make.conf? While experimenting with NanoBSD I found e.g. that the handbook http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html mentions NO_EXAMPLES NO_SYSCONS ... - just two out of many. Yet, these are not in the manpage of make.conf(5) on a 6.3-RELEASE. So, where did the handbook author find them? Thanks, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: Documentation of NO_* knobs
Hello, On Wed, Feb 27, 2008 at 09:18:31AM -0800, Jeremy Chadwick wrote: > I think you're looking for all the WITHOUT knobs in src.conf(5). I'm running RELENG_6_3 on production machines unlikely to change any time real soon. > Note that src.conf(5) does not apply to RELENG_6 or earlier, where the > knobs are named NO_xxx. You can get a list of those from > /usr/share/examples/etc/make.conf. I knew about that file. NO_SYSCONS and NO_EXAMPLES are neither in this one nor in the manpage for make.conf. Yet they are in the handbook example for NanoBSD builds. That's why I'm asking for the "official" exhaustive list. Thanks for taking the time to answer, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3
Hi, all,
On Thu, Jun 05, 2008 at 05:51:05AM -0700, Jeremy Chadwick wrote:
> On Thu, Jun 05, 2008 at 01:03:04PM +0100, Bruce M. Simpson wrote:
> > Jo Rhett wrote:
> >>
> >> I am suggesting that given that the current bug list for 6.3-RELEASE is
> >> both (a) too large and (b) breaks things that work fine in 6.2 ... that I
> >> think pushing 6.2 (the real stable release) into EoL is a bit rushed. I
> >> sympathize with the development costs of maintaining old versions. Again,
> >> I will help in any way I can.
> >
> > I'm sorry to hear about the problems you've been having.
>
> If the exact regression between 6.2 and 6.3 can be tracked down, great.
> If it's in a specific driver, CVS commit logs or cvsweb will come in
> handy. Otherwise, if it's some larger piece of code ("ohai i revamped
> the intrupt handlar!"), chances of finding it are slimmer. I'm a bit
> disappointed that Jo hasn't explicitly mentioned what's broken in 6.3
> that's affecting him, because that might help everyone. Heck, I'll even
> add it to my Commonly reported issue wiki page. PRs would be good, but
> I'll gladly take past mailing list discussions.
Since we, too, use quite a few machines in production, most of
them 6.3 BTW, i spent some time searching the PRs with the
keyword "3ware" and varying combinations of release, severity, etc.
I was not able to find anything with respect to that hardware
that wasn't recorded as early as 6.1. em0 lockups were fixed
around 6.1 for us with Jack Vogels kind assistance (and hardware
provided by us ;-)
Kind regards,
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
[EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
Hello, On Thu, Jun 05, 2008 at 10:33:18AM -0500, Paul Schmehl wrote: > --On Thursday, June 05, 2008 18:39:07 +1000 Peter Jeremy > <[EMAIL PROTECTED]> wrote: > >> On 2008-Jun-04 22:22:33 -0700, Jo Rhett <[EMAIL PROTECTED]> wrote: >>> And please stop with the loaded language. I'm not asking anyone to work >>> for me. I am suggesting that it is perhaps too early to EoL 6.2 because >>> 6.3 isn't ready yet. >> >> So you have stated. When asked to provide evidence to backup that >> statement, you have refused. Since you are the one claiming that >> "6.3 isn't ready yet", the onus is on you to put up or shut up. > > That is a blatant lie. He has stated repeatedly that there are *known* > bugs, complete with bug reports, that are not resolved and that affect the > hardware he uses. So he should at least be able to name the relevant PRs. Or name at least one. Then nobody would complain. But stating "it's all well documented" without providing evidence doesn't help. I for one was not able to find any open PRs that deal specifically with 3ware hardware and 6.3, but not 6.[0-2]. > He has also stated that there is no need for him to > provide further evidence of an already documented bug Agreed, but he should name the PRs he's referring to. You know, my crystal ball is at the shop for a check, and it seems like everybody else's is, too. Kind regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
Hello,
On Sat, Jun 07, 2008 at 01:28:21PM -0700, Jo Rhett wrote:
> In rereading my quotes I may have not been clear on something. The vast
> majority of these bugs have already been fixed. ("not in a state that needs
> help identifying" was what I said trying to cover both that and known bugs
> without a fix yet)
>
> However, the fixes are not available in a -RELEASE version of the operating
> system.
Yes. So what?
Upgrading your systems to 6.3 takes _precisely_ the same amount
of work as upgrading to "6-STABLE as of today 00:00 GMT".
You may want to pick a different point of time, but it really
doesn't matter, because a release _is_ just a CVS branch created
at a certain time.
> This is why EoLing 6.2 and forcing people to upgrade to a release
> with lots of known issues is a problem.
People who have issues with RELENG_6_3 should upgrade to RELENG_6
which is perfectly supported.
Kind regards,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
[EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
Hello, On Sat, Jun 07, 2008 at 03:11:42PM -0700, Jo Rhett wrote: > On Jun 7, 2008, at 1:44 PM, Patrick M. Hausen wrote: >> Upgrading your systems to 6.3 takes _precisely_ the same amount >> of work as upgrading to "6-STABLE as of today 00:00 GMT". > > No, it doesn't. You can get to 6.3 with freebsd-update. And you can stay > patched with freebsd-update on a -RELEASE. For a corporation to choose to > stick with -RELEASE makes perfect sense, and it specifically what the > -RELEASE versions were intended for. Correct, that's why we are running RELENG_6_3 on ~40 machines. >> People who have issues with RELENG_6_3 should upgrade to RELENG_6 >> which is perfectly supported. > > I'm sorry, but you clearly don't run RELENG_6 on anything. I run it on two > home computers, and grabbing it on any given day and trying to run with it > in production is insanity. That's not true. I'm running FreeBSD since 1994 and I've run RELENG_N in production at various stages including N = 3, 4, 5 and 6. > Lots and lots of things are committed, > reverted, recommitted, reverted and then finally redesigned. Each of those > steps are often committed to the source tree. Big changes that affect various parts of the system are announced by HEADS UP messages on the -stable mainling list. And by naming "today 00:00" I did not mean to suggest an _arbitrary_ state of the source tree but one you are to _pick_ based on commits and mailing list information. For example, when Jack comitted his fixes for em(4), we set the checkout date to just past he did precisely that. cvsup, make world, reboot, test (!), rollout ... I have never ever had a single problem caused by running RELENG_N. We changed that only because as the number of machines increases it pays to run the same software on all of them, and "RELEASE" provides a convenient (!) reference point for that. Yet, if I were affected by a particular bug in RELENG_6_3, I would simply pick my own later reference point at which the bug is fixed. Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
dhclient and resolv.conf.sav
Hello, we have been bitten by something that obvoiusly is a feature, not a bug, but I do not quite understand the intentions and reasoning behind it. I have a host with manual interface and resolver configuration and an additional interface that should get it's IP address via DHCP. But only it's IP address and netmask, nothing else. The DHCP server used hands out only IP addresses/netmasks, no domain-name-servers, domain-name, etc. configured. Yet, if there happens to exist a /etc/resolv.conf.sav file, every renewal of the lease by dhclient overwrites the contents of /etc/resolv.conf with those of resolv.conf.sav. In my particular case the .sav file contained an internal nameserver that was used when I initially set up the host in the lab. This entry was of no use to the server after it had been deployed in our datacenter. Can anyone shed some light on the intended mechanism? Studying the dhclient-script was not too helpful, either. Thanks, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Unattended install w/ serial console?
Hello,
I've managed to get sysinstall to do a completely unattended
install via DHCP/PXE and reboot the system into a state
where it will be possible to login via SSH.
So far, so good. Unfortunately This works for VGA consoles only.
If the server in question has got a serial console, I get
this prompt:
/stand/sysinstall running as init on serial console
These are the predefined terminal types available to
sysinstall when running stand-alone. Please choose the
closest match for your particular terminal.
1 .. Standard ANSI terminal.
2 .. VT100 or compatible terminal.
3 .. FreeBSD system console (color).
4 .. FreeBSD system console (monochrome).
5 .. xterm terminal emulator.
Your choice: (1-5)
After entering (e.g.) 2, the complete install runs just fine
without any more operator assistance.
The code responsible for this seems to be in
/usr/src/usr.sbin/sysinstall/termcap.c, line 92 ff.:
if (!OnVTY || (stat < 0)) {
if (!term) {
char *term, *termcap;
prompt_term(&term, &termcap);
with prompt_term() being the function that displays the
above menue.
Term is set at the beginning of set_termcap(), line 80:
term = getenv("TERM");
OK, here's the question: how do I set environment variables
in install.cfg or some other file in my mfsroot?
TERM=vt100
in install.cfg did not make it to sysinstall, would have been too
simple, I guess ;-)
Thanks a lot,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
[EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusio
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: Deprecating base system ftpd?
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: Does / Is anyone maintaining CVS for FreeBSD?
Hello, Am 03.01.2013 um 16:36 schrieb Eitan Adler : > 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: Does / Is anyone maintaining CVS for FreeBSD?
Hi, all, Am 03.01.2013 um 19:21 schrieb Matthew Seaman : > 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?
Hi, all, Am 04.01.2013 um 10:42 schrieb Chris Rees : > 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: svn - but smaller?
Hi, all, Am 24.01.2013 um 15:20 schrieb Gyrd Thane Lange : > 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 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"
Poudriere questions
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
Hello, Am 20.02.2013 um 18:07 schrieb Guido Falsi : > 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
Hi, Guido,
Am 20.02.2013 um 18:28 schrieb Guido Falsi :
>> 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: Poudriere questions
Hi! Am 21.02.2013 um 11:44 schrieb Guido Falsi : > 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
Hi, all, Am 21.02.2013 um 09:54 schrieb Guido Falsi : > 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
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
Good morning,
Am 20.02.2013 um 18:28 schrieb Guido Falsi :
> 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"
Re: svn - but smaller?
Hi, Am 09.04.2013 um 17:05 schrieb Patrick M. Hausen : > 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?
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: [SOLVED][BUG??] Unattended install using bsdinstall and ZFS
Hi, Claus,
> Am 29.05.2015 um 19:17 schrieb Claus Andersen :
>
> 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:"
echo " ansi Standard ANSI terminal"
echo " vt100VT100 or compatible terminal"
echo " xtermxterm terminal emulator (or compatible)"
echo " cons25w 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: Swap Questions
HI! > Am 14.08.2015 um 15:15 schrieb Tim Daneliuk : > > 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"
Memory error logged in /var/log/messages
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 acpi
Re: issue upgradning src
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"
Re: Binary update to -STABLE? And if so, what do I get?
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: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)
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"
NVME aborting outstanding i/o
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: NVME aborting outstanding i/o
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"
Re: NVME aborting outstanding i/o
> 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
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"
Rare NVME related freeze at boot (was: Re: NVME aborting outstanding i/o)
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: Rare NVME related freeze at boot (was: Re: NVME aborting outstanding i/o)
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"
Re: NVME aborting outstanding i/o and controller resets
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: N
Re: NVME aborting outstanding i/o and controller resets
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
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
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
> 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
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
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: ZFS...
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: ZFS...
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...
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: fsck vs zvol
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: RELENG_10 to RELENG11 buildworld no possible ?
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: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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: LUA ERROR: memory allocation error: block too big
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: ntpd on a NAT gateway seems to do nothing
Hi, all! On Tue, Jul 24, 2007 at 04:00:08PM +0100, Pete French wrote: > Yes, I discovered the UDPness of it last night and went > through the rules again. I am pretty sure they are correct (or > at least I cannot see anything wrong). I would assume that ntpdate > also uses UDP - and using that I can see all these servers ? I would try and run # tcpdump -n -i host in a separate window and compare the output when running ntpdate vs. starting ntpd. HTH, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: problems with Hitachi 1TB SATA drives
Hi, all! > To add fuel to the fire, Seagate *again* sent me a refurbished drive > (and I used their advanced replacement program), which has sat in a box > unopened since received. I ended up buying two WD 500GB drives to > replace the single Seagate; one of the drives is used for nothing other > than doing incremental dump(8)s of the other (and the main OS drive). > If either of those 500GB drives fail, I'll be able to recover in some > way somewhat painlessly. We mirror all servers now, given the low prices of S-ATA disks and gmirror(8). Of yourse this is not backup, but it can be a foundation for backup ... > * All this leads me to the topic of backups. Hard disks are growing in > capacity at a rate which the backup industry cannot follow. It's > getting to the point where you have to buy hard drives to back up the > data on other hard drives, but anyone with half a brain knows RAID is > not a replacement for backups. RAID or mirroring gives you availability and resiliency for single disk failures (at least). Backup should give you an archive of file versions reaching back a certain amount of time to restore slowly corrupted data. The backup should be on a server and/or media different than the backed up one. So we are using a system with two 2 TB RAID 5 volumes that serves as an Amanda backup server. Backups are stored in vtapes on the disks (read: directories) managed by Amanda. Since there is no way that a slow filesystem corruption on one of the clients could affect the backup server, I'd call this a reasonable solution to the capacity problem. If the backup server goes up in smoke, it is highly unlikely that we have a severe need of a restore at the very same instant. We cannot carry the tape magazines around anymore, so if the data centre goes up in flames, we are fooled. Eventually a second data centre, second backup server, fast connection and rsync(1) will do the trick. Which leads us to private backups: > There is presently nothing __affordable on the consumer market__ which > makes backing up 300GB+ of data easy. RAID1 USB2 case for S-ATA disk: USD 400 2 WD RE2 500 GB drives: USD 600 Regular incremental backups:priceless ;-)) Again I'm just doing versioned backups to redundant disks. When I'm not doing backups, I'm not connecting the volume to my Mac, so software failure, worms, whatever, ... cannot by accident destroy the backups. Now, long term archiving ... that's another interesting topic. Kind regards, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: pam_group vs. multiple group lines
Hi, all! On Wed, Aug 22, 2007 at 09:53:42AM +0200, Ulrich Spoerlein wrote: > On 8/22/07, Chuck Swiger <[EMAIL PROTECTED]> wrote: > > On Aug 21, 2007, at 2:02 PM, Richard Foulkes wrote: > > > Ok, so how are you supposed to control membership of the wheel > > > group via ldap? Ok, you COULD remove the local wheel entry in /etc/ > > > group, but this would probably be a bad idea if the ldap server > > > were unavailable. > > > > You've aptly summarized my thoughts on the matter-- I would not rely > > on LDAP to provide information about root or the wheel group. > > That is exactly the gist of my question. Of course I know that a group > oneliner is the way to go. However, I saw people suggest splitting > groups into multiple lines, if the lines are too long or too many > groups per line (something to do with the /etc/group parser, I guess). > > Anyway, I want the LDAP groups to *augment* system groups. Removing > wheel from /etc/group and relying on a complex network service > not funny. I've only followed this thread loosely, so I apologize if this has already been stated or if I'm completely missing the point, but here goes: We do not use LDAP yet, but have been using NIS in our internal office network for years. If you use the magic "+" token to merge your NIS database with the static files for passwd and group information, then _if_ the group entry in the static file does not contain any users _then_ the information from NIS is merged in So you can keep a "wheel" group around as the _primary_ group for root, toor, whatnot ... and all the additional members that have "wheel" as an auxiliary group come from NIS. Possibly this works for LDAP, too? IMHO at least it should ;-)) Kind regards, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: [OT] Which one is best MTA for me?
Hi! > Recently I am considering to move to another MTA. At one time I was > wondering what mail server big ISP are running. I can't decide postfix > or qmail. > > Which one is best MTA for me? Sendmail? It's the best MTA for me ;-) Maybe your question could be answered in a more helpful way, if you stated - which MTA you are currently using - what you don't like about it, so you want to switch We are an ISP and we run Sendmail. Works great. I don't like qmail, because for me it's architecture is even more arcane than Sendmail's. And it doesn't log all information Sendmail does - which is important for us when tracing "lost" mails. (remote MTA queue ID, for example) I hear lots of good things about postfix, but switch for the sake of switching? I already have enough work ;-) Kind regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: [OT] Which one is best MTA for me?
Hi! On Tue, Aug 28, 2007 at 01:58:36PM -0500, Eric wrote: > theres more interesting facts about DJBs software on the maradns homepage if > anyone is interested. Jehova! Jehova! DJB's software is guaranteed bug free SCNR, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: rm(1) bug, possibly serious
Hello! On Tue, Sep 25, 2007 at 11:54:14PM +0200, Oliver Brandmueller wrote: > In sh: > > $ which rm > /bin/rm > $ cd /tmp > $ mkdir -p foo/bar > $ cd foo/bar > $ rm -rf ../ > rm: ../: Invalid argument $ pwd /tmp $ ktrace -i /bin/sh $ which rm /bin/rm $ mkdir -p foo/bar $ cd foo/bar $ rm -rf ../ rm: ../: Invalid argument $ rm -rf ../ $ ktrace -C ... 35356 rm NAMI "../" 35356 rm RET rmdir -1 errno 22 Invalid argument ... 35488 rm NAMI "../" 35488 rm RET lstat -1 errno 2 No such file or directory ... HTH, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@)
Mornin', On Tue, Dec 04, 2007 at 05:23:15PM -0800, Garrett Cooper wrote: > Instead of asking all of the questions on a list, why not just direct > people to input information via a webpage? Seems to be a bit more effective > / less traffic than posting results to multiple lists.. Instead of sending the filled in questionaire to the list why not simply send it back to the original author as doubtlessly intended ...? ;-) Kind regards, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]"
Re: Is some combination of gmirror, md file systems, snapshots and, maybe, quotas considered harmful?
Hello, On Sun, Mar 22, 2009 at 04:31:56AM -0500, Scott Lambert wrote: > > I added this machine to our AMANDA setup on March 13, 2009. > > > > I noticed that mksnap_ffs was running on /home, cpu time used: 0:00.77, > > as things began to circle the drain. That was about 30 minutes after > > the dump attempt had been started by AMANDA. There were many processes > > waiting in state D. This time I did a reboot -n -q and the box rebooted > > but was still fscking when I got to the office. > > > > # ls -l /home/.snap > > -r 1 root operator 117285093376 Mar 20 03:18 dump_snapshot Did you compile the Amanda port with the "-L" option to dump enabled? Don't ;-) 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"
