Re: Repeatable crash with 5.4-p1-RELEASE and SMP
On Sat, 4 Jun 2005, Palle Girgensohn wrote: Anyway, I have managed to get an automatic reboot and a core dump. Giant leap for mankind :-) . It looks kind of partly overwritten, though. According to the Developer's handbook, the core should be saved *before* the swap partition is added to the system. I can easily verifying that this is not the case, the swap is mounted first. I once again raise the question if PR conf/73834 shouln't be addressed? Or perhaps my core dump is quite normal? Doesn't look like it. In rc.conf, I have: I can't speak to the crash itself, but regarding swap and cores: the problem is that fsck requires quite a lot of memory in order to operate on large file systems, so you have to configure swap before you fsck. However, you can't write the core dump to the file system until it has been fsck'd. Normally, if fsck actually uses swap, it will overwrite the core dump header, and savecore will recognize that the entire dump is invalidated, so usually you don't see the corrupted core, just that the core is missing. Whether this happens depends on how large your file systems are, how many you have (since fsck runs in parallel), and how much memory you have. If you want to be sure this doesn't happen, boot to single user mode after the crash, manually fsck without swap enabled (fsck -p), mount -a, then sh /etc/rc.d/savecore start to save the core. My suspicion is that the corruption you're seeing is not a property of swap being started, but it's easy to rule out if you have a reproduceable crash and can be there to boot single-user after the reboot. Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystems not properly unmounted
Vulpes Velox wrote: I have had the same problem with fat32 filesystems before also. I have ut2004 installed on a fatpartition on my dualboot machine. To make it accessible so that I can play it in freebsd aswell, I need to mount and unmount the drive from a rc.d script under /usr/local/etc/ rc.d/ to make sure it gets unmount. With out that, it does not properly unmount it. Odd.. I do not see that with msdosfs (vfat/fat32). I have: /dev/ad4s2 on /dos (msdosfs, local) and it always shuts down cleanly. How do you have it mounted? mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xffm - xfsamba4 broken in 5-stable?
On Tue, 31 May 2005 20:39:47 +0300 Andriy Gapon [EMAIL PROTECTED] wrote: if (kill(PID,SIGCONT) == 0) return TRUE; [ cut lorts of interesting text ] Removing that line fixed xfsamba4 for me, but I encountered another Ok, so you just removed that line from tubo.c? I wonder if this is the correct way to fix it, but anyway, I'm going to try it. problem after that, my PDC (NT4) doesn't respond to the following request (Samba3 client): nmblookup -A master browser ip so instead I had to use nmblookup -M -S -- - FWIW, my (non-working) xfsamba4 uses 'nmblookup -M -- -' (that dash M double dash dash) and this made xfsamba4 perfectly well. Perhaps you should send-pr this information. -- Regards Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xffm - xfsamba4 broken in 5-stable?
On Sat, 04 Jun 2005 20:27:35 +0200 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Ok, so you just removed that line from tubo.c? Reading the line in context shows that this might indeed be the correct fix, here is the context: #ifdef __FreeBSD__ /* This apparently does the bug workaround for wait failure * on FreeBSD 5.1: */ if (kill(PID,SIGCONT) == 0) return TRUE; #endif Perhaps this should be removed, or at least fixed so that it only is needed on FreeBSD 5.1. I wonder if this is the correct way to fix it, but anyway, I'm going to try it. And it worked. I did a 'make extract' in the xfce4-fm port directory, removed the offending line 'if (kill(PID...', and did a 'make deinstall' followed by a 'make reinstall'. Now xfsamba4 works like it did before. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [lists] RAID-1 as back-up
Remo Lacho wrote: On 6/4/2005 at 12:26 AM Hans F. Nordhaug wrote: Dear list, I would like to use RAID-1 as a back-up solution. If one of the disk breaks I would like my server to continue to run from the other disk. I have followed the mailing list for a while and read some howtos, but I'm not sure if this is possible (without doing all kinds of tricks when the accidents happens - removing meta data and so on). In addition, I thought, gvinum was the way to go, but hasn't there been some problems with it (reported here lately)? I'm running 5.3 - what do you recommend - gvinum, ccd, others? What is the definitive howto for the recommend solution. Thx for your time. Regards, Hans ... *** REPLY SEPARATOR *** Good place to start: http://people.freebsd.org/~rse/mirror/ Up to a point - beware of geom_mirror with USB and FireWire disks - it's temperamental at best and with my FireWire drives simple won't work reliably (panic during boot if a rebuild is needed and unrecoverable errors during rebuilds). I've just re-done the mirror set on my box with gvinum and so far it's looking good - it boots ok and rebuild is a lot faster. This on a 5-STABLE box with a FW800 card a 2x LaCie 500GB bigger disk extreme external FW drives. If this works for my next trick I'll try RAID5 with 4x250gb usb drives. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID-1 as back-up
On Jun 3, 2005, at 18:50, Karl Denninger wrote: As with all backup strategies (absent write-once media in SOME cases) if the media is PHYSICALLY connected to the machine and it is hacked it is possible for a hacker to scribble on THAT as well. This is no more likely, however, Or a voltage spike to fry it (the OP has a UPS, right?). Or if there is some flooding it will scramble things as well. Regardless of media you use, make sure there is at least one back up off site. I've heard of some insurance companies not paying out the business continuation payments since there was no off site data (it was a condition in the agreement / contract). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kadmin (heimdal port) ignores the ldap backend
On Fri, 3 Jun 2005 15:00:56 -0500 Scot Hetzel wrote:
On 6/3/05, Boris Samorodov [EMAIL PROTECTED] wrote:
I believe you have to set NO_KERBEROS in /etc/make.conf. Then rebuild
install the FreeBSD sources in /usr/src. Then after the
installworld, you'll need to go to the /usr/lib directory and
move/remove all libs that are older than the date of the install.
NOTE: I would also do a second installworld, after removing the
libraries. Just incase something was removed that wasn't supposed to
be removed.
Then install the KERBEROS hemidal port.
Hmm. And what about kerbesized applications (i.e. sshd) from the base
system which I'd like to use with kerberos authentication?
looks like you would have to install them from ports, unless you
Those from ports uses MIT Kerberos 5 realization. Maybe they work with
Heimdal also...
hacked the sources to use KERBEROS installed from the port.
src/secure/usr.bin/ssh/Makefile
src/lib/libtelnet/Makefile
src/lib/libpam/modules/modules.inc
NOTE: there may be others
You would have to change the files to check if the hemdial libraries
are installed:
.if (defined(HEIMDAL_HOME) exists(${HEIMDAL_HOME}/lib/libkrb5.so) )
|| !defined(NO_KERBEROS)
NOTE: you may also need to set LDFLAGS+=-L${HEIMDAL_HOME}/lib
And see if it compiles.
This way means applying patches every build/install world. And there
is no guarantee that pathes apply well. And it is really a *hack*.
I try to find a way to DTRT (do the right thing).
So far I have two workarounds (may be *hacks* all together):
o install heimdal from ports and change library searching path (to
search /usr/local/lib before athers). Don't know if it may break
something;
o install heimdal from ports with LOCALBASE=/usr. The port should be
reinstalled after make world.
Thus neighter of them are good...
WBR
--
bsam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [lists] RAID-1 as back-up
Remo Lacho wrote: O Up to a point - beware of geom_mirror with USB and FireWire disks - it's temperamental at best and with my FireWire drives simple won't work reliably (panic during boot if a rebuild is needed and unrecoverable errors during rebuilds). I've just re-done the mirror set on my box with gvinum and so far it's looking good - it boots ok and rebuild is a lot faster. This on a 5-STABLE box with a FW800 card a 2x LaCie 500GB bigger disk extreme external FW drives. If this works for my next trick I'll try RAID5 with 4x250gb usb drives. *** REPLY SEPARATOR *** I feel your pain. :) Please excuse my ignorance, but why would you use USB or Firewire drives on a production server? It's a home server and the storage is near-line photo archives (I'm a professional photographer) that's also backed up on REV cartridges. I don't need the performance of a multi thousand dollar server box just the storage capacity to host up to a terabyte of images. If I really needed the performace I'd build somthing with SCSI or SATA drives but I just need capacity. Currently the box has: IDE 80 GB main disk (root usr var tmp swap ) 1x250GB FW 400 - scratch storage 2x300GB FW 400 in a gstripe set - storage for BackupPC which covers the desktop boxes. 2x500GB FW 800 (on a separate FW800 controller) - this is going to be the photo archive in a gvinum mirror set. Then I have 4xUSB250GB drives that are not really doing anyting right now and I may build into a RAID5 for future expansion. John ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID-1 as back-up
On Sat, Jun 04, 2005 at 04:57:52PM -0400, David Magda wrote: On Jun 3, 2005, at 18:50, Karl Denninger wrote: As with all backup strategies (absent write-once media in SOME cases) if the media is PHYSICALLY connected to the machine and it is hacked it is possible for a hacker to scribble on THAT as well. This is no more likely, however, Or a voltage spike to fry it (the OP has a UPS, right?). Or if there is some flooding it will scramble things as well. Regardless of media you use, make sure there is at least one back up off site. I've heard of some insurance companies not paying out the business continuation payments since there was no off site data (it was a condition in the agreement / contract). Having an offsite copy is just good common sense. My point is that there are other ways to do this beyond traditional tape media, and that a RAID system is a perfectly-viable means of accomplishing the goal. - -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re[2]: [lists] RAID-1 as back-up
On Jun 4, 2005, at 5:11 PM, Remo Lacho wrote: Please excuse my ignorance, but why would you use USB or Firewire drives on a production server? Firewire makes a really nice hot-pluggable I/O bus which works nicely with external devices. Your typical external Firewire drive is generally a medium-decent IDE drive (ie, one with a 3-year warranty and more cache than the typical drive sold today) using an IDE-FW converter. Firewire is especially well suited to things like movie editting and other A/V work, and I'd rather use it than IDE for those kind of tasks. It's not clear that even Ultra320 SCSI is a better choice as an interface, although the highest-end SCSI drives are probably more reliable. You'd have to switch up to a fibre-channel SAN to get a system which is significantly faster or more fault-tolerant. [ I don't think so highly of USB2. ] -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD-5.4R-p1 problems with lnc device and AT-1500FT PnP card
Hi,
I am trying to make a network card work with lnc(4) device.
The card is an AT-1500 PnP Ethernet Adapter based on PCnet(TM)-ISA II
chip from AMD (AM79C961AKC) which is supposed to be supported under lnc(4)
driver. The card has both a 10BaseFL (ST) and 10BaseT port.
After adding the card's pnp id to the lnc_pnp_ids[] structure I am getting
the card recognized and attached but the chip and MAC address are wrongly
detected.
Any help will be appreciated!
#uname -a
FreeBSD test 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #4: Sun Jun 5
00:18:56 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TEST i386
#dmesg
...
lnc1: ATI AT-1500 Ethernet Network Adapter at port 0x220-0x237 irq 9 drq 3 on
isa0
lnc1: Attaching ATI AT-1500 Ethernet Network Adapter
lnc1: Ethernet address: cf:bf:ff:ef:00:ff --wrong (tested against DOS setup
program)
lnc1: if_start running deferred for Giant
lnc1: Unknown - (chip id 0!)
...
A diff to if_lnc_isa:
=
--- sys/dev/lnc/if_lnc_isa.c.orig Sun Jan 30 01:59:53 2005
+++ sys/dev/lnc/if_lnc_isa.cSun Jun 5 00:16:19 2005
@@ -54,6 +54,8 @@
#include dev/lnc/if_lncreg.h
static struct isa_pnp_id lnc_pnp_ids[] = {
+{0x00158b06, NULL}, /* ATK1500 - ATI AT-1500 Ethernet Network
Adapter */
+{0x8c82d041, AMD PCNet Family Cards}, /* PNP828C */
{0, NULL}
};
=
the information added to if_lnc_isa.c was obtained with pnpinfo(8).
Regards,
G. Ardelean
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
