Re: Exabyte VXA tape drives - anyone using?
Run it through strace(1) and ktrace(1) in Linux and see what devices it
talks to in /dev and see if they can be emulated. It's probably talking
to /dev/ns{r,a}0 and /dev/ch0, depending on udev/autodev/
foo-bar-latest-greatest linux framework.
You might also check the Amanda/Bacula list archives.
~BAS
On Wed, 2007-06-27 at 12:09 -0400, Rob wrote:
> Linux emulation on FreeBSD? It's just a simple utility for operating
> & running
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM, Vinum difference
On Wed, 2007-08-22 at 08:51 +0400, Rakhesh Sasidharan wrote: > Lowell Gilbert wrote: > > > Rakhesh Sasidharan <[EMAIL PROTECTED]> writes: > > > >> I see that if I want to do disk striping/ concating/ mirroring, > >> FreeBSD offers the GEOM utilities and the Vinum LVM (which fits into > >> the GEOM architecture). Why do we have two different ways of doing the ... > definitely a difference. Thanks! > > Another (related) question: both gvinum and the geom utilities like > gmirror and gstripe etc provide for RAID0, RAID1, and RAID3. Any > advantages/ disadvantages of using one instead of the other? It depends greatly upon your application and needs. A common practice in a common 6-disk capable server is to use a RAID1 set of smaller capacity, faster speed/RPM disks for RAID1 for the "system" file systems, while using a combination of larger, slower disks in a RAID1 set, then RAID0'd together for both space, performance, and redundancy. RAID1+0. ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: how to increase RAID space
UFS/FFS probably wont deal well with the underlying "logical"-physical
disk size changing (bytes/section, number of sectors, etc.). Even if it
was pure concatenation.
No, an LVM2/VxFS is needed.
Also, shops that can afford SAN and high end RAID tend to be able to
provision temp space to store media while they expand and re-create
volumes.
~BAS
On Wed, 2007-06-27 at 20:21 +1000, Norberto Meijome wrote:
> On Wed, 27 Jun 2007 17:07:32 +0700 (ICT)
> Olivier Nicole <[EMAIL PROTECTED]> wrote:
>
> > > that's what a volume manager (such as LVM2 in linux, Veritas Vol Mgr , and
> > > vinum (I think) in FBSD 4 ) do - they abstract the hardware storage
> > > layer.
> >
> > That is hardware RAID.
>
> yes, i realise you mentioned it . You'd imagine some raid card manufacturers
> would have something as flexible as LVM built into their cards by now... maybe
> someone does already.. ?
>
> _
> {Beto|Norberto|Numard} Meijome
>
> "Those who do not remember the past are condemned to repeat it."
>George Santayana
>
> I speak for myself, not my employer. Contents may be hot. Slippery when wet.
> Reading disclaimers makes you go blind. Writing them is worse. You have been
> Warned.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>
>
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror
The size colum can be human readable number (ex, "5g") and the offset can be the name of the previous partition. For the offset and size of the first and last partitions respectively use "*". Read the disklabel(8) man page for more details -- it is actually a real well written one. I wouldn't worry about exact replication -- the sector sizes and total sectors of the logical gmirror volume and the underlying phyiscal disk will always be different -- that's the nature of LVM. Just make them relatively close and match up the letters. ~~BAS On Wed, 2007-06-27 at 14:16 -0400, [EMAIL PROTECTED] wrote: > Quick question, I am configuring gmirror to mirror certain slices on my > hard drives.. I want to mirror /dev/ad0s1 (700M) to another drive.. I am > fine with configuring gmirror and getting it running but I am unsure of > how I create the BSD slices with bsdlabel -e.. > > When I do a bsdlabel -e /dev/ad0s1 I get: > > # /dev/ad0s1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 40960004.2BSD 2048 16384 25608 > c: 14297220unused0 0 # "raw" part, > don't edit > d: 1020122 4096004.2BSD 2048 16384 63760 > > When I initially create the mirror on the backup disk, I run a bsdlabel -e > /dev/mirror/gm0s1 and this is what it shows: > > # /dev/mirror/gm0s1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 1429705 16unused0 0 > c: 14297210unused0 0 # "raw" part, > don't edit > > My initial instinct was to mirror the bsdlabel output from ad0s1 but with > just the 16 offset for the 'a' slice coming out with: > > # /dev/mirror/gm0s1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 409584164.2BSD 2048 16384 25608 > c: 14297210unused0 0 # "raw" part, > don't edit > d: 1020122 4095844.2BSD 2048 16384 63760 > > Is my assumption correct? Or am I missing something here? > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CPU Monitoring Software
And for visual historical data, use MRTG. ~BAS On Fri, 2007-09-28 at 15:30 +0200, Dominique Goncalves wrote: > Hi, > > On 9/28/07, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > I was wanting to see what my servers utilize as far as memory, disk, cpu, > > etc. over a certain time period. Is there some software that I can use? > > I guess something like the 'top' command that gives an average output over > > a certain time. > > > > I downloaded sysstat for my linux boxes, but it does not want to compile > > under freebsd. > > What about using systat(1) ? :-) > It's already in the base system. > > HTH, > Regards. > > > Thanks. > > > > -- > > Scott Mayo > > System Administrator > > Bloomfield Schools > > > > Gun Control: Belief that violent predators willing to ignore laws against > > robbery, kidnapping, rape, and murder will obey a law telling them that > > they cannot do so with a gun. > > > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0, Open LDAP, PAM, TLS and NSS, howto?
FreeBSD 5.x and 6.x work fine with both PAM and NSS -> LDAP w/ TLS (PKI). All other services (RADIUS, Apache ((mod_ldap, mod_pam_auth), PHP, interactive shell, SFTP, etc.) can be tied into LDAP either directly or via PAM. As for password change, I don't know if anyone has a passwd(1) binary that properly changes the LDAP password attribute -- if there is and its out there, it requires ACL insanity. Like Oracle, you can either understand OpenLDAP ACLs, or you have real work to do >:} Check the nss_pam.conf and nss_ldap.conf configs in local/etc/* -- set to "debug 1" to get debugging info. Feel free to share error messages. ~BAS On Fri, 2007-09-28 at 10:54 +, O. Hartmann wrote: > Hello out there, > I have a problem with setting up an FreeBSD box as OpenLDAP server with > several services, like SAMBA, NFS. > > The intention is to have a FreeBSD 7.0 fileserver (NFS, SAMBA) also > acting as OpenLDAP server. So far. OpenLDAP is up and running, using > TLS/SSL certificate. SAMBA is also up and running - but it never > connects to the OpenLDAP server due to an connection error, but this > shouldn't be the subject here, I have more basic questions about what > FreeBSD already has and what to install additionally. > > I want customers to log in on the FBSD box, so they sould log in > (authenticated via OpenLDAP), change their passwords and shells and > those user specifica should be updated on the LDAP server. > > I already installed pam_ldap-port but ran into trouble because FreeBSD's > nss obviously does not have a tag 'ldap' to refere to an OpenLDAP server > (and not files). > Well, I'm confused and not very firm with OpenLDAP/PAM/NSS stuff, > especially if SSL/TLS come into play and I would like to ask those > herein administering those setups, especially within a hybrid NFS/SAMBA > fileservicing environment, where to find up to date > informationes/howto/tipps. > > Most websites and HowTo's I found were Linux related or, if related to > FreeBSD, outdated. > > Sorry beeing so unspecific, but the problem is complex (to me) so I > would better ask for those who are willing to help or give hints and tips. > > Thanks in advance and for your patience, > Oliver > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 amd64 ufs_dirbad
Can you post your dmesg(8) from /var/run/dmesg(8) so that we can see your SATA controller information? Can you try loading /usr/obj and /usr/src onto an alternate disk to see if the problem is controller/HBA/sata cable/disk related? ~BAS On Fri, 2007-09-28 at 10:33 -0700, Eric Osterweil wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > I've been chasing my tail with a problem for a few days now and I'm > about to throw in the towel. I have a Tyan Thunder K8SR w/ 2 > amd64's, 6GB of mem, and a 250 GB SATA drive. > > I've been trying to get FreeBSD 6.2 amd64 on it. When I do the > install, if I try to put the ports on, it reliably crashes with a > ufs_dirbad. I can install w/o the ports. I found a ref to booting > with: > set hw.physmem="4G" > and that gets me through (w/ the ports). > > When I buildworld, I eventually get the same ufs_dirbad. > > I have swapped out the drive and tried a new one (same problem). > WHenever I reboot (at all) if I fsck I see lots of filesystem > errors. I just did a memtest86 over night, and found no problems. > > Can anyone help me out here? I can provide any other info that would > help. > > Thanks, > > Eric > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFG/Tr8K/tq6CJjZQIRAjwKAJ48hBPeFwnSBQaykw7rJsNW49Rt3wCeO0HY > yxThKkuyCTPJOjfTw2KWsp4= > =syDq > -END PGP SIGNATURE- > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to restart a freezed tty?
On Sat, 2007-09-29 at 13:16 +0330, Bahman M. wrote: > Hi all, > > For some reason all the ttys are frozen up; I can switch between X and > them back and forth but not between the ttys themselves using ALT+Fn. Can you start new xterms? When you say 'frozen', do they "not accept keyboard input"? Is it possible scroll-lock is enabled? What about the TTY that you started Xorg from? Is this temporal? When did it start happening? Is there anything in /var/log/messages? Did you try: $ sudo pkill -HUP init ? ~BAS > I tried killing them; they terminate and restart but still > frozen. I don't believe the only way out is to restart the system. > > How to make ttys behave normally? I'd appreciate any idea. > FreeBSD 6.2-RELEASE-p7 > xorg-7.2 > fluxbox-1.0rc3_3 > > TIA, > > Bahman > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: using the date command
To set time: $ sudo /usr/sbin/ntpdate pool.ntp.org 29 Sep 23:48:31 ntpdate[9404]: adjust time server 66.250.45.2 offset 0.001289 sec To date info about your timezone settings: $ zdump /etc/localtime /etc/localtime Sat Sep 29 23:49:19 2007 EDT Options: $ ls /usr/shaoneinfo/ | egrep -v "^d" total 78 -rw-r--r-- 1 root wheel755 Aug 22 11:11 CET -rw-r--r-- 1 root wheel837 Aug 22 11:11 CST6CDT -rw-r--r-- 1 root wheel679 Aug 22 11:11 EET -rw-r--r-- 1 root wheel 56 Aug 22 11:11 EST -rw-r--r-- 1 root wheel837 Aug 22 11:11 EST5EDT [...] To set timezone: $ ln -s /share/zoneinfo/$WHATEVER /etc/localtime For you probably PST8PDT. For your best NTP experience, use OpenNTP from ports: /usr/ports/net/openntpd/ ~BAS On Sat, 2007-09-29 at 20:33 -0700, jekillen wrote: > Hello all; > I have built 4 machines and installed FreeBSD 6.0 in one and 6.2 > in the other three. They are all using the wrong date and time. > The last one (v6.2 on ecs mb with AMD64) is the worst. It is telling > me today is Jan 3 2003 PST (I am on the west coast and it is still PDT). > These machines are all web servers. So up until now this has not been > a big issue but a configuration of software is complaining that the > files > it creates have an older date than the files in the software bundle, > it is time to do something about it. So I am looking at man date and as > I interpret the instructions #date ccyymmddHHMM.ss (20079282027.00 or > 200709282027.00 for instance) is supposed to set the > clock to the current date. But when I run a command with the > current date and time in the above format I get the complaint that > the format string is wrong. > Can anyone be kind enough to give me a quick tutorial on this? > I will be looking seriously into using NTP, but for now I need to > get the date straight. I have entries in apache error log gener > ated by php scripts that are supposed to use its date command. > Thanks in advance for assistance. > Jeff K > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0, Open LDAP, PAM, TLS and NSS, howto?
There should be an nss_ldap.conf and pam_ldap.conf in /usr/local/etc . You need to set a variety of settings there. What do they look like? Remember: pkg_info -L pam_ldap nss_ldap! Also, not sure about the TCP FIN_2 issue -- probably just the usual shakes and bangs with -current. ~BAS On Fri, 28 Sep 2007, O. Hartmann wrote: Thank you for responding. So, I'll feel free reporting my bad luck. This is a reference page I consulted for some hints, but without success: http://www.cultdeadsheep.org/FreeBSD/docs/Quick_and_dirty_FreeBSD_5_x_and_nss_ldap_mini-HOWTO.html First, OS ist the most recent FreeBSD 7.0. OpenLDAP is openldap-server-2.3.38, standard config, no SASL support or anything else apart from default PAM_LDAP NSS_LDAP I renamed cached.conf to nscd.conf as suggested (for your information). In /etc/nsswitch.conf I changed # # nsswitch.conf(5) - name service switch configuration file # $FreeBSD: src/etc/nsswitch.conf,v 1.1 2006/05/03 15:14:47 ume Exp $ # group: files ldap group_compat: nis hosts: files dns networks: files passwd: files ldap passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files I also changed /etc/pam.d/sshd to this: # # $FreeBSD: src/etc/pam.d/sshd,v 1.16 2007/06/10 18:57:20 yar Exp $ # # PAM configuration for the "sshd" service # # auth authsufficient pam_opie.so no_warn no_fake_prompts authrequisite pam_opieaccess.so no_warn allow_local #auth sufficient pam_krb5.so no_warn try_first_pass authsufficient /usr/local/lib/pam_ldap.so no_warn try_first_pass authsufficient pam_ssh.so no_warn try_first_pass authrequiredpam_unix.so no_warn try_first_pass # account account requiredpam_nologin.so #accountrequiredpam_krb5.so account requiredpam_login_access.so account requiredpam_unix.so # session #sessionoptionalpam_ssh.so session requiredpam_permit.so # password #password sufficient pam_krb5.so no_warn try_first_pass passwordrequiredpam_unix.so no_warn try_first_pass Both configuration files for nss_ldap and pam_ldap respective got linked to /usr/localetc/openldap/ldap.conf, which looks like this: # # LDAP Defaults # # See ldap.conf(5) for details # This file should be world readable but not world writable. BASEdc=foo,dc=org #URIldapi:/// URI ldapi://%2fvar%2frun%2fopenldap%2fldapi/ #SSL start_tls #SIZELIMIT 12 #TIMELIMIT 15 #DEREF never #TLS_CACERT#TLS_CERT #TLS_KEY #TLS_REQCERTallow #TLS_REQCERTdemand #TLS_CHECKPEER yes My /etc/rc.conf.local file has the following OpenLDAP specific entry: ### ### OpenLDAP Server ### ### slapd_enable="YES" #slapd_flags='-d 3 -4 -s 4 -h "ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap:/// ldaps:///"' slapd_flags='-4 -s 4 -h "ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap://192.168.2.210 ldaps://192.168.2.210"' slapd_sockets="/var/run/openldap/ldapi" My OpenLDAP config file has SSL-certificates disabled. After the installation of nss_ldap the slapd server takes several decades of seconds to start. But it starts well and after it has initiated itself, I can do on the server a simple 'slapcat' and receive. But I can't access the LDAP server. Doing an 'id testuser' results in 'id not found'. On the console, I receive massively errors like this: TCP: [127.0.0.1]:389 to [127.0.0.1]:63896 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received data after socket was closed, sending RST and removing tcpcb Well, I checked sockstat for a listening slapd and I found slapd listening on both loopback, local NIC adn on both ports 389 and 636. So what is wrong ? Regards, a desperate Oliver Brian A. Seklecki wrote: FreeBSD 5.x and 6.x work fine with both PAM and NSS -> LDAP w/ TLS (PKI). All other services (RADIUS, Apache ((mod_ldap, mod_pam_auth), PHP, interactive shell, SFTP, etc.) can be tied into LDAP either directly or via PAM. As for password change, I don't know if anyone has a passwd(1) binary that properly changes the LDAP password attribute -- if there is and its out there, it requires ACL insanity. Like Oracle, you can either understand OpenLDAP ACLs, or you have real work to do >:} Check the nss_pam.conf and nss_ldap.conf configs in local/etc/* -- set to "debug 1" to get debugging info. Feel free to share error messages. ~BAS On Fri, 2007-09-28 at 10:54 +, O. Hartmann wrote:
Re: passwd(1) and LDAP (was Re: FreeBSD 7.0, Open LDAP, PAM, TLS and NSS, howto?)
Does it log in as the LDAP user or the PAM super-user to do the attribute
change? I'll check out the source...but that's great news. ~BAS
On Mon, 1 Oct 2007, Jonathan McKeown wrote:
On Friday 28 September 2007 16:29, Brian A. Seklecki wrote:
FreeBSD 5.x and 6.x work fine with both PAM and NSS -> LDAP w/ TLS
(PKI).
All other services (RADIUS, Apache ((mod_ldap, mod_pam_auth), PHP,
interactive shell, SFTP, etc.) can be tied into LDAP either directly or
via PAM.
As for password change, I don't know if anyone has a passwd(1) binary
that properly changes the LDAP password attribute -- if there is and its
out there, it requires ACL insanity.
The passwd(1) program was rewritten some time ago to use PAM, but a test was
left in which prevents it doing so. I have asked, both on this list and on
freebsd-hackers in the last few weeks, whether there is any reason other than
historical to leave this test in, and been deafened by the silence. There are
a couple of PRs either open or suspended regarding this issue.
I diked out the whole switch statement and replaced it with a single printf,
and it works for changing LDAP passwords. I haven't thoroughly tested to see
if it causes any other problems.
Jonathan
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"Guilty? Yeah. But he knows it. I mean, you're guilty.
You just don't know it. So who's really in jail?"
~Maynard James Keenan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fibre Channel Card Detection
We need to see your dmesg(8) output from /var/run/dmesg.boot and/or the output of "pciconf -v" / "scanpci" / "lspci" ~BAS ~BAS On Wed, 2007-10-03 at 11:34 -0700, Sean Murphy wrote: > I have a Qlogic PCIe Fibre Channel card installed in my FreeBSD 6.2 > Release server. I do not see it listed on boot up of the server. I > have also run dmesg with no luck. How do I find out if it is detected > and how would it be listed as. > > Thanks > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange df
The math is off because some space is reserved for UID 0 / root. Read these two man pages: ~BAS NEWFS(8) FreeBSD System Manager's Manual NEWFS(8) NAME newfs -- construct a new UFS1/UFS2 file system -m free-space The percentage of space reserved from normal users; the minimum free space threshold. The default value used is defined by MINFREE from , currently 8%. See tunefs(8) for more details on how to set this option. TUNEFS(8) NetBSD System Manager's ManualTUNEFS(8) NAME tunefs -- tune up an existing file system -m minfree This value specifies the percentage of space held back from nor- mal users; the minimum free space threshold. The default value is set during creation of the filesystem, see newfs(8). This value can be set to zero, however up to a factor of three in throughput will be lost over the performance obtained at a 5% threshold. Note that if the value is raised above the current usage level, users will be unable to allocate files until enough files have been deleted to get under the higher threshold. On Fri, 2007-10-05 at 12:12 +0200, Albert Shih wrote: > Hi all > > What's that mean ? > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /dev/ad4s1a50763069050 39797015%/ > devfs 110 100%/dev > /dev/ad4s1g 78017664 55539220 1623703277%/home > /dev/ad4s1e507630-8960 475980-2%/tmp > ^^ > > Regards. > > > > > -- > Albert SHIH > Observatoire de Paris Meudon > SIO batiment 15 > Heure local/Local time: > Ven 5 oct 2007 12:11:30 CEST > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bind configuration in FreeBSD
You need to enable the service: $ sudo vi /etc/rc.conf >> named_enable="YES" :wq $ sudo /etc/rc.d/named restart The bind in-tree is 9.3.4 and the chroot is already setup for you by default. You don't want to go installing a bitrot version from Ports. ~BAS On Fri, 2007-10-05 at 12:08 +, dhaneshk k wrote: > but no message that it is starting or not . ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange df
On Fri, 2007-10-05 at 13:11 +0300, Ivailo Tanusheff wrote: > This seams as a wrong lable info. > Check: bsdlabel /dev/ad4s1 Oh wow, yea, I misread. That's really scarry -- normally the kernel would panic. I'm very surprised bsdlabel(8) let you write that to the disk. Does fsck(8) function? Did sysinstall do this? You probably want /tmp to be MFS anyway -- it's almost never a disk partition. Especially since you don't have /var on its own file system (/var/tmp) ~BAS IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BASH as root shell (static linking)
On Sat, 2007-10-06 at 04:54 +1000, Jerahmy Pocott wrote: > Hello, > > I'm wanting to use BASH as my root shell, so I compiled a statically > linked > version then tried to log in with only / mounted. But I was locked > out because > elf.ld.so could not be found.. JP: Did: $ ldd /bin/bash Return anything? It should not. ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a SAN using FreeBSD
On Sat, 2007-10-06 at 14:00 -0700, Don O'Neil wrote: > Anyone have any resources for building a FreeBSD based SAN device? IE, how > can I create an extendable file system using networked drives in muliple Spinnaker Networks, (spinnakernet.com), of Pittsburgh, Pennsylvania, a hardware company which builds network attached storage (NAS) servers. But they got gobbled up by NetApp =/ ~BAS > boxes without paying a billion dollars for someones expensive drive arrays. > > TIA! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sudo doesn't log anything
On Wed, 2007-10-10 at 18:38 +0200, Nicolas Letellier wrote: > Pieter de Goeje a écrit : > > Sudo by default logs with facility 'local2' and priority 'notice'. Neither > > one > > is specified in your syslog.conf. > > To set the facility in sudoer(5): Defaultssyslog=auth Or local0-7 if you have a lot of action. ~BAS > Yes, it fix my problem ! > > Thanks very much ! > > Nicolas > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install on new INTEL motherboard, can't find ATA devices
On Mon, 2007-10-22 at 15:13 -0400, Thomas David Rivers wrote: > I just got a new INTEL motherboard - chock full of these new-fangled > SATA connectors... and one "legacy" ATA connector. I moved a disk > drive from an older box to this new one.. > > The machine can boot from the disk drive, but then after the kernel > is up-and-running - it can't find the drive to mount the root file > system. Can you paste your complete /var/run/dmesg.boot from the boot kernel? Did you try a 7-PRERELEASE snapshot? Are there any modes to toggle in the BIOS? ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Live video streaming on FreeBSD?
> /usr/ports/multimedia/mencoder can encode/recode videos to many > different formats, including wmv9 and H.264. > > /usr/ports/multimedia/vlc contains a streaming server, IIRC. Do any of these support multicast? Cisco is pushing this big time with AVVID. -- Brian A. Seklecki <[EMAIL PROTECTED]> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Live video streaming on FreeBSD?
On Wed, 24 Oct 2007 17:35:34 +0300
Nikos Vassiliadis <[EMAIL PROTECTED]> wrote:
> On Wednesday 24 October 2007 17:03:57 Brian A. Seklecki wrote:
> > > /usr/ports/multimedia/mencoder can encode/recode videos to many
> > > differen
Well, no, its just that the 99% of the managed switches & routers out
there are going to ("need to") support multicast video delivery
they way they want.
~BAS
IMPORTANT: This message contains confidential information and is intended only
for the individual named. If the reader of this message is not an intended
recipient (or the individual responsible for the delivery of this message to an
intended recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
release(8) environmental variables
As far as building goes, the variables in play are: DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR, CHROOTDIR, CVSROOT, EXTSRCDIR, EXTDOCDIR, BUIILDNAME, RELEASETAG, NODOC, NOPORTS, WORLD_FLAGS, LOCAL_SCRIPT For stage one of the release process, the following seem relevant: DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR For stage two: CHROOTDIR, CVSROOT, EXTSRCDIR, EXTDOCDIR, BUIILDNAME, RELEASETAG, NODOC, NOPORTS, WORLD_FLAGS, LOCAL_SCRIPT Do you guys prefer to set these in make.conf(5) or as exported environmental variables in the shell that spawn's make(1) ? ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncftpput & ncftpget
To find out:
$ cd /usr/ports && egrep -i ncftp* {ftp,net}/*/PLIST*
~BAS
On Tue, 2007-10-30 at 08:48 -0400, Bill Banks wrote:
> What port should I make to get ncftpput?
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization
On Tue, 2007-10-30 at 09:03 -0400, Bart Silverstrim wrote: > I was curious with the information coming out regarding FreeBSD 7 what > option are available for virtualizing other OS's using FreeBSD as a host. Just jail(8) atm. VMWare wont issue keys for the last known-working of VMWare server/WS that ran on FreeBSD under Linux emulation. Their loss. ~BAS P.S. I'm considering using my bsd-appliance project to do an ultra-thing Xen hypervisor based on a NetBSD host. A kernel with IP, iSCSI, NFS etc. It can probably be done using less RAM than the ATI framebuffer robs. ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Xorg and WSXGA
On Mon, 2007-10-29 at 23:36 -0700, Crist J. Clark wrote: > I finally dumped the CRT and bought a ridiculusly cheap 20" > LCD monitor. Works great except I'm having problems getting it > to go widescreen and use the full display area. > > I followed the instruction xinit -- -verbose 9 -logverbose 9 It should print out a list of modes that it _will_ validate. ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release(8) environmental variables
On Wed, 2007-10-31 at 13:54 +0200, Giorgos Keramidas wrote: > On 2007-10-30 18:02, "Brian A. Seklecki" <[EMAIL PROTECTED]> wrote: > > > > As far as building goes, the variables in play are: > > > > DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR, CHROOTDIR, CVSROOT, > > EXTSRCDIR, EXTDOCDIR, BUIILDNAME, RELEASETAG, NODOC, NOPORTS, > > WORLD_FLAGS, LOCAL_SCRIPT > > > > For stage one of the release process, the following seem relevant: > > > > DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR > > > > For stage two: > > > > CHROOTDIR, CVSROOT, EXTSRCDIR, EXTDOCDIR, BUIILDNAME, RELEASETAG, NODOC, > > NOPORTS, WORLD_FLAGS, LOCAL_SCRIPT > > > > Do you guys prefer to set these in make.conf(5) or as exported > > environmental variables in the shell that spawn's make(1) ? I ask because I noticed that the following variablkes do not get honored by "make release" that occurs inside the chroot() as spawned by "make release" (presumably during release.5) DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR For example, OBJs get sent right into $CHROOTDIR/usr/obj/, which really sucks. ~BAS > > make.conf is too invasive. I just set them in a shell script called > `bldenv.sh' and saved in the release-checkout area :) > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release(8) environmental variables
really sucks.
I believe that's intentional, so re-running "make release" with
different CHROOTDIR values will produce consistently "similar" binaries.
I use LOCAL_SCRIPT to copy /etc/make.conf (well, /etc/src.conf) into place
inside the jail for the rebuild so that I can build a custom internal
release w/o certain subsystems (IPv6 or CSH, for example)
Is there a better way to do it?
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"Guilty? Yeah. But he knows it. I mean, you're guilty.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
iso.1 target and release(8) in RELENG_7 (WAS: Re: release(8) environmental variables)
Here's some fun -- I'm pretty sure this worked in RELENG_6: "make release" in /usr/src/release into RELEASEDIR=/opt/releasedir The rebuild completes (release.1 -> release.8), the kernels are built, the file system layout is prepared (ftp.1 -> cdrom.3), then (I think) the iso.1 target is called and the images are zero-bytes. Log excerpts below... Either I'm confused, I have my environmental variables set wrong, or this is broken. :) 1) My $LOCAL_SCRIPT properly copies mkisofs(1) and mkhybrid(1) into place in the $CHROOTDIR/usr/bin $ ls -al /opt/relchroot/usr/bin/mkisofs -r-xr-xr-x 1 root wheel 510712 Nov 1 02:13 /opt/relchroot/usr/bin/mkisofs 2) On the root of the system, I have to make /R a sylink to /opt/relchroot/R to make "make iso.1" succeed : # ls -al /R lrwxr-xr-x 1 root wheel 16 Oct 29 23:20 /R -> /opt/relchroot/R Other-wise: [EMAIL PROTECTED] /usr/src/release]# make iso.1 Creating ISO images... mkisofs: No such file or directory. Invalid node - /R/cdrom/bootonly *** Error code 2 Stop in /usr/src/release. 3) I don't see how $CHROOTDIR is used in /usr/src/release/Makefile at: iso.1: [...] Unless, when not run as a manual target outside of the chroot(), it runs in the chroot and /R is relative to $CHROOTDIR?. That would make sense of the error in the log excerpt below matched what I encounter on the command line as a manual run. I'm setting: # applies to build export DESTDIR=/opt/dest export MAKEOBJDIRPREFIX=/opt/obj export RELEASEDIR=/opt/release export CHROOTDIR=/opt/relchroot This is a shell script that runs nightly -- it worked in RELENG_6. ~BAS [...] Created /R/stage/floppies/boot.flp touch floppies.1 touch floppies.3 Setting up FTP distribution area 0 blocks 0 blocks touch ftp.1 Building CDROM live filesystem image 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks Copy GENERIC kernel to boot area Setting up CDROM boot area touch cdrom.1 Building CDROM disc1 filesystem image 0 blocks 0 blocks Building CDROM disc2 filesystem image touch cdrom.2 Building bootonly CDROM filesystem image touch cdrom.3 Release done [...] On Wed, 2007-10-31 at 19:45 +0200, Giorgos Keramidas wrote: > On 2007-10-31 13:26, "Brian A. Seklecki" <[EMAIL PROTECTED]> wrote: > >>> really sucks. > >> > >> I believe that's intentional, so re-running "make release" with > >> different CHROOTDIR values will produce consistently "similar" binaries. > > > > I use LOCAL_SCRIPT to copy /etc/make.conf (well, /etc/src.conf) into place > > inside the jail for the rebuild so that I can build a custom internal > > release w/o certain subsystems (IPv6 or CSH, for example) > > > > Is there a better way to do it? > > LOCAL_SCRIPT sounds fine to me :) > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Pioneer DVR-112D/1.21 refuses to write CDs, only writes DVDs
On Sat, 2007-11-17 at 20:26 -0800, Yuri wrote: > I bought the new DVD writer -- Pioneer DVR-112D. > > But every time I try to write data CD or audio CD it gives Input/Output error. > > It can read CDs and write and read DVDs no problem. > > Anybody else has this problem? What is the solution? Are you using burncd(1) or ports/sysutils/cdrtools ? Are you getting DMA errors to kernel msgbuf or simple 1-line I/O error? ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Pioneer DVR-112D/1.21 refuses to write CDs, only writes DVDs
Normally that means that the drive is not ready to burn (Door not closed, or media not ready). Its possible that the driver is sensing that data wrong from the hardware, too. You only have the one drive in the system? No possible /dev/ confusion? Try cdrtools (Good luck with the syntax) ~BAS On Sat, 17 Nov 2007, Yuri wrote: Are you using burncd(1) or ports/sysutils/cdrtools ? Are you getting DMA errors to kernel msgbuf or simple 1-line I/O error? I am using burncd. There is only one-line I/O error. l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail?" ~Maynard James Keenan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Release 7.0 Beta2
On Sun, 2007-12-09 at 09:36 -0800, Srinivasa R Kanduru wrote: > Hi, > > I was trying to install FreeBSD 7.0 Beta2 on a dell x86 machine which use the bios menu to set the keyboard mode to compat/ps/2 emulation mode. Also try unplugging & reconnecting the usb keyboard post-boot. Is this a a Optiplex 755 or 745? ~BAS > doesn't have any PS2 ports. The installer expects a PS2 keyboard I think. > The USB port is disabled for some reason and it is not possible to proceed > further in the installation process. > > Is this a known issue ? Does the installer doesn't recognize a USB keyboard > ? > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rc: not working as expected? (round 2)
You can do a dry run as a non root user: $ rcorder /etc/rc.d/* /usr/local/etc/rc.d* 2>&1 | more ~BAS On Fri, 2008-10-10 at 12:19 -0300, Paul Halliday wrote: > (I mistakenly sent the last msg before finishing..) > > Or maybe an interpretation issue. > > I have a few startup scripts in rc.d and I am experiencing timing > issues. i.e. I need xyz to start before abc. > > Within xyz I tried: > > # REQUIRE: abc > > This didn't work so I tried: > > 100.xyz > 900.abc > > which doesn't appear to work either. > > What am I missing? > > Thanks. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup.uk.freebsd.org down
Did it ever come back?
Someone with good BGP views should probably put all of the CVS/FTP/Rsync
mirrors in Nagios (with something reasonable like a 6 hour check interval)
and send reports to freebsd-www@ or so.
~BAS
On Mon, 8 Sep 2008, Paul Macdonald wrote:
I just noticed this cvs server is down
I've switched to cvsup2 which seems fine for now, I presume any updates to 2
are not dependent on cvsup.uk.freebsd being up?
thanks
Paul.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"Guilty? Yeah. But he knows it. I mean, you're guilty.
You just don't know it. So who's really in jail?"
~Maynard James Keenan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup mirrors
Or...contact the maintainer: http://www.dslreports.com/profile/191119 $ host cvsup1.ca.FreeBSD.org cvsup1.ca.FreeBSD.org is an alias for less.cogeco.net. less.cogeco.net has address 24.226.6.67 http://less.cogeco.net/ Many broken URLS. ~BAS On Fri, 12 Sep 2008, Michael P. Soulier wrote: I found this http://www.freebsd.org/doc/en/books/handbook/cvsup.html#CVSUP-MIRRORS and it lists one for me in Canada. cvsup1.ca.freebsd.org Unfortunately, it doesn't have RELENG_6 on it. cvsup says it's not there. Does the mirrors list need an update? Thanks, Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail?" ~Maynard James Keenan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core Dumb during CVSUP
use csup, but at this stage, i'll wait untill portupgrade has finished to see if anything changes in that reguards. Well, you could ktrace(8) the binary and/or rebuild it with debugging symbols and bt the coredump ~BAS ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Check_CVSUp / PServer - Nagios Plugins?
Hey all: One of the big pitfalls of running a public CVS/CVSup/FTP mirror seems to be poor reporting on failed updates. I'd like add some Nagios monitoring to our project. For FTP and CVSUP rsyncs, I can have my cron(8)'d update scripts touch(1) a file if [ $? = 0 ]; then check them with libexec/nagios/check_file_age for mtime/utime. However, I'd also like to monitor the CVSup and PServer services as well at the protocol level. There do not seem to be any plugins in the public domain. Ideas: CVSUp: - php/perl/python bindings/libraries to talk cvsup protocol and maybe query a list of collections, plus the protocol version negotiated? - Is there maybe a way to exec() the cvsup(1)/csup(1) client in "list" mode? Does the protocol have a list operation? CVS Pserver: - Maybe just do a "cvs log src/Makefile" -- verifies that the protocol is active. SSH: - Duh FTP/RSYNC: - Yea Thougths? Discussion? l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail?" ~Maynard James Keenan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Errors found in Freebsd
On Wed, 2008-10-22 at 13:04 +0200, Leon Swanepoel - MWEB wrote: > 2650 machines that are constantly running Ierrs. The bce,em,xl or any Yea -- call Dell and ask them why they started shipping crappy chips in the 9th gen. Probably to sell lots of PCI-E dual port addon cards, which is my suggestion to anyone who lives or dies by PowerEdge. -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any help about FreeBSD & Dell's Troubleshooting Tool DSET
On Wed, 2008-11-12 at 16:01 +0100, VeeJay wrote: > There seemed to be a problem related to RAID controller on > one server. Screw Dell's diagnostics tools. Those are there to help psychology majors who got their MCSE and RHCE after they realized that all you can do with a psychology degree is teach psychology or serve coffee. Send us your screenshot. Nothing was attached. -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any help about FreeBSD & Dell's Troubleshooting Tool DSET
On Wed, 2008-11-12 at 19:39 +0100, VeeJay wrote: > Hi Brian > > Thanks. I sent the attachment but FreeBSD List would not allow me to First order of business is to _not_ send it as a BMP. Use PNG instead, and post the URL and not the actual file: http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png --- Second order of business: "Unexpected sense code" on a PD (Physical Disk) suggests that one of your disks is bad / becoming bad. Check the enclosure -- likely it is flashing. Install MegaCli from ports, if you can. You can always reboot and use the BIOS menu to check the event log. If its not a bad disk, then something bizarre is happening. We'll want to know what firmware revision you're running on the controller, and on the disks (Dell disk firmware updates run from DOS) ~~BAS > send email of more than 200K in size. So, here it is... > > I hope you can figure out how to solve this issue... > > With best wishes > > VJ > > > On Wed, Nov 12, 2008 at 4:25 PM, Brian A. Seklecki > <[EMAIL PROTECTED]> wrote: > On Wed, 2008-11-12 at 16:01 +0100, VeeJay wrote: > > There seemed to be a problem related to RAID controller on > > one server. > > Screw Dell's diagnostics tools. > > Those are there to help psychology majors who got their MCSE > and RHCE > after they realized that all you can do with a psychology > degree is > teach psychology or serve coffee. > > Send us your screenshot. Nothing was attached. > > -- > Brian A. Seklecki <[EMAIL PROTECTED]> > Collaborative Fusion, Inc. > > > > > IMPORTANT: This message contains confidential information and > is intended only for the individual named. If the reader of > this message is not an intended recipient (or the individual > responsible for the delivery of this message to an intended > recipient), please be advised that any re-use, dissemination, > distribution or copying of this message is prohibited. Please > notify the sender immediately by e-mail if you have received > this e-mail by mistake and delete this e-mail from your > system. > > > > > > -- > Thanks! > > BR / vj -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PXE Boot - Silent kernel dmesg output
All: Has anyone experience a PXE boot problem on amd64 (Dell PowerEdge 850, 1850, DRAC4, DRAC5) where kernel dmesg output is suppressed on VGA Console? I've tried kernels, mfsroot, and pxeboot from 6.4-RC2, 6.3-PLX, 7.1-B2 builds. I've verified stock /boot/device.hints, /defaults/loader.conf, and /boot/loader.conf are in place on my NFS export. Here's a slightly ambiguous screenshot: http://people.collaborativefusion.com/~seklecki/pxe_lock.jpg Note: Its hard to tell, but the spindle has already become a block cursor. We used to see this in early 6.x days and assumed it was a bum bPXE configuration on the server-side; eventually mfsroot would get loaded and sysinstall(8) welcome would be the first thing displayed after the 2nd stage boot loader. Breaking out of the loader reveals: console="vidconsole" Very very strange... I'm going to have a look at tcpdump(8) on NFS reads to my export and determine if it is indeed actually reading loader.conf(5). However, the system-wide defaults w/o loader.conf + loader.rc + boot.conf shouldn't prohibit kernel VGA console output. -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mfi(4) lockups and the adapter event log
> with linux-megacli showed TONS of messages. Trying to clear them using > linux-megacli seemed to cause a similar lockup, filled with command > timeouts, but no fatal firmware error. Also, does anyone know if the mfiutil(8) util in RELENG_8 has the ability to purge the event log? Man page 'clear' command nukes the volume configuration >:} We don't have RELENG_8 on a PowerEdge system yet. ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Urgent: filesystem "full", though space is available
> > i need to get this space released ASAP! Can anyone help? > > Please see the FreeBSD FAQ entries on "The du and df commands show > different amounts of disk space available. What is going on?" and "How > is it possible for a partition to be more than 100% full?" Also be sure to: $ alias df="/bin/df -hi". Inodes at 100% capacity (such as a sendmail clusterfuck) can cause file system-full error messages. This is why you should have partitioned off /var ~BAS -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fault tolerance with FreeBSD for old DOS app
On Mon, 2008-03-24 at 19:36 +0200, B. Bonev wrote: > I want advice for old DOS app on Windows PC, that I need to make on 2 PC-s > fault tolerant. Any advice for working solution on FreeBSD? Yep...rewrite the database in SQL with a PHP front end. Import the data from the old system. Use a Radware/F5 Load Balancer for the web and Slony-I for the database replication. Welcome to 2008. ~BAS P.S. In reality you could likely do a HA-VMWare GSX virtual machine with synchronized failover, but that's off-topic here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Working /etc/pam.d/sshd file with pam_ldap 6.3 or 7.0 ?
The problem is that the PAM libraries provide a shit-fuck-ass-worthless debug mechanisms. This only eclipsed by the terribly organized information on LDAP+NSS+PAM for FreeBSD on the web. The file is the same for pam.d/system and /usr/local/etc/pam.d/sudo. Please put this on the OpenLDAP / PADL Wiki somewhere: [EMAIL PROTECTED]:/home/seklecki$ more /etc/pam.d/sshd # $FreeBSD: src/etc/pam.d/sshd,v 1.15 2003/04/30 21:57:54 markm Exp $ # # PAM configuration for the "sshd" service # # auth #auth requiredpam_nologin.so no_warn #auth sufficient pam_opie.so no_warn no_fake_prompts #auth requisite pam_opieaccess.so no_warn allow_local #auth sufficient pam_krb5.so no_warn try_first_pass #auth sufficient pam_ssh.so no_warn try_first_pass authsufficient /usr/local/lib/pam_ldap.so authrequiredpam_unix.so no_warn try_first_pass # account #accountrequiredpam_krb5.so account requiredpam_login_access.so account required /usr/local/lib/pam_ldap.so ignore_authinfo_unavail ignore_unknown_user account requiredpam_unix.so # session #sessionoptionalpam_ssh.so session requiredpam_permit.so session sufficient /usr/local/lib/pam_ldap.so no_warn try_first_pass # password #password sufficient pam_krb5.so no_warn try_first_pass passwordrequiredpam_unix.so no_warn try_first_pass #password required /usr/local/lib/pam_ldap.so no_warn try_first_pass Also try: $ grep -i debug /usr/local/etc/ldap.conf #debug 1 $ grep -i debug /usr/local/etc/nss_ldap.conf #debug 1 Higher levels for fun. ~BAS On Tue, 2008-03-25 at 15:34 +0100, Frank Bonnet wrote: > Hello > > I can't get a working sshd access using pam_ldap and nss_ldap > > /etc/nsswitch.conf is OK > > but I'm having difficulties to configure pam_ldap for a ssh access > on a machine ( 6.3 or 7.0 ) ... I have been trying a lot to configure > the /etc/pam.d/sshd file but haven't any success (sigh!) > > Anyone could helps ? > > Thanks a lot ! > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Working /etc/pam.d/sshd file with pam_ldap 6.3 or 7.0 ?
On Tue, 2008-03-25 at 16:31 +0100, Frank Bonnet wrote: > Hello Brian > > Thanks for the quick answer but I'm still in trouble Turn on the debugging flags in the configuration file for pam_ldap in /usr/local/etc and watch the console on the system. ~BAS > we I try to ssh connect to the machine I fall in a loop > like the following > > panzer:~> ssh [EMAIL PROTECTED] > Password: > Old Password: > Password: > Old Password: > Password: > > I am SURE the password I type works > > > > > Brian A. Seklecki wrote: > > The problem is that the PAM libraries provide a shit-fuck-ass-worthless > > debug mechanisms. This only eclipsed by the terribly organized > > information on LDAP+NSS+PAM for FreeBSD on the web. > > > > The file is the same for pam.d/system and /usr/local/etc/pam.d/sudo. > > Please put this on the OpenLDAP / PADL Wiki somewhere: > > > > [EMAIL PROTECTED]:/home/seklecki$ more /etc/pam.d/sshd > > > > > > # $FreeBSD: src/etc/pam.d/sshd,v 1.15 2003/04/30 21:57:54 markm Exp $ > > # > > # PAM configuration for the "sshd" service > > # > > > > # auth > > #auth requiredpam_nologin.so no_warn > > #auth sufficient pam_opie.so no_warn > > no_fake_prompts > > #auth requisite pam_opieaccess.so no_warn > > allow_local > > #auth sufficient pam_krb5.so no_warn > > try_first_pass > > #auth sufficient pam_ssh.so no_warn > > try_first_pass > > authsufficient /usr/local/lib/pam_ldap.so > > authrequiredpam_unix.so no_warn > > try_first_pass > > > > # account > > #accountrequiredpam_krb5.so > > account requiredpam_login_access.so > > account required /usr/local/lib/pam_ldap.so > > ignore_authinfo_unavail ignore_unknown_user > > account requiredpam_unix.so > > > > # session > > #sessionoptionalpam_ssh.so > > session requiredpam_permit.so > > session sufficient /usr/local/lib/pam_ldap.so no_warn > > try_first_pass > > > > # password > > #password sufficient pam_krb5.so no_warn > > try_first_pass > > passwordrequiredpam_unix.so no_warn > > try_first_pass > > #password required /usr/local/lib/pam_ldap.so no_warn > > try_first_pass > > > > > > Also try: > > > > $ grep -i debug /usr/local/etc/ldap.conf > > #debug 1 > > $ grep -i debug /usr/local/etc/nss_ldap.conf > > #debug 1 > > > > > > Higher levels for fun. > > > > ~BAS > > > > > > On Tue, 2008-03-25 at 15:34 +0100, Frank Bonnet wrote: > >> Hello > >> > >> I can't get a working sshd access using pam_ldap and nss_ldap > >> > >> /etc/nsswitch.conf is OK > >> > >> but I'm having difficulties to configure pam_ldap for a ssh access > >> on a machine ( 6.3 or 7.0 ) ... I have been trying a lot to configure > >> the /etc/pam.d/sshd file but haven't any success (sigh!) > >> > >> Anyone could helps ? > >> > >> Thanks a lot ! > >> > >> > >> ___ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suppressing "Limiting icmp unreach response" log messages
Install syslog-ng 2.x from ports.
source src { unix-dgram("/var/run/log");
unix-dgram("/var/run/logpriv" perm(0600));
internal(); file("/dev/klog"); };
Kernel messages from /dev/klog get mapped to "user.notice" syslog, so:
log { source(src); filter(f_user); filter(f_notice);
destination(mailadmin); };
Or the destionation of your choice.
~BAS
On Thu, 2008-03-27 at 07:44 -0700, Paul Hoffman wrote:
> How can I eliminate the "Limiting icmp unreach response" messages
> from getting to /var/log/messages or to the console? I have a spate
> of them that is causing log rollovers. I think I know the source of
> the problem, but need to get rid of the messages first.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Temperature Monitoring on PowerEdge 1950
On Thu, 2008-04-03 at 13:28 -0500, Andy Christianson wrote: > In response to "Andy Christianson" <[EMAIL PROTECTED]>: > > >We've been able to do this using IPMI. You can talk to the DRAC4/DRAC5 BMC out of band, independent of the OS. Otherwise: # kldload /boot/kernel/ipmi.ko God speed. ~BAS > Thanks for the fast response. I have installed the ipmitool port, but I > have no /dev/ipmi. Do I have to manually load the driver? > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Comments on DRAC IV, V, VI w/ FreeBSD 6.3, 7.0
On Wed, 2008-04-09 at 13:39 -0400, Philip M. Gollucci wrote: > Hi All, > > Does anybody have any comments, suggestion, feedback, compatability The DRAC5 is an abomination to professional computer operators everywhere. It runs Linux, and to use the remote VGA console or remote Virtual Media, you need ActiveX plugins (or a RHEL4-i386-only-XPI). The DRAC4 is very agreeable. Pure Java, which works out-of-the-box with Ports. Overall, the 9th-gen PowerEdges were sloppy (Revision 1 had serious instability issues related to PERC5) ~BAS > notes, etc with DRAC and FreeBSD? > > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipmi(4) on PowerEdge 860 - bogus CPU temperature readings
This platform is returning a bogus value for the main temperature sensor using the ipmi(4) module in 6.3/amd64: # ipmitool -V ipmitool version 1.8.8 # ipmitool sdr Temp | -54 degrees C | cr Planar Temp | 30 degrees C | ok That value should probably be an absolute value? IpmiTool: # ipmitool -v sdr': ipmitool -v sdr |more Sensor ID : Temp (0x1) Entity ID : 3.1 (Processor) Sensor Type (Analog) : Temperature Sensor Reading: -54 (+/- 1) degrees C Status: Lower Critical Nominal Reading : 50.000 Normal Minimum: 11.000 Normal Maximum: 119.000 Positive Hysteresis : -127.000 Negative Hysteresis : -127.000 Minimum sensor range : Unspecified Maximum sensor range : Unspecified Event Message Control : Per-threshold Readable Thresholds : Settable Thresholds : lcr lnc unc ucr Threshold Read Mask : lcr lnc unc ucr Event Status : Event Messages Disabled Assertion Events : Event Enable : Event Messages Disabled Assertions Enabled: Same results with FreeIPMI # ipmi-sensors 1: Temp (Temperature): -54.00 C (5.00/125.00): [At or Below (<=) Lower Critical Threshold] 2: Planar Temp (Temperature): 30.00 C (3.00/53.00): [OK] 3: CMOS Battery (Voltage): 3.06 V (2.64/NA): [OK] 4: VCORE (Voltage): [State Deasserted] 5: PROC VTT (Voltage): [State Deasserted] 6: 1.5V PG (Voltage): [State Deasserted] 7: 1.8V PG (Voltage): [State Deasserted] 8: Presence (Entity Presence): [Entity Present] 9: PROC Fan (Fan): 3150.00 RPM (750.00/NA): [OK] 10: DIMM Fan (Fan): 3000.00 RPM (750.00/NA): [OK] 11: PCI Fan (Fan): 1350.00 RPM (1425.00/NA): [OK] 12: Status (Processor): [Processor Presence detected] 13: VRM (Power Supply): [Presence detected] 14: OS Watchdog (Watchdog 2): [OK] 15: SEL (Event Logging Disabled): [Unknown] 16: Intrusion (Platform Chassis Intrusion): [OK] 17: Temp Interface (Temperature): [OK] 23: ECC Corr Err (Memory): [Unknown] 24: ECC Uncorr Err (Memory): [Unknown] 25: I/O Channel Chk (Critical Interrupt): [Unknown] 26: PCI Parity Err (Critical Interrupt): [Unknown] 27: PCI System Err (Critical Interrupt): [Unknown] 28: SBE Log Disable (Event Logging Disabled): [Unknown] 29: Logging Disable (Event Logging Disabled): [Unknown] 30: Unknown (System Event): [Unknown] 31: PROC Protocol (Processor): [Unknown] 32: PROC Bus PERR (Processor): [Unknown] 33: PROC Init Err (Processor): [Unknown] 34: PROC Machine Ch (Processor): [Unknown] 35: Memory Spared (Memory): [Unknown] 36: Memory Mirrored (Memory): [Unknown] 37: Memory RAID (Memory): [Unknown] 38: Memory Added (Memory): [Unknown] 39: Memory Removed (Memory): [Unknown] 40: PCIE Fatal Err (Critical Interrupt): [Unknown] 41: Chipset Err (Critical Interrupt): [Unknown] 42: Err Reg Pointer (OEM Reserved): [Unknown] dmesg(8): Copyright (c) 1992-2008 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 RELENG_6_3_amd64-CFI_INTERNAL-022408-1232EST #0: Sun Feb 24 19:43:21 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU3050 @ 2.13GHz (2133.42-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f2 Stepping = 2 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 real memory = 1073479680 (1023 MB) avail memory = 1020604416 (973 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:42:43) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 28.0 on pci0 pci2: on pcib2 pcib3: at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 2.0 on pci3 pci4: on pcib4 pci4: at device 2.0 (no driver attached) pci4: at device 4.0 (no driver attached) pci4: at device 4.1 (no driver attached) pci4: at device 4.2 (no driver attached) atapci0: port 0xe8f0-0xe8f7,0xe8e4-0xe8e7,0xe8d8-0xe8df,0xe8d0-0xe8d3,0xe870-0xe87f mem 0xdfdeec00-0xdfdeecff irq 32 at device 7.0 on pci4 ata2: on atapci0 ata3: on atapci0 pcib5: at device 28.4 on pci0 pci5: on pcib5 bge0: mem 0xdf9f-0xdf9f irq 16 a
Re: Max Ram
On Sun, 2008-04-20 at 18:49 -0400, Jose Perez wrote: > Hello Freebsd > > I would like to know if can i use 8 GB To use 8 gigs of ram, run the amd64 distribution. > of Ram in Freebsd 6.1 and if have raid drivers for the new dell 2950 The "r3" of the 2950 that Dell will sell you on Monday is the PERC6, which is the same as the PREC5, but you'll want to run 6.3 or newer for an up-to-date mfi(4). Don't waste your money on the DRAC5, its about as useful as an asshole on your elbow. ~BAS > > Regards > > Jose G. > _ > Get in touch in an instant. Get Windows Live Messenger now. > http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge1: watchdog timeout -- resetting bge1: link state changed to DOWN
On Tue, 2008-05-06 at 23:35 +0300, Indiana Jones wrote: > If anybody could provide a solid solution, I'd be most grateful. > > I have this box that works as an Internet router and I have two NICs > in it, 3com 3C996-SX and 3C996-T, the later is bge1 on which I get > this persistent ERROR below, the first one, bge0 is OK! Welcome to the world of Broadcom. Imagine our surprise when Dell started shipping embedded bge(4) and bce(4). ~BAS > The result of this error is blackouts and instability of the Internet > connections! > > May 2 14:09:48 GBRT2 kernel: bge1: watchdog timeout -- resetting > Ma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mfi freebsd7
nitor/investigate > >>>> your array. > >>>> > >>>> Vince > >>>> > >>>>> i'll keep looking but - has anybody successfully deployed > >>>>> production servers using the LSI MegaSAS 1078 in RAID1 on a very > >>>>> busy web server? > >>>>> is there any loss in performance using that hardware in RAID1? > >>>>> any performance loss in RAID1 at all? > >>>>> > >>>>> > >>>>> thanks... > >>>>> > >>>>> ___ > >>>>> freebsd-questions@freebsd.org mailing list > >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>>>> To unsubscribe, send any mail to > >>>>> "[EMAIL PROTECTED]" > >>>> > >>>> ___ > >>>> freebsd-questions@freebsd.org mailing list > >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>>> To unsubscribe, send any mail to > >>>> "[EMAIL PROTECTED]" > >>> ___ > >>> freebsd-questions@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>> To unsubscribe, send any mail to > >>> "[EMAIL PROTECTED]" > >> > >> ___ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to > >> "[EMAIL PROTECTED]" > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-06:07.pf
III. Impact By sending carefully crafted sequence of IP packet fragments, a remote attacker can cause a system running pf with a ruleset containing a 'scrub fragment crop' or 'scrub fragment drop-ovl' rule to crash. IV. Workaround Do not use 'scrub fragment crop' or 'scrub fragment drop-ovl' rules on systems running pf. In most cases, such rules can be replaced by 'scrub fragment reassemble' rules; see the pf.conf(5) manual page for All: Just to clarify on the syntax, since it's not actually mentioned in pf.conf(5): Per the PF FAQ, a rule: "scrub in all" or "scrub all" Implies "scrub in all fragment reassemble" as a default argument/flags to "scrub" when not are specified, and none of the other scrubbing options (no-df, random-id, etc.). This per observation of "pfctl -s all": $ sudo grep -i scrub /etc/pf.conf scrub in all $ sudo pfctl -s all | grep -i scrub scrub in all fragment reassemble Correct? To the credit of the FAQ Author, it does state "This is the default behavior when no fragment option is specified." ... but that still begs the question: "What are the default scrubbing options, other than fragment reassembly, when none are specified?" Might be useful to mention these things in the FAQ and the advisory. TIA, ~lava more details. Systems which do not use pf, or use pf but do not use the aforementioned rules, are not affected by this issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Syslog-NG at Boot (WAS: Re: cvs commit: ports/sysutils/syslog-ng Makefile distinfo pkg-plist)
might expect to talk to it. I assume you put syslogng_enable="YES" into /etc/rc.conf? as well as syslogd_enable="NO". (Or, it might work just to change syslogd_program="/path/to/syslogngd" and not bother with changing anything else). --Alex Just to clarify, even the latest src/etc/rc.d/syslogd at: http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/syslogd?rev=1.11&content-type=text/x-cvsweb-markup Specially hard-codes /usr/sbin/$program as the executable, thus setting: syslogd_program="/usr/local/sbin/syslog-ng" syslogd_flags="-p /var/run/syslog.pid" syslogd_enable="YES" Has no effect at startup. It starts the system syslogd(8). *HOWEVER*, after the boot process is complete, /etc/rc.d/syslogd begins to honor syslogd_program="" (start, stop, status). It's very strange. Perhaps a more rc(8) compliant syslog-ng.sh.example should be packaged up? ~lava On Thu, 7 Jul 2005, Roman Bogorodskiy wrote: novel 2005-07-07 18:57:24 UTC FreeBSD ports repository Modified files: sysutils/syslog-ng Makefile distinfo pkg-plist Log: - Update to 1.6.8 that fixes some bugs - Fix potential broke as authors move old versions to old/ directory - Make NOPORTDOCS work PR: 83102 Submitted by: Vsevolod Stakhov <[EMAIL PROTECTED]> Approved by:Vince Valenti (maintainer) Revision ChangesPath 1.27 +3 -2 ports/sysutils/syslog-ng/Makefile 1.19 +2 -2 ports/sysutils/syslog-ng/distinfo 1.3 +14 -14ports/sysutils/syslog-ng/pkg-plist ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" l8* -lava x.25 - minix - bitnet - plan9 - 110 bps - ASR 33 - base8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NAS advice?
On Tue, 14 Feb 2006, DAve wrote: (I am cross posting to FreeBSD questions and Bacula Users, I will not be cross posting replies) I've been crying for four years that we needed a decent backup system and I always got put off. "It's on order", "can you resubmit an updated equipment list". Yea, checks in the mail. So yesterday I am told that we have some equipment we got in another deal and I can have it to backup my NOC. I plan to run Bacula which I already have on some individual machines. I want to have Bacula clients on all my machines talking to a single machine running the Bacula director, hopefully using the NAS machines for storage. This is the equipment they threw at me, it is old, but amazingly, unused. One Dell Poweredge 750, 2.8ghz CPU, 1gb ram, 2 500gb SATA Maxtor drives(yuk!), CERC SATA controller. Be very careful here. I run OpenBSD with CMU RAIDFrame RAID-1 mirrors and FreeBSD 5.3 with GEOM/GMirror RAID-1 on this platform for embeded devices. It's rock-solid, except Dell phased the 750 for the 850 and went from ICH6 to ICH7 Intel Chipsets? Also, they're now OEM'ing Broadcom bge(4) based NICs instead of Intel em(4), so consider yourself lucky in a sense >:}. The point is that the 850 will only run the very latest FreeBSD 6.1-BETA1 snapshots contain support for the newer chips. ~lava ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ng_one2many v.s. AFT (NIC Fault Tolerance/Fail Over/Redundancy Revisited)
FYI, to bring this thread back to the list -- Forwarded message -- Date: Wed, 15 Feb 2006 20:53:59 -0500 (EST) From: Brian A. Seklecki <[EMAIL PROTECTED]> To: Jonathan Donaldson <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], Brian J. Creasy <[EMAIL PROTECTED]>, Chad Ziccardi <[EMAIL PROTECTED]>, Danny Howard <[EMAIL PROTECTED]>, Brad Bendy <[EMAIL PROTECTED]> Subject: Re: ng_one2many v.s. AFT (NIC Fault Tolerance/Fail Over/Redundancy Revisited) (fwd) On Wed, 15 Feb 2006, Jonathan Donaldson wrote: Take a look here: http://www.freebsd.org/cgi/getmsg.cgi?fetch=607312+0+/usr/local/www/db/text/2004/cvs-all/20041128.cvs-all Yea, I see it now. Sorry. I'm CC'ing the developer who commited the changes, and the the MFC. The man page needs to be updated, and it should mention your caveat. I got caught by your caveat with the one-link-down-at-boot. However, the code begins to work after bringing up the down link, as if it would if they were both active at boot, which is good. Where I got tripped up was that I thought that quote: "The node listens to flow control message from many hooks, and considers link failed if NGM_LINK_IS_DOWN is received.", Where "Flow Control Messages" I interrpted that as something on the wire like a STP/802.1q BPDU. Apparently, it's really an In-Kernel event related to the new ethernet link-state code in 6.x, or maybe just glorrified poll()'ing. Either way, it works well. Sorry for jumping the gun. ~lava P.S., in 7.0-CURRENT, there appears to be an import of the OpenBSD bridge(4) to relate the old-school "options BRIDGE" code. This one being 802.1q STP aware. When 7.x becomes release production, I suspect I'll end up using that instead since it works so well with NetBSD/OpenBSD for HA ethernet, plus I'd rather have a PVST+ Cisco switch make the packet forwarding the decisions >:} ~lava and then look here: http://fxr.watson.org/fxr/source/netgraph/ng_one2many.h?v=RELENG6 65 /* Algorithms for detecting link failure (XXX only one so far) */ 66 #define NG_ONE2MANY_FAIL_MANUAL 1 /* use enabledLinks[] array */ 67 #define NG_ONE2MANY_FAIL_NOTIFY 2 /* listen to flow control msgs */ so set your fail alg to 2 and see if you see the messages and failover... On Feb 15, 2006, at 8:11 PM, Brian A. Seklecki wrote: On Thu, 12 Jan 2006, Brian J. Creasy wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian A. Seklecki wrote: | | Johnathan's comments suggest that we may need to move to 6.x on the | production cluster. | | 6.x has been upgraded from a technology release to stable, and our goal | is stability. | | Brian: What are you thoughts so far on the 6.x experience? no complaints here.. though, i have it running only on my laptop and Okay. | As of Freebsd 6_0 (which is at RC1 now), the NG_ONE2MANY does | support the failure of a link which does not end up with 50% packet | loss. There is new code in the One2Many module that xmits a layer 2 "I'm | alive" broadcast out all links, as long as this is picked up on the | other links, then all interfaces are considered alive. If one of the | packets is not received, then after 2 x heartbeat duration that link is | considered "down". I have tested this in the 6.0 code and it works with | one caveat. When the server is brought up, both interfaces must be | connected and live, or for some reason, the failure algorithm never | seems to kick in. I saw exactly what you saw in 5.4 and newer with | regards to the 50% packet loss. Jonathan: I'm not sure where you got the info about this. Accoring to the NG_ONE2MANY(4) page in CVS -rHEAD (-CURRENT): "Currently, the valid settings for the xmitAlg field are NG_ONE2MANY_XMIT_ROUNDROBIN (default) or NG_ONE2MANY_XMIT_ALL. The only valid setting for failAlg is NG_ONE2MANY_FAIL_MANUAL; this is also the default setting." I have 6.1-BETA1 on a box right now and I've got my config setup for NG_ONE2MANY_XMIT_ROUNDROBIN + NG_ONE2MANY_FAIL_NOTIFY and I don't see any layer2 heartbeat related traffic (watching via tcpdump(8) on another machine in the same segment) Can you share what you saw? ~lava |> mission critical environment). |> - Xmit-All causes twice as much load on to be placed on the switch |> /fabric and switch CPU. |> | | As of Freebsd 6_0 (which is at RC1 now), the NG_ONE2MANY does | support the failure of a link which does not end up with 50% packet | loss. There is new code in the One2Many module that xmits a layer 2 "I'm | alive" broadcast out all links, as long as this is picked up on the | other links, then all interfaces are considered alive. If one of the | packets is not received, then after 2 x heartbeat duration that link is | considered "down&q
Re: ng_one2many v.s. AFT (NIC Fault Tolerance/Fail Over/Redundancy Revisited) (fwd)
-- Forwarded message -- Date: Wed, 15 Feb 2006 20:11:49 -0500 (EST) From: Brian A. Seklecki <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], Jonathan Donaldson <[EMAIL PROTECTED]>, Brian J. Creasy <[EMAIL PROTECTED]> Cc: Chad Ziccardi <[EMAIL PROTECTED]>, Danny Howard <[EMAIL PROTECTED]>, Brad Bendy <[EMAIL PROTECTED]> Subject: Re: ng_one2many v.s. AFT (NIC Fault Tolerance/Fail Over/Redundancy Revisited) (fwd) On Thu, 12 Jan 2006, Brian J. Creasy wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian A. Seklecki wrote: | | Johnathan's comments suggest that we may need to move to 6.x on the | production cluster. | | 6.x has been upgraded from a technology release to stable, and our goal | is stability. | | Brian: What are you thoughts so far on the 6.x experience? no complaints here.. though, i have it running only on my laptop and Okay. | As of Freebsd 6_0 (which is at RC1 now), the NG_ONE2MANY does | support the failure of a link which does not end up with 50% packet | loss. There is new code in the One2Many module that xmits a layer 2 "I'm | alive" broadcast out all links, as long as this is picked up on the | other links, then all interfaces are considered alive. If one of the | packets is not received, then after 2 x heartbeat duration that link is | considered "down". I have tested this in the 6.0 code and it works with | one caveat. When the server is brought up, both interfaces must be | connected and live, or for some reason, the failure algorithm never | seems to kick in. I saw exactly what you saw in 5.4 and newer with | regards to the 50% packet loss. Jonathan: I'm not sure where you got the info about this. Accoring to the NG_ONE2MANY(4) page in CVS -rHEAD (-CURRENT): "Currently, the valid settings for the xmitAlg field are NG_ONE2MANY_XMIT_ROUNDROBIN (default) or NG_ONE2MANY_XMIT_ALL. The only valid setting for failAlg is NG_ONE2MANY_FAIL_MANUAL; this is also the default setting." I have 6.1-BETA1 on a box right now and I've got my config setup for NG_ONE2MANY_XMIT_ROUNDROBIN + NG_ONE2MANY_FAIL_NOTIFY and I don't see any layer2 heartbeat related traffic (watching via tcpdump(8) on another machine in the same segment) Can you share what you saw? ~lava |> mission critical environment). |> - Xmit-All causes twice as much load on to be placed on the switch |> /fabric and switch CPU. |> | | As of Freebsd 6_0 (which is at RC1 now), the NG_ONE2MANY does | support the failure of a link which does not end up with 50% packet | loss. There is new code in the One2Many module that xmits a layer 2 "I'm | alive" broadcast out all links, as long as this is picked up on the | other links, then all interfaces are considered alive. If one of the | packets is not received, then after 2 x heartbeat duration that link is | considered "down". I have tested this in the 6.0 code and it works with | one caveat. When the server is brought up, both interfaces must be | connected and live, or for some reason, the failure algorithm never | seems to kick in. I saw exactly what you saw in 5.4 and newer with | regards to the 50% packet loss. | | |> What ng_one2many needs is a "Active-Standy" XMIT algorithm (STP BOFH's |> will think BLOCKING/FORWARDING). It could even be used on top of |> other NetGraph nodes like ng_fec or possibly (hopefully) ng_802.3ad >:} |> | - -- Brian J. Creasy Collaborative Fusion, Inc. 412.422.3463 x4020 [EMAIL PROTECTED] pgp public key: ~ http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5F94E004 IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDxmXvDgwDm1+U4AQRAr3GAJ42+HcJFO595aZvljztWCkd+NWgvACeMQiu ILXLchBGR90TZTZHjn6DVCY= =68DY -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dell Powervault 120T / ADIC FastStor DLT D116
I just connected a Dell Powervault 120T to an Adaptec AHA-2944 HVD ("High
Voltage Differential") controller and the resulting dmesg indicates what
is probed by my RELENG_5_3 kernel:
ahc0: port 0xe400-0xe4ff mem
0xe9001000-0xe9001fff irq 5 at device 11.0 on pci0
sa1 at ahc1 bus 0 target 4 lun 0
sa1: Removable Sequential Access SCSI-3
device
sa1: 40.000MB/s transfers (40.000MHz, offset 32)
pass0 at ahc0 bus 0 target 0 lun 0
pass0: Removable Changer SCSI-2 device
pass0: 3.300MB/s transfers
For some reason, the tape changer is probing as pass(4) instead of ch(4).
Any ideas why? SCSI devices have a "device class" designation, IIRC.
However, I can't get useful debugging out of camcontrol(8) w/ recompiling
the kernel w/ DEBUG options.
I'm going to do that now, but any ideas would be appreciated.
l8*
-lava
x.25 - minix - bitnet - plan9 - 110 bps - ASR 33 - base8
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell Powervault 120T / ADIC FastStor DLT D116
On Mon, 25 Jul 2005, Brian A. Seklecki wrote: For some reason, the tape changer is probing as pass(4) instead of ch(4). Any ideas why? SCSI devices have a "device class" designation, IIRC. Nevermind, someone had removed "device ch" from the kernel config (as well as uk(4), which explains pass(4) attachment) ch1 at ahc0 bus 0 target 0 lun 0 ch1: Removable Changer SCSI-2 device ch1: 3.300MB/s transfers ch1: 7 slots, 1 drive, 1 picker, 0 portals sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) # amtapetype -f /dev/sa0 Writing 256 Mbyte compresseable data: 25 sec Writing 256 Mbyte uncompresseable data: 207 sec WARNING: Tape drive has hardware compression enabled Estimated time to write 2 * 1024 Mbyte: 1656 sec = 0 h 27 min wrote 454530 32Kb blocks in 1390 files in 13494 seconds (short write) [interrupt] ...more complete output amtapetype(1) to amanda-users@amanda.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Restarting network & vlan interface = kernel memory corruption (if_vlan / conf/63700 redux)
[Originally from freebsd-hackers@ / Feb 2008; freebsd-net Jun 2010] All: pf conf/63700 got the ball rolling on fixing cloned/VLAN interface management with rc.d/netif, but a very specific problem still remains. For example, adding an alias to a VLAN and running: /etc/rc.d/netif restart && /etc/rc.d/routing restart is a failure. --- Take the following rc.conf(4) config: hostname="sexdrugsandunix" cloned_interfaces="vlan14" ifconfig_em0="up media 100baseTX mediaopt full-duplex -tso" ifconfig_vlan14="inet 1.2.3.4 netmask 255.255.255.128 vlan 14 vlandev em0 up" ifconfig_vlan14_alias0="inet 1.2.3.5 netmask 255.255.255.255" Change it to include a second alias without a reboot, instead run 'rc.d/netif restart', as works on a physical interface: hostname="sexdrugsandunix" cloned_interfaces="vlan14" ifconfig_em0="up media 100baseTX mediaopt full-duplex -tso" ifconfig_vlan14="inet 1.2.3.4 netmask 255.255.255.128 vlan 14 vlandev em0 up" ifconfig_vlan14_alias0="inet 1.2.3.5 netmask 255.255.255.255" ifconfig_vlan14_alias1="inet 1.2.3.6 netmask 255.255.255.255" The result will be: % ifconfig vlan14 [bsekle...@sureshot ~]$ ifconfig vlan14 vlan14: flags=8843 metric 0 mtu inet 1.2.3.6 netmask 0x broadcast 192.168.158.152 inet 1.2.3.5 netmask 0x broadcast 192.168.158.255 1) I'm not sure where the .152 broadcast comes from. ?! 2) The new _alias1= data is now in the primary IP slot 3) The primary IP is lost, there is no routable IP 4) The original _alias0= data is now in the 1st alias slot 5) rc.d/routing fails because the interface lacks a routable IP with a valid netmask/broadcast combination. --- Problem #1: rc.d/netif::network_stop() The core problem is that rc.d/netif::network_stop() never calls network.subr::clone_down() in the same way that rc.d/netif::network_start() calls network.subr::cloned_up() I'd speculate that this is a design decision not to destroy network interfaces that certain userland daemons (DHCP, RTADVD, BPF) may be strictly bound to; I disagree. Even if you explicitly pass your VLAN interface to rc.d/netif, a stop doesn't call 'ifconfig [VL] destory', and, when 'rc.d/netif start' is called later, SIOCSETVLAN results. jail-host-80:/home/bseklecki% sudo ifconfig vlan666 destroy jail-host-80:/home/bseklecki% sudo ifconfig vlan666 create inet 1.2.3.4 netmask 255.255.255.0 vlan 666 vlandev em0 jail-host-80:/home/bseklecki% sudo ifconfig vlan666 create inet 1.2.3.4 netmask 255.255.255.0 vlan 666 vlandev em0 ifconfig: create: bad value A simple rc.d/network_stop() patch could fix this problem if we can avoid bikeshedding. -- Problem #2: VLAN interface kernel data structures maintain configuration data after being destroyed and re-created %ifconfig vlan666 vlan666: flags=8843 metric 0 mtu 1500 options=3 ether 00:0c:29:a1:4b:9d inet 192.168.15.54 netmask 0xff00 broadcast 192.168.15.255 media: Ethernet 1000baseT status: active vlan: 666 parent interface: em0 %sudo ifconfig vlan666 destroy %sudo ifconfig vlan666 create %ifconfig vlan666 vlan666: flags=8843 metric 0 mtu 1500 options=3 ether 00:0c:29:a1:4b:9d !!**>> inet 192.168.15.54 netmask 0xff00 broadcast 192.168.15.255 <<**!! media: Ethernet 1000baseT status: active vlan: 666 parent interface: em0 Now, that's something you don't see very day!! NOTE: I can't get that persistent IP data problem to happen consistently, but its highly reproducible. I also have no idea on the fixes, I'll check this weekend, but I have a work-around. To avoid destroying your routing table after adding an alias to a VLAN interface in rc.conf(5), simply run: $ sudo /etc/rc.d/netif [VLAN] start DO NOT RESTART, and you should be okay. ~BAS References: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-February/023440.html http://www.freebsd.org/cgi/query-pr.cgi?pr=63700&cat= (Circa 2004) http://lists.freebsd.org/pipermail/freebsd-net/2007-September/015447.html http://lists.freebsd.org/pipermail/freebsd-net/2010-June/025514.html -- Brian A. Seklecki Collaborative Fusion, Inc. signature.asc Description: This is a digitally signed message part
pxeboot(8) NFS code breaks PIX/ASA policy
I'm PXE booting systems using the "dhcprelay" feature on a PIX 525 running 7.1(2). The TFTP process of retrieval of /tftoboot/pxeboot works fine, however once loaded NFS mount requests to the server fail per the following messages. In my config, all layer 4->7 packet "inspection" features are turned off. Any ideas why pxeboot would set the destination UDP port number to 0? It should be UDP/111 and UDP/2049, but alas TCPdump on the server shows nothing coming through. My work-around right now is to recompile pxeboot w/o NFS support and use TFTP file retrieval...which...sort of works. TIA, ~BAS -- Sep 05 2006 17:38:15: %PIX-4-54: Invalid transport field for protocol=UDP, from 192.168.129.130/1023 to 192.168.128.40/0 Sep 05 2006 17:38:19: %PIX-4-54: Invalid transport field for protocol=UDP, from 192.168.129.130/1023 to 192.168.128.40/0 According to Cisco: %PIX-4-54: Invalid transport field for protocol=protocol, from src_addr/src_port to dest_addr/dest_port Explanation This message appears when there is an invalid transport number, in which the source or destination port number for a protocol is zero. The protocol field is 6 for TCP and 17 for UDP. --- l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PERC 5/E SAS RAID in Dell PowerEdge 1950/2950
On Sun, 11 Jun 2006, Brian A. Seklecki wrote: All: Does anyone have details about the new PERC 5/E SAS RAID controller Dell is (or will soon be) shipping in the 1950/2950? For the record, this is mfi(4). Yay! ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PERC 5/E SAS RAID in Dell PowerEdge 1950/2950
On Thu, 2006-09-07 at 20:07, ke han wrote: > On Sep 8, 2006, at 12:49 AM, Brian A. Seklecki wrote: > > > > > > > On Sun, 11 Jun 2006, Brian A. Seklecki wrote: > > > >> All: > >> > >> Does anyone have details about the new PERC 5/E SAS RAID > >> controller Dell > >> is (or will soon be) shipping in the 1950/2950? > >> > > > > For the record, this is mfi(4). > > Have you done an install of FreeBSD 6.1 on a 1950/2950? Does the > install kernel automatically recognize RAID arrays you have setup It finds the RAID controller fine. However, we're very concerned about the lack of a management CLI like ports/sysutils/megarc. It's the DRAC5 virtual USB keyboard that requires you sacrifice your moral integrity to obtain. A small price to pay, considering the client requires ActiveX and Java. Also I had some problems with if_bce.c < rev1.7. Media state confusion. ~BAS > with the PERC 5 bios? IOW, do I have to manually load some updated > module outside of the default 6.1 install and config? > > thanks, ke han > > > > > Yay! > > > > ~BAS > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions- > > [EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: two NIC and nfs
On Mon, 23 Oct 2006, Jeff Mohler wrote: Well..the right way to do this is with a switch that can etherchannel the NICs together, im not sure if Fbsd can do that..of course. FreeBSD supports EthernetChannel, 802.1ad, etc. So does NetBSD. I's LACP that needs work. ~BAS___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reading /dev/klog / log(9)
/dev/klog seems to be special in that, even in O_NONBLOCk, it:
*) Never blocks, but does(?)
*) Always returns read(2) = 0
*) Never returns EOF
I'm trying to read out the contents silently via a shell script prior to
starting syslog-ng. I.e., "drain it".
One would think any I/O manipulation utility (dd/pax/cpio/cat, etc.) would
work. The problem is that dd(1) w/ count=1 && bs=1 will always hang after
reading the last byte is read.
If I had some way of couting the bytes that could be read using stat(1) or
fstat(1), I could pass the correct count=$val
I've been staring at syslogd.c on FreeBSD for a while, but I'm still at a
lost as to the logic of how it even gets into klog_read(); I don't see
any select(2) or stat(2) logic.
Anyway, this perl script sort of explains where I'm trying to go:
$BUFSIZ=1;
sysopen(KLOG, "/dev/klog", O_RDONLY|O_NONBLOCK);
$oldbuffer="init";
while (1) {
undef($rv);
$rv = sysread(KLOG, $buffer, $BUFSIZ);
if (!defined($rv) && $! == EAGAIN) {
# would block
print "$rv\n";
print "Would block";
exit;
} else {
#successfully read $rv bytes from HANDLE
print "No Block";
print "$rv\n";
print "Buffer: \"" . $buffer . "\"\n";
chomp($buffer);
print "Buffer Chomped: \"" . $buffer . "\"\n";
print "Old Buffer: \"" . $oldbuffer . "\"\n";
print "Old Buffer Unchomped: \"" . $oldbufferunchomped . "\"\n";
#if ( ($buffer eq "") && ($oldbuffer eq "")) {
if ($buffer eq "") {
print "match, exit!\n";
}
$oldbuffer = $buffer
}
}
sysclose (KLOG);
~BAS
l8*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tcpwrappers & SSH
On Wed, 25 Oct 2006, Alex Zbyslaw wrote: òÉÈÁÄ çÁÄÖÉÅ× wrote: A comment in /etc/hosts.allow states that: Wrapping sshd(8) is not normally a good idea With tcpwrappers, you still have to open a socket and burn cycles/ram/resources on the 3-way, followed by a quick RST. With pf(4), you can maintain a hash list on a L4 block rule and it's much more efficient. No RST needed. ~BAS___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Dell PERC 5/i mfi status?
On Tue, 31 Oct 2006, Bret Esquivel wrote: Mathieu, I was actually asking if there is an "amrstat" type utility that I can check the array status while in production. Thanks for the advice on 6-STABLE, I Well, it was sysutils/megarc for PERC/4. On PERC/5 mfi(1), it's whatever we decide to call it. Dell is shipping a CLI with OMSA or whatever. We may have to hack on the kernel interface: http://lists.us.dell.com/pipermail/linux-poweredge/2006-October/027645.html We've got the /dev/mfi? management interface already, just need to port the Linux code over. I'm really starting to think OpenBSD will beat FreeBSD to the game with the bio(4) RAID management hardware abstraction subsystem: http://www.openbsd.org/cgi-bin/man.cgi?query=bio&sektion=4&arch=i386&apropos=0&manpath=OpenBSD+Current ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: PERC 5/E SAS RAID in Dell PowerEdge 1950/2950
On Tue, 31 Oct 2006, Krempasky, Mark wrote: I have installed FreeBSD 6.2 and have no issues with using multiple RAID groups with the Dell 2950 internal disks. Thanks, ~BAS -Original Message- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell 2950 Perc 5/i RAID Controller and FreeBSD 6.1 Question
It would be very very useful if you provided dmesg(8), bsdlabel(8), and
fdisk(8) outputs to illustrate the problem.
For each RAID group you assemble in the BIOS/CMOS utility, you should see
a seaparate mfid[0-9] phyiscal device. Once properly partitioned, they
should each contain "s1" slice -- for some reason we number disks from 0
but slices from 1 (possibily because the BIOS does)
Then each physical slice can be BSD labeled'd with [a-z]
~BAS
On Thu, 26 Oct 2006, Krempasky, Mark wrote:
Hi,
We have a new Dell 2950 with 6 disks, we have verified that the bios and
raid controller firmware are up to date.
Our issue is: after creating 3, RAID 1 virtual disk groups and
initializing them we successfully install FreeBSD 6.1 on the first raid
group.
We then create a file system on the second raid group which seems to
wipe out the FreeBSD install on the first disk group.
It seems as though FreeBSD6.1 is not differentiating between the
different disk groups thus when you make changes to 1 group it will
write the changes to the other.
Anyone have any ideas on how to get FreeBSD6.1 to differentiate between
the different virtual disk groups on a Dell 2950?
Thanks
Mark.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PERC 5/E SAS RAID in Dell PowerEdge 1950/2950
It finds the RAID controller fine. However, we're very concerned about the lack of a management CLI like ports/sysutils/megarc. Now that 6.2 release is imminent and bce(4) has been patched to the point where it is relatively stable, we're nearing the point where we can finally put Dell PowerEdge 1950s/2950s into production. However the lack of a MFI CLI management utility is still a grave concern. Without it, there is no way to proactively monitor the RAID controller for failed components (aside from sitting there 24/7/365 and waiting for a blue light to go amber) ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell 2950 Perc 5/i RAID Controller and FreeBSD 6.1 Question
See the question archive: Date: Thu, 26 Oct 2006 20:42:49 +0200 From: Erik Trulsson <[EMAIL PROTECTED]> To: "Marthias, Santosso" <[EMAIL PROTECTED]> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.1 and RAID controller PERC 5/i in DELL PowerEdge 2950 [...snip...] Similar problem report to yours Anybody know about this issue? Any suggestion? There have been several bug fixes and improvements made to the mfi(4) driver since 6.1 was released, including one that is supposed to fix problems with multiple volumes. I would suggest trying the latest 6.2-BETA and see if that works better. (It probably will.) -- Erik Trulsson [EMAIL PROTECTED] ~BAS On Thu, 26 Oct 2006, Krempasky, Mark wrote: Hi, We have a new Dell 2950 with 6 disks, we have verified that the bios and raid controller firmware are up to date. Our issue is: after creating 3, RAID 1 virtual disk groups and initializing them we successfully install FreeBSD 6.1 on the first raid group. We then create a file system on the second raid group which seems to wipe out the FreeBSD install on the first disk group. It seems as though FreeBSD6.1 is not differentiating between the different disk groups thus when you make changes to 1 group it will write the changes to the other. Anyone have any ideas on how to get FreeBSD6.1 to differentiate between the different virtual disk groups on a Dell 2950? Thanks Mark. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PERC 5/E SAS RAID in Dell PowerEdge 1950/2950
The DRAC cards do that, don't they?
I dunno the SSH interface on the DRAC5's wont let us in. The SSH
interface on the DRAC4 was useless, but it was the last version upon which
Firefox could load the remote console interface via Java.
Now they only support Firefox 1.0.5 plugins on RH7.1 >:}
~BAS
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hardware Console Redirection
God I miss the days of the good old PC Weasel. Those guys would have made a killing selling the technology to Intel/Dell/Phoenix. Instead this is what we're stuck with On two platforms I work with: 1) Dell Poweredge [1,2][8,9]50 2) Axiomtek VIA Embedded SBC83672 I have noticed that the "Phoenix BIOS" console redirection feature on both discontinues to operate once the kernel has booted (however, the 1st/2nd stage boot loaders work fine). I'm trying to avoid having to use a combination of both hardware and software console redirection. The advantage of native, hardware level BIOS -> VGA emulated console redirection is that, much like Sun/MacPPC or any OPF/PROM aware platform (Soekris), the OS/Bootblocks need not be aware of the serial console semantics; -- only of a benign VGA console. The only limitation being interpretation of certain escape characters. The question becomes: Is there some routine in the *BSD kernel console code that performs an operation, perhaps a reset, on the serial ports, that wouldn't happen in DOS? In the case of the Axiom device, the console is redirected to the BIOS level "com0" 0x3f8. In the case of the PowerEdge, the redirection is to a "virtual com1" which is attached to the DRAC5 LOM card. I tried the FreeBSD loader(8) hint.sio.1.flags="0x40" to attempt to have the kernel ignore the device without success. There was some discussion of this on misc@openbsd.org: http://archives.neohapsis.com/archives/openbsd/2006-08/1903.html That essentially the os needs to "block" the virtual serial port. Seems like a conflict of interest. Now taking ideas on how to work around this. l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Dell PERC 5/i mfi status?
On Tue, 31 Oct 2006, Bret Esquivel wrote: Mathieu, I was actually asking if there is an "amrstat" type utility that I can check the array status while in production. Thanks for the advice on 6-STABLE, I Well, it was sysutils/megarc for PERC/4. On PERC/5 mfi(1), it's whatever we decide to call it. Dell is shipping a CLI with OMSA or whatever. We may have to hack on the kernel interface: http://lists.us.dell.com/pipermail/linux-poweredge/2006-October/027645.html We've got the /dev/mfi? management interface already, just need to port the Linux code over. I'm really starting to think OpenBSD will beat FreeBSD to the game with the bio(4) RAID management hardware abstraction subsystem: http://www.openbsd.org/cgi-bin/man.cgi?query=bio&sektion=4&arch=i386&apropos=0&manpath=OpenBSD+Current ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hardware Console Redirection
> Why is that a problem? The BIOS doesn't use the console once > the kernel has booted. Because it becomes a burden always having to customize your install/upgrade media/kernels/bootblocks to use redirection. Dell knew that; that's why they made the DRAC4 with a virtual VNC-based console redirection. Then the bungled it with the DRAC5 when they re-wrote it to depend on ActiveX. Also because the hardware vendors could follow the PC Weasel model and not utilize a serial port visible to the OS. With NetBSD its just one or two flags to installboot(8) to change the options, with the only exception being that we seem to lack the ability to set the com console _speed_ when in *interactive* mode at boot(8) ; of course it can be set from the installboot(8) flags. With FreeBSD, you have to jump through a ring of fire to get it to work right. You've got three stages of bootblocks to recompile/configure. boot.config. device.hints. etc. etc. Then the kernel has to be told in-src, recompiled. Then the getty. In either case, forget about sysinst/sysinstall to install off of stock install media. All very possible with the Weasel. You alway have to consider the the 3:30 AM incident where you're fumbling though a stack of CD-Rs for a Fixit or Live CD and you have to wonder if you re-mastered the disc with a boot image containing your custom serial enabled kernel with the right baud and com port (as you can see below). > What serial console semantics do the bootblocks get wrong? None. I'm just suggesting that for simplicity it would be nice not to have to make them aware. > What sort of reset do you need? I don't really understand the > question, I'm afraid. Reset my attitude I guess >:} I'm pining for the days of sparc systems and a unified serial console server. When TLS says: "Of course; it is a BIOS feature, and NetBSD does not use the BIOS for console I/O.", I tend to think of Sun how writing to the OBP firmware console is not dissimilar from the NetBSD kernel output. It would be nice to think x86 has caught up over the last 15 years. Anyway, for the record: The old PC Weasel Console Redirection: Phoenix BIOS: http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=23 NetBSD 2.0 Sysinst: http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=24 Bios Summary: http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=22 --- Dell PE750 Console Redirection: http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=21 Compare where DRAC VNC (IE6 only) VGA redirected console output continues and the DRAC5 virtual "COM2" serial redirection halts: http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=27 http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=25 vs.: http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=29 Dell PE2950 Settings (BIOS nicely drawn via Serial/ANSI): http://digitalfreaks.org/~lavalamp/cp/displayimage.php?album=16&pos=28 ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hardware Console Redirection
redirection) and use "consdev com0". (Unless you used the bios console direction at > 9600 bps) Right, and the Dell PE uses "com 2", or "com1" (when properly counting from 0), ah la 0x2F8 which is logically connected to a serial port on the DRAC5 via the daughterboard connection. And that's where Dell, Intel, and Phoenix went totally wrong. Another big problem with mixing hard and soft serial console redirection (at least with FreeBSD) is that kernel panic/trap message output doesn't always make it to the serial console (such as UVM faults), where with VGA console you almost always get the message. This killed us several times with FBSD 5.3 and some NFS bugs. Plus when you're doing serial console redirection, your console server has to be configured to be connected 100% of the time and log output to a file. If you get a panic and need to connect on-demand, you'll have missed that message to the buffer otherwise. With the Real Weasel, you could connect on demand and force a screen refresh/redraw and it would grab the current VGA framebuffer and re-write to the TTY. --- The only macro keys you get with Dell are: Press the spacebar to pause... KEY MAPPING FOR CONSOLE REDIRECTION: Use the <0> key sequence for Use the key sequence for Use the <@> key sequence for Use the key sequence for Use the key sequence for Use the key sequence for Use the key sequence for Use the key sequence for , where x is any letter key, and X is the upper case of that key Use the key sequence for ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Console Redirection After Boot
On Wed, 2006-11-01 at 09:08 -0600, Matt Domsch wrote: > On Wed, Nov 01, 2006 at 10:37:01AM -0400, eclark wrote: > > there any way to force serial console redirection in the kernel, so I can > > log > > boot sequences? It gets a bit old having to continuously reboot to stare at > > scrolling messages when you are trying to do kernel testing. > Just for the record, I just tested: - An Intel Server Motherboard SE7520* - A Dell PE2950 - An Axiomtek SBC83672 All have Phoenix BIOS. All exhibit the same behavior. I/O to the console does not get redirected to serial _unless_ it was sent there via a BIOS call. Ah la, DOS. The only options are: - Write a framebuffer driver for the kernel that uses BIOS calls (_not likely_, and for which there would most presumably be no terminal disciplines capable of running sysint/sysinstall) - Convince hardware vendors like Dell/Intel to implement a more Real Weasel-like console redirection system (not likely) - Convince Dell not to re-write the ActiveX applet that is the DRAC5 interface in something slight more portable, such as...oh, Java. - During emergency scenarios like DRP deployment, have a Windows system around. - Buy an OpenBoot enabled platform. =p J/K #3 seems most logical. Well at least now I understand the problem in its entirely. Thanks all. ~BAS > That's easy. > > 1) Disable (or really, don't enable) console redirection in BIOS SETUP. > 2) Put on the kernel command line: console=ttyS0,115200 console=tty0 > > We do 99% of our kernel debugging this way. > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Raid monitoring - 6.2 RELEASEE - Dell SC440
On Fri, 20 Jul 2007, Lars Olsson wrote: I'm running FreeBSD 6.2 RELEASE on a Dell PowerEdge SC440 with a SAS 5/iR Hmmm, must be a software-assist RAID. Does it probe a mega-volume / logical disk or individual components? ~BAS Raid controller. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SV: Raid monitoring - 6.2 RELEASEE - Dell SC440
There might not even be one for Linux yet: http://marc.info/?l=linux-poweredge&m=116657592817014&w=2 http://fedoraproject.org/wiki/DmraidStatus It seems to be standards-based somehow, though: http://people.redhat.com/~heinzm/sw/dmraid/readme I know NetBSD ld(4) can extract that information at scan time, but I don't know about re-poll()'ing after boot: mlx0 at pci0 dev 2 function 0: Mylex RAID (v2 interface) mlx0: interrupting at dec 6600 irq 12 mlx0: DAC960P/PD, 3 channels, firmware 2.70-0-00, 8MB RAM ld0 at mlx0 unit 0: RAID0, online ld0: 4092 MB, 2078 cyl, 64 head, 63 sec, 512 bytes/sect x 8380416 sectors ld1 at mlx0 unit 1: RAID0, online ( ld(4) attached to amr(4) for the MegaRAID 'lite' soft-raid HBAs) ~~BAS On Fri, 20 Jul 2007, Lars Olsson wrote: The drives is detected as one logical drive. /dev/da0. -Ursprungligt meddelande- Från: Brian A. Seklecki [mailto:[EMAIL PROTECTED] Skickat: den 20 juli 2007 17:33 Till: Lars Olsson Kopia: freebsd-questions@freebsd.org Ämne: Re: Raid monitoring - 6.2 RELEASEE - Dell SC440 On Fri, 20 Jul 2007, Lars Olsson wrote: I'm running FreeBSD 6.2 RELEASE on a Dell PowerEdge SC440 with a SAS 5/iR Hmmm, must be a software-assist RAID. Does it probe a mega-volume / logical disk or individual components? ~BAS Raid controller. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail?" ~Maynard James Keenan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How does gmirror know of a faulty drive
No answers?
I just actually replied to a thread about this. Apparently there is no
automatic demotion of a device to DEGRADED. I just had a provider error
for a good 5 minutes of SCSI kernel messages (bad sectors, grown defects),
without any automatic corrective action taken by gmirror(4)
My original message was held of moderation.
~BAS
On Wed, 27 Jul 2005, Ivan Carey wrote:
In FreeBSD 5.3 I have set up 2 drives in RAID-1 format.
How will I know if one of the drives is faulty such as either not working or
has some lost sectors?
Is it possible to have gmirror email me if there is a problem?
Thanks,
Ivan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror: degraded, Component ad4 (device gm0) broken, skipping.
gmirror insert gm0 ad4 The big question is: In your example, ad4 has already been "prepped" for use in as a component in the gmirror by ? Or will it just overwrite anything on ad4 regardless? ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
geom(4)/gmirror(4) automatic device DEGRADED status demotion (WAS:Re: gmirror HD failure detection)
On Wed, 14 Feb 2007, Brian A. Seklecki wrote: All: For a while our strategy was to use NRPE2+ a custom nagios check (check_raid_fbsdgmirror -- ugly-as-hell Perl, but which I can make available to the public). However, this morning a drive in a Dell PE1850 (one without a PERC4 controller) started erroring. It has just regular old (bad) mpt(4) controller. The problem is that gmirror(4) never marked the drive as failed. I'd have to tear through the code to find where the logic is for automatic demotion of a failed mirror. Either way, the original thinking behind the Nagios pluging check, was that gmirror(4) would have some threshold of failed attempts to write/read from a provider disk should lead to flagging a provider as "DEGRADED" Its entirely possible that we never had a chance to test it. Now I have to go back and re-visit all of that. ~BAS On Wed, 20 Sep 2006, Alex Zbyslaw wrote: Robin Becker wrote: After using Dru Lavigne's excellent article http://tinyurl.com/da66a about Raid-1 I have a full Raid-1 mirror on a new rack server. I'm wondering if anyone can tell me how best to monitor the hardware status to detect imminent failure of one of the disks? Do I use something like smartctl in a cron or what? Assuming that the disks support SMART then just read the man page for smartd. No need for cron. You can also schedule "short" and "long" tests to run in off hours. smartmontools is easy to uninstall if it doesn't work for you. However, this will tell you that a disk is failing (or failed) which is not quite the same as array status. An array (theoretically) might be sub-optimal for non-SMART reasons. Someone familiar with gmirror will have to answer that bit... but gmirror status -s looks from the man page like it might be interesting and *that* could be run from cron and parsed to weed out "status OK results". ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
geom(4)/gmirror(4) automatic device DEGRADED status promotion (WAS:Re: gmirror HD failure detection)
All: For a while our strategy was to use NRPE2+a custom nagios check (check_raid_fbsdgmirror -- ugly as hell Perl but which I can make available to the public). However, this morning a drive in a Dell PE1850 (one without a PERC4 controller) started erroring. It has just regular old (bad) mpt(4) controller. The problem is that gmirror(4) never marked the drive as failed. I'd have to tear through the code to find where the logic is for automatic demotion of a failed mirror. Either way, the original thinking behind the Nagios pluging check, was that gmirror(4) would have some threshold of failed attempts to write/read from a provider disk should lead to flagging a provider as "DEGRADED" Its entirely possible that we never had a chance to test it. Now I have to go back and re-visit all of that. ~BAS On Wed, 20 Sep 2006, Alex Zbyslaw wrote: Robin Becker wrote: After using Dru Lavigne's excellent article http://tinyurl.com/da66a about Raid-1 I have a full Raid-1 mirror on a new rack server. I'm wondering if anyone can tell me how best to monitor the hardware status to detect imminent failure of one of the disks? Do I use something like smartctl in a cron or what? Assuming that the disks support SMART then just read the man page for smartd. No need for cron. You can also schedule "short" and "long" tests to run in off hours. smartmontools is easy to uninstall if it doesn't work for you. However, this will tell you that a disk is failing (or failed) which is not quite the same as array status. An array (theoretically) might be sub-optimal for non-SMART reasons. Someone familiar with gmirror will have to answer that bit... but gmirror status -s looks from the man page like it might be interesting and *that* could be run from cron and parsed to weed out "status OK results". --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCSI Error reported in Daily Run.
Crazy no one replied.
Yea the disk is going bad.
Try:
# sudo camcontrol defects da0 -f block -G
~~BAS
On Fri, 16 Feb 2007, Grant Peel wrote:
Hi all,
Can anyone simplify this error message?
Only seen once, system seems to be running OK.
Fix? Replace?
+++ /tmp/security.hjdAMgoP Fri Feb 16 03:02:47 2007
+(da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 f3 a 3f 0 0 20 0
+(da0:ahc0:0:0:0): CAM Status: SCSI Status Error
+(da0:ahc0:0:0:0): SCSI Status: Check Condition
+(da0:ahc0:0:0:0): Deferred Error: HARDWARE FAILURE info:341b461 asc:44,0
+(da0:ahc0:0:0:0): Internal target failure field replaceable unit: bc
+(da0:ahc0:0:0:0): Retrying Command (per Sense Data)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
scsictl(8) 'detach' equiv in camcontrol(8) ?
NBSD provides a safe way to detach the kernel data structures of a disk, 'scsictl detach [target] [lun]' From scsictl(8) man page: "Commands pertaining to scsi busses: reset scan target lun detach target lun Use `any' or `all' to wildcard target or lun" We seem to be missing this feature. "Stop" is just going to cause the disk to spin down. So what is the equiviliant recommended procedure on FreeBSD? Current thinking: - Umount the FS; - Remove it from any geom(4) devices - Physically pull the drive - Rescan the bus w/ camcontrol and let it discover that the disk is no longer there - Insert the new drive - Rescan the bus and let it discover the new drive Presumably instead of rescanning the whole bus, you could scan a specific bus[:target:lun]. Thoughts? ~BAS l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCSI Error reported in Daily Run.
The drive knows about one bad sector that has developed since the drive
left the factory.
Where I'm at, that's sufficient to have the vendor replace the drive
(because by the time that is a bad sector where live data lives).
~BAS
On Sun, 4 Mar 2007, Grant Peel wrote:
Hi Brian,
Here is the output. Care to decipher for me? :-)
defiant# camcontrol defects da0 -f block -G
camcontrol: requested defect format not available
camcontrol: Device returned physical sector format
Got 1 defect:
70740:1:634
defiant#
-Grant
Crazy no one replied.
Yea the disk is going bad.
Try:
# sudo camcontrol defects da0 -f block -G
~~BAS
On Fri, 16 Feb 2007, Grant Peel wrote:
Hi all,
Can anyone simplify this error message?
Only seen once, system seems to be running OK.
Fix? Replace?
+++ /tmp/security.hjdAMgoP Fri Feb 16 03:02:47 2007
+(da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 f3 a 3f 0 0 20 0
+(da0:ahc0:0:0:0): CAM Status: SCSI Status Error
+(da0:ahc0:0:0:0): SCSI Status: Check Condition
+(da0:ahc0:0:0:0): Deferred Error: HARDWARE FAILURE info:341b461 asc:44,0
+(da0:ahc0:0:0:0): Internal target failure field replaceable unit: bc
+(da0:ahc0:0:0:0): Retrying Command (per Sense Data)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: puc and uart as modules with FreeBSD6.2-REL
The man page I see says that you need sio(4) as well. "iso* at puc? port ?" Or in the fbsd case, the iso module or option in the kernel. ~BAS > Am I missing something obvious, or do I need to compile yet another custom > kernel to get this card working? > > Jonathan > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PowerApp 120/1550 Install problems
sysinstall will frequently silently fail on the physical partitioning stage for any variety of reasons which will fail to create the appropriate slice entries Show us your partition and slice tables? Send logs from the emergency VTY? ~BAS On Sat, 2007-03-17 at 21:02 -0400, Don Munyak wrote: > On 3/17/07, Minnesota Slinky <[EMAIL PROTECTED]> wrote: > > Hey list, > > > > I'm trying to install FreeBSD 6.2-RELEASE on a Dell PowerApp 120 > > (1550) I just purchased. The system claims to have an AIC 7899 SCSI > > host adapter. I've currently got a known-good 9GB Fujitsu hard disk > > in the system, as ID 0. During installation, the disk comes up as > > da0. After going through all the options for install, etc, I get an > > error when it tries to write the file systems: > > > > "Unable to find device node for /dev/da0s1b in /dev!" and mentions > > that installation is aborting. At first I thought it was a problem > > with the SCSI backplane, but RHEL and Window 2000 Server both install > > and operate without problems. > > > > Thanks for your advice! > > > > Eric Crist > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > Don't know the answer, but have a suggestion. > > How about getting a live cd to boot from and then query /var/log for > hardware spec's > > Don > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Logrotating and running a command
Sounds slightly beyond the mandate of newsyslog(8). Although instead
of a path-to-PID, a glob to pass to pkill(8) -HUP ${glob} would be on my
NFR list.
At that point, logrotate(8) may seem appealing (or a custom solution):
postrotate/endscript
The lines between postrotate and endscript (both of which must
appear on lines by themselves) are executed after the log file
is rotated. These directives may only appear inside of a log
file definition. See prerotate as well.
For all your non-posix-signal-honoring-daemons out there.
~BAS
On Fri, 2007-03-16 at 19:22 -0300, José Pablo Fernández wrote:
> Hello,
> I need to rotate some logs, but instead of getting the PID out of a file and
> sending a SIGHUP to that process, like newsyslog does, I need to run a
> command.
> Is that possible with newsyslog? how should I do it?
> Thank you.
--
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.
IMPORTANT: This message contains confidential information and is intended only
for the individual named. If the reader of this message is not an intended
recipient (or the individual responsible for the delivery of this message to an
intended recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unattended FreeBSD install
The trick about make release(7) is that it installs your native /usr/obj into /usr/release_chroot or wherever and begins a fresh make buildworld in it's chroot and doesn't honor or systems' make.conf(5). Good for integrating source patches Bad for pruning out subsystems / profiling. ~BAS On Mon, 2007-03-19 at 15:53 -0400, Dave wrote: > Hello, > I've read a howto on creating your own FreeBSD isos located at: > > http://romana.now.ie/writing/customfreebsdiso.html > > and i'd like to combine this with an unattended file install.cfg i believe > it is. My goal is to go to a box, boot it from CD, then walk away, come > back, and the OS including patches is insalled and ready to go with custom > packages already installed. If anyone has any working configs, so far my > atempts to create an unattend file, have not been successful, i'd appreciate > them. > Thanks. > Dave. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shared object "libintl.so.6" not found
Reinstall gettext from ports as root. Rebuild your shells that are linked against it. Like, ldd /usr/local/bin/bash and see if it's looking for an old version. Maybe a temporary symlink for now? ~BAS On Mon, 2007-03-19 at 18:04 -0400, Gerard Seibert wrote: > FreeBSD-6.2 > > After booting up my system, I receive an error message: > > Shared object "libintl.so.6" not found > > This file should be in /usr/local/lib, but it isn't. I have no idea why. > I can now only log in as root. Since I am not sure where this file even > came from, I don't know how to replace it. > > I assume I don't have to reinstall the OS (I hope) so where do I go from > here? > > Thanks! > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a custom FreeBSD ISO install image
On Wed, 2007-03-21 at 14:15 +0100, Olivier Regnier wrote: > /ncvs/FreeBSD/Release/usr/src/sys/conf && mv newvers.sh foo && sed Is the path right? Relative to your chroot? Main system? What environmental variables did you declare and what does make.conf(5) look like? -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Clustering
Depends on your application / needs. For most application-delivery situations, I would recommend a layer 4 -> layer 7 "Application Switch / Load Balancer"; -- HA and Load balancing. For Beowulf style clustering, check Ports. ~BAS On Wed, 2007-03-21 at 14:03 -0300, [EMAIL PROTECTED] wrote: > Hi all, > > Where is the best place to look for information about clustering > Freebsd? > The freebsd-clustering list seems to be abandoned. > > > - Marcelo Souza > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote logging with syslogd
run syslogd in the foreground without daemonizing: $ sudo syslogd -dv [flags] If you don't see anything, tcpdump(8) and validate that UDP/514 packets are coming in. ~BAS On Wed, 2007-03-21 at 17:35 +0100, Guido Demmenie wrote: > Hello, > > I'm trying to put up a remote logging server. I want to let my > Airport Express send its logs to my FreeBSD server. > > So I said to my Airport to send its logs to the internal ip of my > server, I suppose it works because that's what Apple hardware does. > Now I did the following things on my bsdbox: > > > I appended to syslog.conf: > > # Log remote Airport Express > +airport > *.* /var/log/airport.log > !* > > I touched /var/log/airport.log and it has rw-r- root:wheel rights > > And to rc.conf I added: > > syslogd_enable="YES" > syslogd_flags="-b myhostname.intranet -a *.intranet" > > I restarted syslogd via: > # /etc/rc.d/syslogd restart > > I suppose it should work, but nothing appears in /var/log/airport and > there should be something that it listens for input or not? > > Also I checked netstat -a | grep syslog > udp4 0 0 myhostname.intranet..syslo *.* > > So it looks like it is not listening. > > Anyone any ideas what I'm doing wrong? > > --Guido > > www.rottnic.nl > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: creating rc.d scripts
what does: $ sudo rcorder /usr/local/etc/rc.d/* /etc/rc.d/* ..look like? ~BAS On Wed, 2007-03-21 at 10:57 -0700, Chuck Swiger wrote: > On Mar 21, 2007, at 10:52 AM, Jim Stapleton wrote: > > I created a script in my /usr/local/etc/rc.d directory, but for some > > reason it doesn't auto start when I start my machine. I added entries > > to the rc.conf that I thought should work, but they did not. On a > > related not, my rc.conf file doesn't seem to disable autostart of > > sendmail. Could anyone advise me? > > Your rc script is probably not working because it might not find > python under /usr/local/bin unless you explicitly set $PATH to > include that directory. > > Secondly, you want to use sendmail_enable="NONE" rather than "NO" if > you want to completely disable all of sendmail. Setting it to "NO" > means that there is no sendmail daemon listening on port 25, but > there will still be a local client mqueue runner spawned to handle > local deliveries. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Minus on disk:-)
On Wed, 2007-03-21 at 21:11 +0100, Anders Troback wrote: > Disk status: > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /dev/ad8s2a253678124556 10882853%/ > devfs 1 10 100%/dev > /dev/ad8s2g 35796214 16027612 1690490649%/home > /dev/ad8s2e 1012974-6 931944-0%/tmp > /dev/ad8s2f 20308398 15124786 355894281%/usr > /dev/ad8s2d 1012974258006 67393228%/var > > Hi, > > I'm just curious about this! How can a FS have used -6 bytes? By default, 8% of capacity is reserved for UID0 (root) and is not represented in df(1). Read tunefs(8): -m minfree Specify the percentage of space held back from normal users; the minimum free space threshold. The default value used is 8%. Note that lowering the threshold can adversely affect perfor- mance: o Settings of 5% and less force space optimization to always be used which will greatly increase the overhead for file writes. o The file system's ability to avoid fragmentation will be reduced when the total free space, including the reserve, drops below 15%. As free space approaches zero, throughput can degrade by up to a factor of three over the performance obtained at a 10% threshold. If the value is raised above the current usage level, users will be unable to allocate files until enough files have been deleted to get under the higher threshold. Try this in fstab(5): md /tmpmfs rw,-s64m,-m02 0 ~BAS > > As I said this is not a problem, I'm just curios about how things work > (and can someone please tell me how to make that a -100 Gb:-)) > > Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp write failed, filesystem is full
Just run an MFS /tmp, add to fstab(5) then "mount /tmp" md/tmpmfs rw,-s64m,-m02 0 Let me know if the syntax error persists. ~BAS On Tue, 2007-03-27 at 16:17 +0200, Michele Endrici wrote: > Hi, can anyone help me find a solution to a make problem?? I'm trying > to build a kernel for FreeBSD 6.2 with a new driver but the make > fails. I tryed in both the old and new school ways but it didn't work > anyway. Here is the error i get: > > /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created > for /usr/src/sys/modules/zlib > > -- > >>> stage 2.3: build tools > -- > cd /usr/obj/usr/src/sys/GENERIC; > MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f > /usr/src/sys/dev/aic7xxx/aicasm/Makefile > Warning: Object directory not changed from original > /usr/obj/usr/src/sys/GENERIC > yacc -b aicasm_gram -d -o aicasm_gram.c > /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y > > /tmp: write failed, filesystem is full > yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c > /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y > cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. > -I/usr/src/sys/dev/aic7xxx/aicasm -c > /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c > cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. > -I/usr/src/sys/dev/aic7xxx/aicasm -c > /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c > cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. > -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c > aicasm_gram.c: In function `yyparse': > aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in > this function) > aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once > aicasm_gram.c:2146: error: for each function it appears in.) > aicasm_gram.c:2146: error: syntax error before '}' token > aicasm_gram.c:2201: error: syntax error at end of input > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/GENERIC. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > > First of all it tells me /tmp filesystem is full. I run "df -h" and > it's quite full. > Hence, I've created a symbolic link to another folder to gain more space > > ln -s /tmp /var/tmp_fake > > but i still get the same error. Any suggestion?? > > Michele > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp write failed, filesystem is full
On Tue, 2007-03-27 at 17:42 +0200, Michele Endrici wrote: > build a kernel for FreeBSD 6.2 with a new driver but the make > > fails "build a kernel for FreeBSD 6.2 with a new driver but the make fails" What did you do just pull a new version of the files into your 6.2 tree? from -current? from RELENG_6 branch? Did you get a patch known to work? This isn't Debian >:} -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard Drive problems
Each BIOS maps beep codes into a diagnostic message. Also, are you getting video signal/BIOS on your monitor? ~BAS On Tue, 2007-03-27 at 14:47 -0500, David J Brooks wrote: > On Tuesday 27 March 2007 02:29:29 pm Jason Gretz wrote: > > Hey guys I am adding a hard drive to my FreeBSD 6.1 box and it stalls > > during booting and makes a beeping noise. I know the hard drive is good > > because I just swapped it out of another FreeBSD box… > > > > So I’m kinda stumped, is there anyways to troubleshoot this? I can’t even > > boot in “safe” or “single-user mode” > > Check the jumper settings on the drive itself. You may be trying to add a > drive configured as Master into a chain that's expecting a Slave. > > David -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB HD Problems Version 6.2 i386
To get PCI USB controllers functional, you shouldn't have to change anything in device.hints. I don't have the full thread of this message, but why don't you send your dmesg(8) output, as well as entries that relate to your hard drive being connected. ~BAS On Sat, 2007-03-31 at 20:50 +0100, SEan Strand wrote: > Can any one please confirm that this is the correct place to try and ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
