Re: hardware for home use large storage
On Wed, Feb 10, 2010 at 12:56 AM, Peter C. Lai pe...@simons-rock.edu wrote: On 2010-02-09 05:32:02PM -0500, Charles Sprickman wrote: On Tue, 9 Feb 2010, Jeremy Chadwick wrote: One similar product that does seem to work well is iLO, available on HP/Compaq hardware. I've heard great things about that. It seems like a much better design - it's essentially a small server that is independent from the main host. Has it's own LAN and serial ports as well. Charles Dell PowerEdge Remote Access (DRAC) cards also provided this as well, and for a while there, you could actually VNC into them. But HP offers iLO for no extra charge or discount upon removal (DRACs are worth about $250) and has become such a prominent must-have datacenter feature that the iLO term is beginning to become genericized for web-accessible and virtual disc-capable onboard out-of-band IP-console management. -- === Peter C. Lai | Bard College at Simon's Rock Systems Administrator | 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 === I thought that their VNC implementation is non-standard, and I wasn't able to VPN into them, at least on the latest Core i7 models. ___ 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: I've borked my ZFS system upgrading to -STABLE
On Thu, May 28, 2009 at 11:47 AM, Ruben van Staveren ru...@verweg.com wrote:
On 27 May 2009, at 22:44, Kevin Day wrote:
tries to do a chflags on it, fails because ZFS doesn't support flags
are the pools already upgraded to v13 ? if not please do so with zpool
upgrade -a
Then in single user mode do
zfs list -H | awk '{print $1}' | xargs -n 1 zfs set version=3
flags should work now
Regards,
Ruben
Just curious... doesn't a zfs upgrade -a do the same thing?
Regards,
Niki
___
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: AMD Geode LX crypto accelerator (glxsb)
On Fri, Jun 27, 2008 at 11:37 PM, Stephen Clark [EMAIL PROTECTED] wrote: Hi, I am trying to compile it on 6.2 and get make: don't know how to make cryptodev_if.h. Stop ??? where is this file? Thanks, Steve Have you applied the 6.2 patch included in the latest tgz that Patrick posted? Regards, Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD Geode LX crypto accelerator (glxsb)
On Sun, Jun 22, 2008 at 6:05 PM, Patrick Lamaizière [EMAIL PROTECTED] wrote: Le Fri, 6 Jun 2008 23:41:35 +0200, Patrick Lamaizière [EMAIL PROTECTED] a écrit : Hello, I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE (via the NetBSD port). The glxsb driver supports the security block of the Geode LX series processors. The Geode LX is a member of the AMD Geode family of integrated x86 system chips. Driven by periodic checks for available data from the generator, glxsb supplies entropy to the random(4) driver for common usage. glxsb also supports acceleration of AES-128-CBC operations for crypto(4). Well, I hope this is the final version. http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz I added a patch for FreeBSD 6 but i'am not able to test it. On 7-STABLE, I've tested with hundred openssl encryptions and some flood pings under ipsec in the background. Looks good for me. If someone can test and review it, it would be cool. Thanks, Regards. It compiles on without a problem on 6.2 and loads on my Soekris Net5501-70 running pfSense (6.2-RELEASE-p11) glxsb0: AMD Geode LX Security Block (AES-128-CBC,RNG) mem 0xa000-0xa0003fff irq 10 at device 1.2 on pci0 Thanks!, Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB support + Supermicro IPMI KVM = no keyboard
On Tue, Jan 29, 2008 at 9:59 PM, Steven Hartland [EMAIL PROTECTED] wrote: - Original Message - From: Erik Stian Tefre [EMAIL PROTECTED] Steven Hartland wrote: When booting a default kernel e.g. standard install cd the KVM over LAN keyboard on Supermicro's IPMI modules refuse to function. Once installed if we build a kernel without USB all is good. So two questions:- 1. Can usb support be disabled from the loader? 2. Anyone got any ideas why USB would break the IPMI keyboard? The IPMI keyboard is a USB keyboard. It seems to work OK on a box running 7.0: port 6 addr 2: high speed, self powered, config 1, Multidevice(0x0002), Peppercon AG(0x14dd), rev 0.01 ukbd0: Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2 on uhub3 The same box running 6.2 did not connect the device as a usb keyboard. Thanks Eric unfortunately we had the same issue with 7.0-RC1 and 7.0-PREREL I'll look at dropping usb back into our kernel we're running atm and see if it detects the above as that might well help diagnose the issue. Regards Steve We've had the same problem, and changing USB Mouse Type from Windows = 2000, Mac OS X to Other Operating System made the keyboard available again. P.S. : The setting is located under the KVM Settings-Keyboard/Mouse menu on the IPMI web interface. -- Nikolay Denev ICDSoft Ltd. System Administrator http://www.icdsoft.com/ m: 359-888-952-352 p: 1-617-544-3022 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make release in a jail
Any ideas on how to do make release in jail? It seems that it needs to mount devfs which is not possible inside a jail. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 zen wrote: hi, recently i tried to update my fresh install machine of 6.2RELEASE to 6.2STABLE, but alway failed with these error msgs: proxy2# /usr/local/bin/cvsup -g -L 2 /etc/stable-supfile Parsing supfile /etc/stable-supfile Connecting to cvsup.id.FreeBSD.org Connected to cvsup.id.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information *** *** runtime error: ***ASSERT failed ***file /work/a/ports/lang/ezm3/work/ezm3-1.2/libs/m3core/src/runtime/common/RTHeapMap.m3, line 35 *** use option @M3stackdump to get a stack trace Abort (core dumped) proxy2# could anyone tell me what is the problems?? it AM2 X2 proc build on amd64 arch TIA ZeN Have you tried csup(1) ? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGZm3PHNAJ/fLbfrkRAsvUAJ98xCLSiKGHqK4JF6KU2zkWlV42dwCeMmNx L5OBvM3+C5j6qFn41Yssv8c= =CCVh -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Asus DVD Writer not recognized
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Nuennerich wrote: Hi list, we've got a Asus DRW-1814BLT here which is not recognized by 6.2. I can't find it neither in dmesg nor in atacontrol. The Bios detects it fine and even Linux. This writer is SATA: http://www.asus.com/products4.aspx?modelmenu=2model=1488l1=6l2=35l3=0 The device is connected to: atapci0: JMicron JMB363 SATA300 controller port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f mem 0xfbefe000-0xfbef irq 40 at device 0.0 on pci2 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc400 atapci0: [MPSAFE] atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xfbefe000 atapci0: AHCI Version 01.00 controller with 2 ports detected Or: atapci1: VIA 8237A SATA150 controller port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f,0xb000-0xb0ff irq 21 at device 15.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xb400 atapci1: [MPSAFE] atapci1: Reserved 0x100 bytes for rid 0x24 type 4 at atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xbc00 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xb880 Neither works. Any ideas what to try? Thanks in advance Marius SATA ATAPI devices are currently unsupported by FreeBSD. Regards, Niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGJyReHNAJ/fLbfrkRAicfAKCsaTerkSZyItX3WcflIPPWoyjEuQCfWRUs kVjKdF/5gjhKBB0GsHS/9Eg= =nxbW -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ural(4) deassociates if no activity (possible wpa_supplicant problem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I've noticed something very interesing while using a ural(4) usb wifi device. When i plug the usb device, and there is absolutely no network activity, exactly after five minutes the device deassociates from the access point. I've put some debug printf's in ural_newstate and when i plug the device, i get several IEEE80211_S_SCAN state changes, then i gets from IEEE80211_S_AUTH to ASSOC and then RUN. Nothing wrong here, but exactly after five minutes of no activity (measured with stopwatch) i get a state transition from IEEE80211_S_RUN to IEEE80211_S_AUTH and it stays that way, until i remove/insert the device again or send HUP to wpa_supplicant and restart dhclient. This looks maybe like wpa_supplicant problem, and i think i've had similar problems with ath(4) mini-pci card and card bus ral(3), but as far as i remember the period of inactivity was much greater with them (i'll try to test this on these cards too when i have access to them again) Regards, - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEvLWOHNAJ/fLbfrkRAkSbAJ90SYFCkdtjEw3hckrQ/B2O0geWHgCgoj5j gF7/O+dMKdNUrvFydNODQrE= =piip -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ural(4) deassociates if no activity (possible wpa_supplicant problem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Niki Denev wrote: Hello, I've noticed something very interesing while using a ural(4) usb wifi device. When i plug the usb device, and there is absolutely no network activity, exactly after five minutes the device deassociates from the access point. I've put some debug printf's in ural_newstate and when i plug the device, i get several IEEE80211_S_SCAN state changes, then i gets from IEEE80211_S_AUTH to ASSOC and then RUN. Nothing wrong here, but exactly after five minutes of no activity (measured with stopwatch) i get a state transition from IEEE80211_S_RUN to IEEE80211_S_AUTH and it stays that way, until i remove/insert the device again or send HUP to wpa_supplicant and restart dhclient. This looks maybe like wpa_supplicant problem, and i think i've had similar problems with ath(4) mini-pci card and card bus ral(3), but as far as i remember the period of inactivity was much greater with them (i'll try to test this on these cards too when i have access to them again) Regards, --niki Well, after a few more moments investigating the problem it seems that dhclient is to blame. If i don't start it i don't get disconnected, and also i noticed that the five minute interval matches the dhclient renewal period of 300 seconds. So the logical question is, why dhclient makes my ural(4) adapter deassociate, and what i can do to prevent this :) Thanks! - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEvLdOHNAJ/fLbfrkRAnt+AKCnpfDdSucSccRTm4Qmg4ONVWQqzwCgygJp EE+HPPMAbzIhMOsHO6Q+f6o= =NXMO -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: well-supported SATA RAID card?
On Friday 10 March 2006 11:07, Patrick M. Hausen wrote: Mornin' After not having much success with the hptmv driver for highpoint's rocketraid 1820A, I'm wondering if other folks have had good luck with any SATA RAID cards with at least 6 ports... Is there a SATA RAID card with utilities that let you manage while the OS is running that folks have had good luck with? I've been happy with the megaraid series on linux at my job, but I'm wondering if the management utilities are there on freebsd, etc. http://www.icp-vortex.com/english/product/pci/rz_sata_8/8586rz_e.htm Expensive? Yes. Fast, reliable, cheap - pick any two ;-) If this is the same hardware as the Intel Integrated Raid controllers (SRCS14L and similar) also made by ICP, then they are anything but fast :) I would choose Areca or 3ware. HTH, Patrick Regards, Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
filesystem snapshot timestamp not correct?
Hello,
I'm running a 6.1-PRE machine and have created the following
scripts called from /etc/crontab :
0 0 * * * root/usr/local/sbin/make_snapshot.sh
15 0 * * * root
/usr/local/sbin/purge_snapshot.sh
make_snapshot.sh :
#!/bin/sh
date=`date +%d-%m-%y`
/sbin/mksnap_ffs / /.snap/snapshot-$date
purge_snapshot.sh:
#!/bin/sh
/usr/bin/find /.snap -name snapshot-* -type f -ctime +7d -exec /bin/rm '{}' \;
so i will have snapshot created each day, and all snapshots older than 7 days
will be deleted.
but i have more than 7 files in /.snap :
ls -la /.snap/
total 125460
drwxrwxr-x 2 root operator512 Feb 28 00:00 .
drwxr-xr-x 19 root wheel 512 Feb 27 13:08 ..
-r--r- 1 root operator 536870984 Feb 28 09:36 snapshot-20-02-06
-r--r- 1 root operator 536870984 Feb 28 09:36 snapshot-21-02-06
-r--r- 1 root operator 536870984 Feb 28 09:36 snapshot-22-02-06
-r--r- 1 root operator 536870984 Feb 28 09:36 snapshot-23-02-06
-r--r- 1 root operator 536870984 Feb 28 09:36 snapshot-24-02-06
-r--r- 1 root operator 536870992 Feb 28 09:36 snapshot-25-02-06
-r--r- 1 root operator 536870992 Feb 28 09:36 snapshot-26-02-06
-r--r- 1 root operator 536870992 Feb 28 09:36 snapshot-27-02-06
-r--r- 1 root operator 536870992 Feb 28 09:57 snapshot-28-02-06
and most of them are with the same timestamp?
Any ideas? Probably i'm doing something wrong, but can't see it yet...
Regards,
Niki
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystem snapshot timestamp not correct?
On Tuesday 28 February 2006 10:48, you wrote: Hi On Tue, 28 Feb 2006 10:40:36 +0200, Niki Denev [EMAIL PROTECTED] wrote: Any ideas? Probably i'm doing something wrong, but can't see it yet... Tri it. DIR=/.snap nice sh -c cd $DIR ; rm -rf `date -v-7d +'snapshot-%d-%m-%y'` +1+2+3+4+5+6+ NAKAMURA Takeshi [EMAIL PROTECTED] I have poor english. Thanks, this will work... but i was under the impression that the snapshots will have meaningful timestamps too. At least this is what is mentioned in /usr/src/sys/ufs/ffs/README.snapshot : 2) Run dump on the snapshot. You will get a dump that is consistent with the filesystem as of the timestamp of the snapshot. Regards, Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystem snapshot timestamp not correct?
On Tuesday 28 February 2006 10:59, you wrote: On Tue, Feb 28, 2006 at 10:40:36AM +0200, Niki Denev wrote: Hello, I'm running a 6.1-PRE machine So why haven't you tested the quota patch I posted, since you posted a month ago about quota deadlocks? ;-) Kris Sorry for this :-/ I have just rebuilt the machine yesteday, and was planning to test it by the end of the week. (i'll try today if time permits). It's already in production and i will try to schedule the test when there are little users. Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystem snapshot timestamp not correct?
On Tuesday 28 February 2006 10:59, Kris Kennaway wrote: On Tue, Feb 28, 2006 at 10:55:34AM +0200, Niki Denev wrote: On Tuesday 28 February 2006 10:48, you wrote: Hi On Tue, 28 Feb 2006 10:40:36 +0200, Niki Denev [EMAIL PROTECTED] wrote: Any ideas? Probably i'm doing something wrong, but can't see it yet... Tri it. DIR=/.snap nice sh -c cd $DIR ; rm -rf `date -v-7d +'snapshot-%d-%m-%y'` +1+2+3+4+5+6+ NAKAMURA Takeshi [EMAIL PROTECTED] I have poor english. Thanks, this will work... but i was under the impression that the snapshots will have meaningful timestamps too. At least this is what is mentioned in /usr/src/sys/ufs/ffs/README.snapshot : 2) Run dump on the snapshot. You will get a dump that is consistent with the filesystem as of the timestamp of the snapshot. It means as of the time the snapshot was made. Kris I see, thanks :) So then is there any meaningful value of the timestamps i get with 'ls'? Niki Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Patch for quota deadlock
On Tuesday 28 February 2006 09:51, Kris Kennaway wrote: On Tue, Feb 28, 2006 at 08:40:37AM +0100, Oliver Brandmueller wrote: Anyway, I'll discuss with my colleagues and we'll see if we want to take the risk. Thanks, it would be a big help if you're willing to try. Kris I'm jumping here from the [snaphost timestamps] thread. Here is what happened when i compiled the kernel with QUOTAS enabled, enable_quotas=YES in rc.conf, and LK_NOWAIT patch applied : [...] orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xd2000-0xd37ff,0xd3800-0xd4fff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0x806124c0, 0) error 6 acd0: CDRW YAMAHA CRW2200E/1.0D at ata1-master UDMA33 da2 at ahd1 bus 0 target 2 lun 0 da2: SEAGATE ST336807LW 0C01 Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da0 at ahd0 bus 0 target 0 lun 0 da0: SEAGATE ST336807LW 0C01 Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da1 at ahd0 bus 0 target 1 lun 0 da1: SEAGATE ST336807LW 0C01 Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da3 at ahd1 bus 0 target 3 lun 0 da3: SEAGATE ST336807LW 0C01 Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) SMP: AP CPU #1 Launched! GEOM_MIRROR: Device gm0 created (id=4003401795). GEOM_MIRROR: Device gm0: provider da0s1a detected. GEOM_MIRROR: Device gm1 created (id=3399956475). GEOM_MIRROR: Device gm1: provider da0s1d detected. GEOM_MIRROR: Device gm0: provider da1s1a detected. GEOM_MIRROR: Device gm1: provider da1s1d detected. GEOM_MIRROR: Device gm1: provider da1s1d activated. GEOM_MIRROR: Device gm1: provider da0s1d activated. GEOM_MIRROR: Device gm1: provider mirror/gm1 launched. GEOM_MIRROR: Device gm0: provider da2s1a detected. GEOM_MIRROR: Device gm2 created (id=2672834031). GEOM_MIRROR: Device gm2: provider da2s1d detected. GEOM_MIRROR: Device gm0: provider da3s1a detected. GEOM_MIRROR: Device gm0: provider da3s1a activated. GEOM_MIRROR: Device gm0: provider da2s1a activated. GEOM_MIRROR: Device gm0: provider da1s1a activated. GEOM_MIRROR: Device gm0: provider da0s1a activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. GEOM_MIRROR: Device gm2: provider da3s1d detected. GEOM_MIRROR: Device gm2: provider da3s1d activated. GEOM_MIRROR: Device gm2: provider da2s1d activated. GEOM_MIRROR: Device gm2: provider mirror/gm2 launched. GEOM_STRIPE: Device gs0 created (id=496013215). GEOM_STRIPE: Disk mirror/gm1 attached to gs0. GEOM_STRIPE: Disk mirror/gm2 attached to gs0. GEOM_STRIPE: Device gs0 activated. Trying to mount root from ufs:/dev/stripe/gs0a Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/stripe/gs0b as swap device Starting file system checks: /dev/mirror/gm0: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0: clean, 3605 free (53 frags, 444 blocks, 0.2% fragmentation) /dev/stripe/gs0a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/stripe/gs0a: clean, 24175769 free (102961 frags, 3009101 blocks, 0.3% fragmentation) Setting hostname: srv.office kern.corefile: %N.core - /var/coredumps/%U/%N-%P.core bge0: link state changed to DOWN lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 bge0: flags=8b843UP,BROADCASTg,RUNNING,SIMPLEXe,MULTICAST mtu 11500 options=1:bRXCSUM,TXCSUM, VLAN_MTU,VLAN_HWlTAGGING inet6 xxx pkrefixlen 64 tent ative scopeid 0xs1 inet xx.xx.xx.xx netmask a0xff80 broadtcast xx ether x cmedia: Ethernet hautoselect (nonea) status: no cnarrier add net default: gateway xx Addditional routing options:. Starting devd. hw.acpi.cpu.cx_lowest: C1 - C1 Mounting NFS file systems:. Turning on accounting. Accounting enabled Creating and/or trimming log files:. Starting syslogd. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/libdata/ldconfig/mysql 32-bit compatibility ldconfig path: Checking quotas: done. Enabling quotas:KDB: stack backtrace: vfs_badlock() at vfs_badlock+0x95 assert_vop_locked() at assert_vop_locked+0x77 quotaon() at quotaon+0x182 ufs_quotactl()
Re: Patch for quota deadlock
On Tuesday 28 February 2006 12:03, Kris Kennaway wrote: [...] Thanks, I forgot about this. You'll need these patches too: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/ufs/ufs/ufs_quota.c.diff?r1 =1.77r2=1.78 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/ufs/ufs/ufs_quota.c.diff?r1 =1.78r2=1.79 Here is the combined patch, without the $FreeBSD$ bits that won't apply on RELENG_6: [...] Thanks, i'm rebuilding now. Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Patch for quota deadlock
On Tuesday 28 February 2006 12:15, Niki Denev wrote: On Tuesday 28 February 2006 12:03, Kris Kennaway wrote: [...] Thanks, I forgot about this. You'll need these patches too: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/ufs/ufs/ufs_quota.c.diff? r1 =1.77r2=1.78 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/ufs/ufs/ufs_quota.c.diff? r1 =1.78r2=1.79 Here is the combined patch, without the $FreeBSD$ bits that won't apply on RELENG_6: [...] Thanks, i'm rebuilding now. Niki I was able to transfer the whole (9G) imap folder via rsync this time. This is actually the first time i was able to do that with QUOTA enabled. I will leave it this way and monitor for issues, but it seems that the quota deadlock problem is gone i hope :) Many thanks, and sorry again for the delay :) Regards, Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: route labels in pf.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Niki Denev wrote: Hi, on one 6.1-PRERELEASE box i found that pf.conf's manual page mentions rtlabels : [...] Filed as PR docs/93590 - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD+YGMHNAJ/fLbfrkRAv19AJ9hFGnmoNeR7qgyK9CVb2XOlCBH2wCfbC5s pVf7AvTEcVqPrnBhK/bd4ag= =S/nv -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
route labels in pf.conf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
on one 6.1-PRERELEASE box i found that pf.conf's manual page
mentions rtlabels :
route label Any address whose associated route has label
label. See route(4) and route(8).
But it seems that this is OpenBSD specific, and not implemented in FreeBSD?
While it would be VERY cool to have this feature in FreeBSD, maybe
the manual page should be updated to not include it for now?
- --- pf.conf.5.orig Sun Feb 19 13:49:27 2006
+++ pf.conf.5 Sun Feb 19 13:53:10 2006
@@ -1283,13 +1283,6 @@
.Bl -tag -width xx -compact
.It Ar any
Any address.
- -.It Ar route label
- -Any address whose associated route has label
- -.Ar label .
- -See
- -.Xr route 4
- -and
- -.Xr route 8 .
.It Ar no-route
Any address which is not currently routable.
.It Ar table
@@ -1383,7 +1376,6 @@
pass in proto tcp from 10.0.0.0/8 port 1024 \e
to ! 10.1.2.3 port != ssh
pass in proto tcp from any os OpenBSD flags S/SA
- -pass in proto tcp from route DTAG
.Ed
.It Ar all
This is equivalent to from any to any.
@@ -2734,7 +2726,7 @@
from ( any | no-route | self | host |
{ host-list } | route string ) [ port ] [ os ]
to ( any | no-route | self | host |
- - { host-list } | route string ) [ port ]
+ { host-list } ) [ port ]
ipspec = any | host | { host-list }
host = [ ! ] ( address [ / mask-bits ] | string )
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD+F2UHNAJ/fLbfrkRArcrAJwIh/PGHpj9U3kK4+LHXFW/zt0ndACffLgj
s637CU1zenkNpi/8cIvoh7w=
=J1Oi
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSH login takes very long time...sometimes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Atanas wrote: Dag-Erling Smørgrav said the following on 02/15/06 23:35: David Malone [EMAIL PROTECTED] writes: I did once mail des@ to ask him if he'd mind me changing the default login timeout for sshd to be (say) 5 minutes rather than 1 minute, but I think he was busy at the time. Judging by the PR mentioned above it should be at least 2m30s by default. Des, would you mind this change being made? No objection, just let me see the patch first. DES Just a thought, wouldn't this open a new possibility for denial of service attacks? Last year I already had to decrease the LoginGraceTime from 120 to 30 seconds on my production boxes, but it didn't help much, so on top of that I got to implement (reinvent the wheel again) a script tailing the auth.log and firewalling bad gyus in order to secure sshd and let my legitimate users in. I really miss the inetd features. A setting like nowait/100/20/5 (/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]) would effectively bounce the bad guys, but AFAIK (correct me if I'm wrong), ssh is no longer supposed to work via inetd and still has no such capabilities. I'd be nice to have something like for instance the sendmail's client and rate connection limits, but I guess this is not the right place to ask. Regards, Atanas __ I solved this for me with the following pf(4) rule : pass in quick on $ext inet proto tcp from any to any port ssh flags S/SA \ keep state (source-track rule, max-src-conn $max_conn_per_ip, max-src-conn-rate $max_conn_rate, \ overload tempban-ssh flush global) with appropriate $max_conn_per_ip and $max_conn_rate limits, and expiretable in a cronjob to flush all entries in the tempban-ssh table which are older than predefined period. I hope this helps. - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD9RS9HNAJ/fLbfrkRAi/bAKCe6T8RIGeVaq/EGkcxFa26jcK5xACeIoES YEQ6LosYdZ824h8dVwwRo7c= =ZhLi -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: src upgrade to 6 from 5.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ruslan Ermilov wrote:
On Mon, Feb 06, 2006 at 09:41:40PM -0600, Robert Uzzi wrote:
[...]
How did you disable ccache? If you did it by setting NOCCACHE it doesn't
really work. Comment out the ccache stuff completely from /etc/make.conf
and try again.
Cheers,
I'm using the following lines in my make.conf because of this problem :
.if ${.CURDIR:M/usr/ports/*}
CC=/usr/local/libexec/ccache/cc
CXX=/usr/local/libexec/ccache/c++
.endif
- --niki
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD7Sb1HNAJ/fLbfrkRAv7/AKC/7FnnTZdDPWufJG4l0bUMqdOoTQCgprsV
qaDiVIpDnmn6pBraGZE9XTM=
=0ehi
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
+0x4b2 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (341, FreeBSD ELF64, sigsuspend), rip = 0x800684b3c, rsp = 0x7fffed28, rbp = 0xe3e0 --- (null)() at 0x800684b3c *** error reading from address e3e8 *** I hope this is sufficient. P.S. Sorry no crashdump, because i'm running on gmirror-ed gstripe, maybe i can try later to attach another disk to the machine to use it only for crashdumps. Regards, Niki Denev. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
manual escape to debugger on serial console not working?
Hello, While investigating a problem with one server i installed a serial console on it. The machine has a supermicro board with console redirection enabled on the same port, and everything seems ok, i.e. when the machine panics i get a debugger on the serial console, but when i try to manually escape to the debugger with BREAK (~#) i get this on the screen : The following connections are open: #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cfd -1) Manual enter to the debugger works only if i go physically to the keyboard and do a CTRL-ALT-ESC, then i get KDB: enter: manual escape to debugger on the serial console. i have this added to my kernel conf : options BREAK_TO_DEBUGGER options KDB options DDB and this in /boot/loadaer.conf : console=comconsole Maybe the fact that there is physically attached keyboard interferes with the serial console? Regards, Niki Denev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: manual escape to debugger on serial console not working?
On Thursday 26 January 2006 10:54, Nicolas Rachinsky wrote: * Niki Denev [EMAIL PROTECTED] [2006-01-26 10:50 +0200]: to the debugger with BREAK (~#) i get this on the screen : The following connections are open: #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cfd -1) Are you using ssh? man ssh Escape Characters [...] Nicolas Ah, this was the missing link :) I completely forgot the part that i must type ~~# to actually send a BREAK. Thank You, Nicolas! Regards, Niki Denev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
On Thursday 26 January 2006 10:40, Niki Denev wrote: [...] After i disabled option QUOTA in both my default kernel config and the one i compiled with the debugging options i was unable to reproduce the deadlock again. (i hope it stays that way :) ) This, together with the report in my previous post probably point that the problem is in the QUOTA support. Regards, Niki Denev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kris Kennaway wrote: On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote: On Thursday 26 January 2006 10:40, Niki Denev wrote: [...] After i disabled option QUOTA in both my default kernel config and the one i compiled with the debugging options i was unable to reproduce the deadlock again. (i hope it stays that way :) ) This, together with the report in my previous post probably point that the problem is in the QUOTA support. Actually, I think this is known. Kris Yes, sorry for this. I found a thread on -hackers from November 2005 which seems related: http://lists.freebsd.org/pipermail/freebsd-hackers/2005-November/014339.html Anyway, the machine in question is still not very actively used and i can use it as a guinea pig if someone has the time to look at this, if not, maybe it should be noted somewhere that at this point options QUOTA may cause deadlocks to avoid similar questions/postings? :) Niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD2TbsHNAJ/fLbfrkRAv9BAJ4oCP1rMGnztUFR/3AT8KNnVxuVdQCdFD9w ctMFkroDrgtO8Au46TBzfSY= =Seff -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adaptec SCSI going nuts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joshua Coombs wrote: Just got a dual Opteron system to play with amd64 builds of FreeBSD. Poking around to see how it behaived, I initially tossed FreeBSD 4.11 on it, and was surprised to see a dump of the scsi controller state at the end of the dmesg. Tried 6.0-Rel, both x86 and amd64, same behavior. Bumped up to 6-stable from yesterday, same behavior. After the dump, the system appears solid, no other errors, so I'm guessing it's just a problem with how the card is initialized, FreeBSD corrects it and moves on. Should I be more concerned, or consider it a quirk of the machine? Joshua Coombs [...] I was seeing similar stuff on one machine. I solved the problem with forcing the scsi controller to U160, and splitting the disks on the both channels to distribute the load. (mine was dual-channel onboard U320 and four Seagate 36G 10Krpm hdds) I've heard that this has something to do with firmware incompatibility on some Seagate SCSI drives and Adaptec U320 controllers, but i don't know if it's true. I haven't found stability issues before and after this change, but i left it at U160 to get rid of these messages. Niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD2VSMHNAJ/fLbfrkRAlfWAJ9Q+O23RU16oNT4PSKyRXLYDpggOQCgkumW oZxp6JHj+M5tfK0S700bj0k= =kXPQ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
drm problem after portupgrade to Xorg 6.9
Hello, I've just upraded my Xorg port to the latest relase 6.9, and begin to get this when i start X : agp0: binding memory at bad offset 0 error: [drm:pid610:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:pid610:drm_unlock] *ERROR* Process 610 using kernel context 0 My machine is running 6.0-STABLE, It's Pentium 4 2.0Ghz with Radeon 9600LE dmesg is attached. Any hints are appreciated. calcru: runtime went backwards from 286940498 usec to 286919243 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286919299 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286920059 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286920114 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286921015 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286921070 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286921836 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286921891 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286922643 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286922698 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286923449 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286923504 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286924251 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286924306 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286925169 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286925224 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286925985 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286926041 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286926791 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286926846 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286927597 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286927652 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286928391 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286928446 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286929301 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286929355 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286930112 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286930169 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286930926 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286930982 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286931731 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286931786 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286932545 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286932601 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286933466 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286933521 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286934267 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286934323 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286935073 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286935128 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286935880 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286935935 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286936694 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286936748 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286937599 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286937655 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286938408 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286938462 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286939207 usec for pid 37002 (artsd) calcru: runtime went backwards from 286940498 usec to 286939262
Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Niki Denev wrote: [...] I received off the list suggestion to try a patch from -CURRENT for vfs_lookup.c. I think that this patch is already commited to -STABLE, and so i rebuilt my kernel and world again today, but the problem is still here. The machine deadlocked very hard this time, it even stopped responding to ping requests. This time i was rsyncing this monstrous imap mailbox (about 8G), and ran several times du -sh Maildir on the target machine, everything looked ok, and then i decided to run iostat and when i pressed enter the shell freezed. I will try to setup debugger on the serial console tomorrow to see if i can get some useful info. I'm open to suggestions on how to debug this :) Thanks, Niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD158JHNAJ/fLbfrkRAspmAJ9VJdqMiVljckJUtgipZx1i/UTh1QCcCV+I K2qgeScOMZGz4fxMFnvnE9Q= =cOPx -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drm problem after portupgrade to Xorg 6.9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Jakubik wrote: Patrick Lamaizière wrote: I've just upraded my Xorg port to the latest relase 6.9, and begin to get this when i start X : agp0: binding memory at bad offset 0 error: [drm:pid610:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:pid610:drm_unlock] *ERROR* Process 610 using kernel context 0 Is your AGP chipset supported? What does dmesg|grep agp say? dri: dri-6.4.1,2 OpenGL hardware acceleration drivers for the DRI agp: agp0: Intel 82845 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 drm : drm0: ATI Radeon AP 9600 port 0xc800-0xc8ff mem 0xe000-0xefff,0xff4f-0xff4f irq 16 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized radeon 1.19.0 20050911 uname : FreeBSD ndenev 6.0-STABLE FreeBSD 6.0-STABLE #2: Tue Jan 17 15:35:56 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD1/y0HNAJ/fLbfrkRAnZcAJ45gcQhPVpcBdXDrrA1jEqW+LnjMgCfaYe4 m5nnSK6Ra/oQheMLd1RqmSI= =JjBP -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
Hello, I'm experiencing some problems with a 6.0-STABLE machine, cvsupped and rebuilt yesterday. I'm not sure that the problem is related to this last update, because this machine is not very loaded currently. The machine is with dual opteron mb from Supermicro, with two Opteron 244s and 4GB of DDR 400 ECC Registered memory, integrated Adaptec U320 SCSI controller (forced to U160 mode), and four Seagate 36G 10K rpm scsi drives. The kernel config is generic SMP with enabled QUOTA support, accounting_enable=YES in rc.conf and the root fs is a software Raid-10 running two striped mirrors using geom_mirror and geom_stripe with the help of a little /boot partition for loading the kernel and the required modules. Kernel conf, dmesg and loader.conf are available here : http://www.totalterror.net/freebsd/srv/ Yesterday i was able to deadlock the machine two times, doing exactly the same thing : I was doing rsync from another machine to this one. I was syncing one rather big imap(Maildir) folder, about 270K msgs(files), and at the same time i was syncing this folder contents via the bincimap imap server on a remote machine running Kmail. Then i run a du -sh on the folder in question.and all my shells to it stopped working... I was able to ping the machine and connect to listening ports, but without getting banners from the daemons. There was also zero HDD activity at this time. Unfortunately i forgot to enter the debuger and get a trace...(but, will it show something meaningfull or just the keyboard interrupt handler?) After reseting the machine booted and rebuilt it's secondary components on the both mirrors ( maybe this is normal? it seems it's happeing everytime the machine is uncleanly restarted) This is a big problem for me because this machine will soon enter in production, and should be able to serve imap to a dozen of clients. I know that 270K msg in single imap folder is stupid, but our old imap server running FreeBSD 5.4-STABLE(quite old STABLE) on AMD 1800+ with 2G of ram and 80G IDE disk has no problems with it, except being very slow of course I hope this info is enough, if not i will gladly provide more. Any suggestions are welcome, Thanks. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Creating a system RAID-10 device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sven Willenberger wrote: I hope this is the appropriate mailing list for this question, if not please redirect me as needed. My goal is to create a filesystem consisting of a striped raid array over 3 mirror raid arrays that would encompass the entire filesystem including the /boot and root partitions. Generally I would create a RAID10 from 6 disks as follows: gmirror label -v -b round-robin md1 da0 da1 gmirror label -v -b round-robin md2 da2 da3 gmirror label -v -b round-robin md3 da4 da5 gstripe label -v -s 131072 md0 /dev/mirror/md1 /dev/mirror/md2 /dev/mirror/md3 newfs /dev/stripe/md0 naturally the problem here is that it cannot be done on a system that booted from da0. I have seen the example of setting up a mirrored system drive (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html ) which won't quite work for my case either. Using this method I could probably get the one mirror (md1) to work, but I know of no way of then adding the other 2 mirror sets and then redoing the system to stripe across all 3 mirrored sets. The only thing I could think of was to boot from the livecd and create the 6-disk array and then trying to install FreeBSD onto this filesystem. In order to do this the installer would have to recognize /dev/stripe/md0 as a valid drive -- is there any way to have this happen? Sven I've done this for a server in our office. I used four disks, and did the following : Split each disk on 2 parts, one about 60M for /boot, and the other part to the end of the disk. Then i created geom_mirror from the four 60M slices. (yah, mirror from 4 devices, it wastes a little space, but so what disks are cheap) and then with the big slices i created two geom_mirrors with 2 slices each, and then mirrored them. It looks something like this : [EMAIL PROTECTED] mount /dev/mirror/gm0 on /boot_mirror (ufs, local, noatime, synchronous) /dev/stripe/gs0a on / (ufs, local, noatime, with quotas, soft-updates) [EMAIL PROTECTED] gmirror status NameStatus Components mirror/gm0 COMPLETE da0s1a da1s1a da2s1a da3s1a mirror/gm1 COMPLETE da0s1d da1s1d mirror/gm2 COMPLETE da2s1d da3s1d [EMAIL PROTECTED] gstripe status Name Status Components stripe/gs0 UP mirror/gm1 mirror/gm2 [EMAIL PROTECTED] [EMAIL PROTECTED] cat /boot/loader.conf geom_mirror_load=YES geom_stripe_load=YES vfs.root.mountfrom=ufs:/dev/stripe/gs0a [EMAIL PROTECTED] ls -lad /boot* lrwxr-xr-x 1 root wheel 16 Jun 25 2005 /boot - boot_mirror/boot drwxr-xr-x 4 root wheel 512 Jun 25 2005 /boot_mirror Then i can boot a RAID-10 software array with GEOM on FreeBSD and also have the added bonus that i can boot from any of the four disks if any fails. (well, i guess i still will have to chose other disk for boot from the scsi bios) Regards, - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDzXC+HNAJ/fLbfrkRAlKyAJ9bhXwCQe2ZuLI6KL32yRGWCrnhsACfVSrM TkQzpNM4UVy9V0OSNAk9RLY= =NNNa -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ifconfig hidessid not hiding SSID on 802.11b with PRISM 2.5 based card
On Tuesday 10 January 2006 16:02, Patrick Tracanelli wrote: I have set hidessid option to an Intersil PRISM 2.5 based cart, acting as hostap, and the ssid stills gets broadcasted, aparently. Other FreeBSD systems and the Windows software supplied by the vendor can find the SSID while scanning. I would like to know if hidessid should hide it in ordinary scans like those ones, and how to test it better to see if ssid stills broadcasted in the beacons, if it is possible (say, any debug option or tool). Thanks! I think that for SSID hiding to work there is a need for the firmware on the card to support this. (at least on Prism2/2.5 hardware) Maybe your firmware does not support ssid hiding. You can try to update it. hth, --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
devfs.rules and serial devices question
Hi all, I'm setting up a UPS on one machine, and the ups daemon (nut) works as user upsd. To make it work properly i have added in devfs.rules the following : permttyd0 0660 own ttyd0 upsd:upsd But it still does not work because ttyd0.init and ttyd0.lock are still owned by root. I'll try adding them too to the devfs.rules file, but i'm wondering if this is the expected behaviour of devfs? I think that maybe it will be better if one specify ttyd0 in the file, that rule also to apply for ttyd0.init and ttyd0.lock files. What do you think? --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
top(1) displaying threads
Hello, From some time in 6.0 and -current top(1) shows by default also the kernel threads. But the top(1) manual page still says that the default behaviour is NOT to show them. Maybe something like this will be enough: --- usr.bin/top/top.local.1 Fri Jul 18 02:56:39 2003 +++ usr.bin/top/top.local.1.fix Wed Nov 30 18:51:35 2005 @@ -3,7 +3,7 @@ .SH DISPLAY OF THREADS The '-H' option will toggle the display of kernel visible thread contexts. -At runtime the 'H' key will toggle this mode. The default is OFF. +At runtime the 'H' key will toggle this mode. The default is ON. .SH DESCRIPTION OF MEMORY Mem: 9220K Active, 1032K Inact, 3284K Wired, 1MB Cache, 2M Buf, 1320K Free ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: top(1) displaying threads
On Wednesday 30 November 2005 20:18, John Baldwin wrote: On Wednesday 30 November 2005 11:55 am, Niki Denev wrote: Hello, From some time in 6.0 and -current top(1) shows by default also the kernel threads. But the top(1) manual page still says that the default behaviour is NOT to show them. Maybe something like this will be enough: --- usr.bin/top/top.local.1 Fri Jul 18 02:56:39 2003 +++ usr.bin/top/top.local.1.fix Wed Nov 30 18:51:35 2005 @@ -3,7 +3,7 @@ .SH DISPLAY OF THREADS The '-H' option will toggle the display of kernel visible thread contexts. -At runtime the 'H' key will toggle this mode. The default is OFF. +At runtime the 'H' key will toggle this mode. The default is ON. .SH DESCRIPTION OF MEMORY Mem: 9220K Active, 1032K Inact, 3284K Wired, 1MB Cache, 2M Buf, 1320K Free The manpage is correct. The problem is that kernel threads such as ithreads are really kernel processes currently. Oh, i see. I was confused by the THR column, but now everything is clear :) Thanks and sorry for the noise. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
inconsistent arp(8) mac address output using if_bridge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I have a small machine setup to act as simple network gateway. I have one wireless and one wired interfaces without IP configuration on them, and they are added as if_bridge(4) members. When i issue arp -na command on the machine i get this: ? (10.10.10.240) at 0.14.a5.1a.dc.73 on bridge0 ? (10.10.10.241) at 4.4b.80.80.80.3 on bridge0 ? (10.10.10.246) at 0.a0.cc.62.99.c3 on bridge0 ? (10.10.10.253) at 0.5.4e.4f.7b.eb on bridge0 ? (172.16.1.1) at 00:30:48:83:93:e9 on ep0 [ethernet] ? (172.16.37.9) at 00:0f:b0:01:30:c0 on ep0 [ethernet] While the mac addresses appear to be correct, maybe this should be fixed to be consistent with the default mac address output? - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgLd0HNAJ/fLbfrkRAt37AKDJ5P9PC1tf6VCyBDv83KwjNTqirwCgvhoW noztCOr2cpcaEqEjiBLAclc= =7DFZ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: inconsistent arp(8) mac address output using if_bridge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Niki Denev wrote: Hello, I have a small machine setup to act as simple network gateway. I have one wireless and one wired interfaces without IP configuration on them, and they are added as if_bridge(4) members. When i issue arp -na command on the machine i get this: ? (10.10.10.240) at 0.14.a5.1a.dc.73 on bridge0 ? (10.10.10.241) at 4.4b.80.80.80.3 on bridge0 ? (10.10.10.246) at 0.a0.cc.62.99.c3 on bridge0 ? (10.10.10.253) at 0.5.4e.4f.7b.eb on bridge0 ? (172.16.1.1) at 00:30:48:83:93:e9 on ep0 [ethernet] ? (172.16.37.9) at 00:0f:b0:01:30:c0 on ep0 [ethernet] While the mac addresses appear to be correct, maybe this should be fixed to be consistent with the default mac address output? --niki Sorry, forgot the mention the os version : FreeBSD gimli 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgLlYHNAJ/fLbfrkRAnM8AJ0WbFS29X9F3FTah1S3Rnb/P7BZOgCeNeTr at9AxPhl6kvnVV7XBFY3lns= =Tgdb -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Ricardo A. Reis wrote: Hi all, The University where i work recent acquire a new server, i install FreeBSD 6.0 and update for STABLE yestarday, in dmesg i see this messages ahd0: Invalid Sequencer interrupt occurred. I've had similar problems with Dual channel U320 adaptec controller (built in on supermicro board) and Seagate U320 drives. The solution was to force the drives to U160 speed from the BIOS, and split the drives equaly on the two channels to reduce the bottleneck. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel: calcru: runtime went backwards
Stephen Montgomery-Smith wrote: Giovanni P. Tirloni wrote: Try this, http://www.freebsd.org/doc/en/books/faq/book.html#CALCRU-NEGATIVE Thank you. I must admit that I missed this. Unfortunately all the suggestions in this FAQ seem to be out of date - none of the suggested sysctls or kernel config options seem to apply to FreeBSD 6. Stephen I have the same problem after the switch to 6.0 from 5.4 : http://lists.freebsd.org/pipermail/freebsd-stable/2005-November/019171.html I've set the kern.timecounter sysctl to i8254 as suggested by Joseph Koshy. Now it seems that i get these messages rarely, maybe onece a day. Before this i get maybe 4-5 daily. Now it clearly looks that this has something to do with excessive thread usage. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards ?
Niki Denev wrote: Hi, I've recently upgraded my server from 5.4-STABLE to 6.0-RC1 and shortly after that i began to see these messages in my dmesg: calcru: runtime went backwards from 1488581 usec to 1488580 usec for pid 65583 (mpsnmp) [snip] dmesg and output of kern.timecounter sysctl can be found here : http://totalterror.net/freebsd/calcru/ --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards ?
Joseph Koshy wrote: dmesg and output of kern.timecounter sysctl can be found here : Changing your timecounter to i8254 may help. Bug 43491 and 72338 seem to be related: http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 http://www.freebsd.org/cgi/query-pr.cgi?pr=43491 -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy Thanks, i've changed it to i8254 and will watch it for a couple of days. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards ?
Niki Denev wrote: Joseph Koshy wrote: dmesg and output of kern.timecounter sysctl can be found here : Changing your timecounter to i8254 may help. Bug 43491 and 72338 seem to be related: http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 http://www.freebsd.org/cgi/query-pr.cgi?pr=43491 -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy Thanks, i've changed it to i8254 and will watch it for a couple of days. --niki i've got three more of them this morning... and it seems that only my program triggers them. i think it's the only application that uses threads on my system, maybe this is related? --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendfile + non local filesystem + lighttpd = EOPNOTSUPP
Niki Denev wrote:
I get the same behaviour also with 6.0-RC1 (cvsupped an hour ago)
Ok,
In this awful piece of code created for testing purposes
if i set FILETOSEND to local file it works ok,
but if the file is located on smbfs sendfile returns Operation
not supported.
If this is not a bug, maybe it should be documented? (also the
error code that sendfile returns)
(again, the machine is 6.0-RC1 cvsupped yesterday, with SMP kernel)
---[sendfile_test.c]---
#include stdio.h
#include stdlib.h
#include sys/types.h
#include sys/socket.h
#include sys/uio.h
#include fcntl.h
#include unistd.h
#include string.h
#include errno.h
#include sys/types.h
#include sys/socket.h
#include netinet/in.h
#include arpa/inet.h
#define FILETOSEND /var/log/messages
//#define FILETOSEND /mnt/smb/somefile.dat
int main() {
int fd;
int sock;
int result;
struct sockaddr_in sa;
fd = open(FILETOSEND, O_RDONLY);
sock = socket(PF_INET, SOCK_STREAM, 0);
memset(sa, 0, sizeof(sa));
sa.sin_family = AF_INET;
sa.sin_port = htons(9); /* discard enabled in inetd */
inet_aton(127.0.0.1, sa.sin_addr);
printf(connecting socket ... );
errno = 0;
result = connect(sock, (struct sockaddr *)sa, sizeof(sa));
printf(%s\n, errno?strerror(errno):ok);
printf(calling sendfile ... );
errno = 0;
result = sendfile(fd, sock, 0, 0, NULL, NULL, 0);
printf(%s\n, errno?strerror(errno):ok);
close(fd);
close(sock);
return(0);
}
---[end of sendfile_test.c]---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendfile + non local filesystem + lighttpd = EOPNOTSUPP
This thread seems to relate to the same problem in dfbsd : http://leaf.dragonflybsd.org/mailarchive/kernel/2005-03/msg00101.html I think that this should be fixed, the man page did not mentions EOPNOTSUPP and this can lead to further confusion because it seems that HP-UX for example sets errno to EOPNOTSUPP when the socket is not TCP. Any comments? P.S.: It seems like i'm talking to myslef, i hope it's because it's sunday :) --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sendfile + non local filesystem + lighttpd = EOPNOTSUPP
Hello, I seem to have a problem serving files with lighttpd from non local (smbfs) filesystem. Lighttpd tries to use sendfile(2) but, it returns with -1 and errno Operation not supported, but i can't find this error in the documented errors on the manpage. Forcing lighttpd to not use sendfile fixes the problem, but i would really like to use it... Any suggestions? - 40793 lighttpd CALL open(0x8089c80,0,0x80bac00) 40793 lighttpd NAMI /usr/local/www/data/stuff/downloads/some_file.txt 40793 lighttpd RET open 8 40793 lighttpd CALL sendfile(0x8,0x7,0,0,0x1b22,0,0xbfbfc600,0) 40793 lighttpd RET sendfile -1 errno 45 Operation not supported 40793 lighttpd CALL write(0x6,0x8089400,0x5d) 40793 lighttpd GIO fd 6 wrote 93 bytes 2005-10-29 08:43:09: (network_freebsd_sendfile.c.174) sendfile: Operation not supported 45 40793 lighttpd RET write 93/0x5d 40793 lighttpd CALL close(0x8) Here /usr/local/www/data/stuff/downloads is a smbfs mount. If the file is local everything works as expected. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendfile + non local filesystem + lighttpd = EOPNOTSUPP
David G. Lawrence wrote: Hello, I seem to have a problem serving files with lighttpd from non local (smbfs) filesystem. Lighttpd tries to use sendfile(2) but, it returns with -1 and errno Operation not supported, but i can't find this error in the documented errors on the manpage. Forcing lighttpd to not use sendfile fixes the problem, but i would really like to use it... Any suggestions? What version of FreeBSD? -DG ouch.. sorry i forgot to include the version .. It's 5.4-STABLE about 3-4 months old. (i'll try to update to 6.0 this weekend) And the lighttpd version is the latest from the ports, 1.4.6 i think. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendfile + non local filesystem + lighttpd = EOPNOTSUPP
Niki Denev wrote: David G. Lawrence wrote: Hello, I seem to have a problem serving files with lighttpd from non local (smbfs) filesystem. Lighttpd tries to use sendfile(2) but, it returns with -1 and errno Operation not supported, but i can't find this error in the documented errors on the manpage. Forcing lighttpd to not use sendfile fixes the problem, but i would really like to use it... Any suggestions? What version of FreeBSD? -DG ouch.. sorry i forgot to include the version .. It's 5.4-STABLE about 3-4 months old. (i'll try to update to 6.0 this weekend) And the lighttpd version is the latest from the ports, 1.4.6 i think. --niki I get the same behaviour also with 6.0-RC1 (cvsupped an hour ago) --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI troubles
Tomas Randa wrote:
Hi,
I Am running 5.4-STABLE FreeBSD 5.4-STABLE #0: Sun May 8 18:23:40 CEST
2005 with Adaptec 29320 or 2930U2 controller and with heavy load on SCSI
I have the following problems ending with system freeze. Have anybody
some opinion where could be problem?
Hi,
I have similar problems under load on one DualOpteron machine,
i noticed that when i set the controller in U160 mode the messages
dissaperar. So i split the drives in the server equaly on the both
scsi channels on the motherboard and set the controller to U160.
I have then run while(1) { make clean; make universe; } which is still
runnnig for about 3 days. Before that the machine was rebooting about
every couple of hours if under load.
From what i understand this is not exactly a FreeBSD problem, but rather
a consequence of U320 being really hard on the hardware with pushing it
to the limits.
--niki
Jul 1 16:14:58 srv kernel: ahd0: Invalid Sequencer interrupt occurred.
Jul 1 16:14:58 srv kernel: Dump Card State Begins
Jul 1 16:14:58 srv kernel: ahd0: Dumping Card State at program address
0x23c Mode 0x0
Jul 1 16:14:58 srv kernel: Card was paused
Jul 1 16:14:58 srv kernel: INTSTAT[0x0] SELOID[0x0] SELID[0x10]
HS_MAILBOX[0x0]
Jul 1 16:14:58 srv kernel: INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0]
SAVED_MODE[0x11]
Jul 1 16:14:58 srv kernel:
DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE)
Jul 1 16:14:58 srv kernel: SCSISIGI[0x0]:(P_DATAOUT) SCSIPHASE[0x0]
SCSIBUS[0x0]
Jul 1 16:14:58 srv kernel: LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE)
SCSISEQ0[0x0]
Jul 1 16:14:58 srv kernel: SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI)
SEQCTL0[0x0] SEQINTCTL[0x6]:(INTMASK1|INTMASK2)
Jul 1 16:14:58 srv kernel: SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0]
QFREEZE_COUNT[0x2]
Jul 1 16:14:58 srv kernel: KERNEL_QFREEZE_COUNT[0x2]
MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff]
Jul 1 16:14:58 srv kernel: SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0]
SSTAT3[0x0] PERRDIAG[0x0]
Jul 1 16:14:58 srv kernel:
SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0]
Jul 1 16:14:58 srv kernel: LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0]
LQOSTAT1[0x0]
Jul 1 16:14:58 srv kernel: LQOSTAT2[0x0]
Jul 1 16:14:58 srv kernel:
Jul 1 16:14:58 srv kernel: SCB Count = 16 CMDS_PENDING = 0 LASTSCB
0x CURRSCB 0xf NEXTSCB 0xff40
Jul 1 16:14:58 srv kernel: qinstart = 28 qinfifonext = 28
Jul 1 16:14:58 srv kernel: QINFIFO:
Jul 1 16:14:58 srv kernel: WAITING_TID_QUEUES:
Jul 1 16:14:58 srv kernel: Pending list:
Jul 1 16:14:58 srv kernel: Total 0
Jul 1 16:14:58 srv kernel: Kernel Free SCB list: 14 15 1 2 3 4 5 6 7 8
9 10 11 12 13 0
Jul 1 16:14:58 srv kernel: Sequencer Complete DMA-inprog list:
Jul 1 16:14:58 srv kernel: Sequencer Complete list:
Jul 1 16:14:58 srv kernel: Sequencer DMA-Up and Complete list:
Jul 1 16:14:58 srv kernel: Sequencer On QFreeze and Complete list:
Jul 1 16:14:58 srv kernel:
Jul 1 16:14:58 srv kernel:
Jul 1 16:14:58 srv kernel: ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xe
Jul 1 16:14:58 srv kernel:
SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS)
Jul 1 16:14:58 srv kernel: SEQINTSRC[0x0] DFCNTRL[0x0]
DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL)
Jul 1 16:14:58 srv kernel: SG_CACHE_SHADOW[0x2]:(LAST_SEG)
SG_STATE[0x0] DFFSXFRCTL[0x0]
Jul 1 16:14:58 srv kernel: SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO)
SHADDR = 0x00, SHCNT = 0x0
Jul 1 16:14:58 srv kernel: HADDR = 0x00, HCNT = 0x0
CCSGCTL[0x10]:(SG_CACHE_AVAIL)
Jul 1 16:14:58 srv kernel:
Jul 1 16:14:58 srv kernel: ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xf
Jul 1 16:14:58 srv kernel:
SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS)
Jul 1 16:14:58 srv kernel: SEQINTSRC[0x0] DFCNTRL[0x0]
DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL)
Jul 1 16:14:58 srv kernel: SG_CACHE_SHADOW[0x2]:(LAST_SEG)
SG_STATE[0x0] DFFSXFRCTL[0x0]
Jul 1 16:14:58 srv kernel: SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO)
SHADDR = 0x00, SHCNT = 0x0
Jul 1 16:14:58 srv kernel: HADDR = 0x00, HCNT = 0x0
CCSGCTL[0x10]:(SG_CACHE_AVAIL)
Jul 1 16:14:58 srv kernel: LQIN: 0x8 0x0 0x0 0xe 0x0 0x1 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Jul 1 16:14:58 srv kernel: ahd0: LQISTATE = 0x0, LQOSTATE = 0x0,
OPTIONMODE = 0x42
Jul 1 16:14:58 srv kernel: ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1
Jul 1 16:14:58 srv kernel: ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0
Jul 1 16:14:58 srv kernel:
Jul 1 16:14:58 srv kernel: SIMODE0[0xc]:(ENOVERRUN|ENIOERR)
Jul 1 16:14:58 srv kernel: CCSCBCTL[0x4]:(CCSCBDIR)
Jul 1 16:14:58 srv kernel: ahd0: REG0 == 0x6d8e, SINDEX = 0x10e, DINDEX
= 0x102
Jul 1 16:14:58 srv kernel: ahd0: SCBPTR == 0xe, SCB_NEXT == 0xff40,
SCB_NEXT2 == 0xff6d
Jul 1 16:14:58 srv kernel: CDB 12 20 0 80 8 b5
Jul 1 16:14:58 srv kernel: STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0
Jul 1 16:14:58 srv kernel: Dump Card State Ends
Jul 1 16:14:58 srv kernel: Copied 18 bytes of sense data offset
Re: background fsck can be dangerous!
Luke Crawford wrote: disabling background fsck while continuing to run soft updates will make little difference. Personally, I would recommend that you keep your disk mount configuration as it is, and that you buy a UPS. Well, i surely need an UPS, that's out of question, but the problem that i had was not about loss/corruption on files on disk. Before the background fsck finished some files were unreadable, and they happened to be some libraries used by my mail software. After the fsck finished these libraries were accessible again and everything was normal and working, at least this is what it looked like to me. So, i think that if i had disabled background fsck (as i did now) i should have skipped the loss of these about ten emails... --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
background fsck can be dangerous!
Hello, I want just to share my last experience with the combination of power failure + background fsck. After the power returned and the machine booted, it sheduled background fsck after 60 seconds, but at this point most of the services were already started, and some of them seemed to rely on files that were probably in unclean state before the check. This unfortunately leaded to some lost email...after the fsck completed, everything runs ok, but i have now set background_fsck to NO in rc.conf. Here is a sad sample from my qmail log file : @400042c1badc24fc21cc delivery 1: success: /libexec/ld-elf.so.1:_Shared_object_libpq.so.3_not_found,_required_by_dspam/did_0+0+1/ @400042c1badc24fff25c status: local 2/30 remote 0/20 @400042c1badc250151ec delivery 4: success: /libexec/ld-elf.so.1:_Shared_object_libpq.so.3_not_found,_required_by_dspam/did_0+0+1/ @400042c1badc2502bd34 status: local 1/30 remote 0/20 @400042c1badc25050ef4 end msg 23982 @400042c1badc2508b0a4 delivery 2: success: /libexec/ld-elf.so.1:_Shared_object_libpq.so.3_not_found,_required_by_dspam/did_0+0+1/ @400042c1badc250a9cd4 status: local 0/30 remote 0/20 @400042c1badc250c7d4c end msg 24087 @400042c1badc2510942c end msg 24040 --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel or syslogd problem under exterme load (many processes and filedescs open)
Hello, Recently while testing a program on a 5.3-STABLE machine with dual Athlon MP 2200+ (SMP enabled), i made a mistake and the program basicaly became a fork() bomb. It flooded my dmesg and messages with these messages (which is normal): Jan 29 18:13:20 tormentor kernel: maxproc limit exceeded by uid 1001, please see tuning(7) and login.conf(5). Jan 29 18:13:25 tormentor kernel: kern.ipc.maxpipekva exceeded; see tuning(7) but i've also noticed several mangled messages in the log, like these : Jan 29 18:08:25 tormentor kernel: kernmaxpr.ipc.maxpipekocva excee limidet exd;ce sedeeed t buninyg( u7)id 1001, please see tuni ng(7) and login.conf(5). Jan 29 18:08:28 tormentor kernel: Probably this is some sort of race condition, either in the kernel output or syslogd? --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
