Re: [OT] Apache SSL certificate authentication
On Mon, Sep 29, 2008 at 12:00:09PM -0500, CyberLeo Kitsana wrote: Fraser Tweedale wrote: - Create my CA key and a CSR, and have CACert sign it. Are you sure it's signed as an intermediary CA? cacert.org's website suggests they will only sign leaf certificates. http://wiki.cacert.org/wiki/SubRoot Fortunately, your client certs need not be signed by the same CA as your server cert, and it's probably somewhat pointless to have a client cert (which will be used for your infrastructure alone) vetted by a third party. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ Thanks for the clarification. I hadn't picked up on the fact that you need a special intermediary cert for the server cert to validate up the chain. Well, nevermind. It's just for personal use anyway... if only X.509 could be simple like OpenPGP :) frase pgpqxJMTtc3na.pgp Description: PGP signature
problems installing package gnucash dependecies
Hi all,
I try to install this gnucash package on my amd64 system running freebsd 6.3
and get the following output:
pkg_add -r gnucash
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/Latest/gnucash.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/cdrtools-2.01_6.tbz...
Done.
pkg_add: package 'cdrtools-2.01_6' conflicts with cjk-cdrtools-2.01.20041227_2
pkg_add: please use pkg_delete first to remove conflicting package(s) or -f to
force installation
pkg_add: pkg_add of dependency 'cdrtools-2.01_6' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/gamin-0.1.9.tbz...
Done.
pkg_add: package 'gamin-0.1.9' conflicts with fam-2.6.10_3
pkg_add: please use pkg_delete first to remove conflicting package(s) or -f to
force installation
pkg_add: pkg_add of dependency 'gamin-0.1.9' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/libgsf-gnome-1.14.7.tbz...
Done.
pkg_add: could not find package cdrtools-2.01_6 !
pkg_add: could not find package gamin-0.1.9 !
pkg_add: pkg_add of dependency 'libgsf-gnome-1.14.7' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/goffice-0.4.3_1.tbz...
Done.
pkg_add: could not find package cdrtools-2.01_6 !
pkg_add: could not find package gamin-0.1.9 !
pkg_add: could not find package libgsf-gnome-1.14.7 !
pkg_add: pkg_add of dependency 'goffice-0.4.3_1' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/yelp-2.20.0.tbz...
Done.
pkg_add: could not find package cdrtools-2.01_6 !
pkg_add: could not find package gamin-0.1.9 !
pkg_add: pkg_add of dependency 'yelp-2.20.0' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/gnucash-docs-2.2.0_2.tbz...
Done.
pkg_add: could not find package cdrtools-2.01_6 !
pkg_add: could not find package gamin-0.1.9 !
pkg_add: could not find package yelp-2.20.0 !
pkg_add: pkg_add of dependency 'gnucash-docs-2.2.0_2' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.3-release/All/gtkhtml3-3.12.3_2.tbz...
Done.
pkg_add: could not find package cdrtools-2.01_6 !
pkg_add: could not find package gamin-0.1.9 !
pkg_add: pkg_add of dependency 'gtkhtml3-3.12.3_2' failed!
# pkg_info | grep -e cdrtools gives
cjk-cdrtools-2.01.20041227_2 CD/CD-R[W] and ISO-9660 image creation and
extraction tools
/etc/make.conf gives:
WITH_FAM_SYSTEM=fam
X11BASE=${LOCALBASE}
#WITH_GHOSTSCRIPT_GNU=yes
# added by use.perl 2008-09-16 09:45:34
PERL_VER=5.8.8
PERL_VERSION=5.8.8
WITH_CUPS=YES
CUPS_OVERWRITE_BASE=YES
WITHOUT_LPR=YES
I think I added fam because of the fact that I have built openoffice.org on
numerous occasions.
Hope somebody can help.
Brgds
Dino
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
postfix-pipe complains: no such file or directory
Hi everyone,
i was wondering if someone has experienced this problem i've been having
for 2 weeks now.
I'm running Freebsd 7.0 and postfix-2.5.1.
The thing is that i've set up a filter written in C using postfix's
pipe feature. The filter works great most of the times but every
2-3 days mainly depending on the amount of load... FreeBSD hangs
completely(or almost completely) and leaves this message behind:
pipe[44634]: fatal: pipe_command: execvp
/usr/local/etc/postfix/quota_postfix: No such file or directory.
*
This file is never touched, i mean, it's still there even when the
system says it can't find the file.
I've tried to change permissions of the file, just in case. Right now
the owner is root:wheel, but i've tried postfix, also filter, and so on.
in the master.cf, i've got this:
# quota_postfix
quota_postfix unix- n n - 20 pipe
flags=R user=filter argv=/usr/local/etc/postfix/quota_postfix
localhost 10028 ${sender} ${recipient} ${domain}
has anyone experienced that? it's a very strange thing that only gets
fixed when you restart postfix. Sometimes i even have to reboot the machine.
This started happening some weeks after i upgraded from 6.3 to 7.0, i
had had this script working for over a year without any problem at all.
i would be very pleased if someone can throw some light on this issue.
Thanks in advance
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA READ_DMA timeouts - SOLVED?
The Wikipedia article you refer to documents a very well-known topic: the SATA150-limiting jumpers on hard disks. Drive vendors have this jumper enabled (capped) by default due to incompatibilities with certain in friday i bought 2 new 750GB disks, connected it and got SATA-300, one was samsung other seagate. so not all vendors ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stop in usr/ports/www/firefox3
On Mon, Sep 29, 2008 at 05:54:20AM -0700, Dino Vliet wrote: Hi Laci, I did portsnap fetch update so I guess that should do the trick. Or not? also see [Bug 449373] firefox3 FreeBSD Alpha build fails on bugzilla.mozilla.org I gave up on firefox3 on FBSD Alpha, use kazehakase instead. regards -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual (zaphod) head on Intel i810 does not work for FreeBSD V7.0 Release
I've now spent a month trying to make this work. Sure it sort of works until we try to do consistent graphics work with wish under kde; then we CANNOT get consistent results with and without the second screen. IS THERE ANY WAY TO START THIS MESS LOOKING LIKE ONE SCREEN. IT JUST DOESN'T WORK. Ray Newman On 29/08/2008, at 10:48 PM, John Hein wrote: Ray Newman wrote at 17:56 +1000 on Aug 29, 2008: Under FreeBSD V6.2 Release (X 6.9.0 and i810 1.4.1) with this xorg.conf, this log file is produced and the dual screen config works. . . Under FreeBSD V7.0 Release (X 1.4.0 and i810 1.6.5) with this xorg.conf which is nearly identical with the previous one, this log file is produced and the dual screen doesn't work. It seems to get the primary and secondary screens totally confused. What if you try x11-drivers/xf86-video-intel instead of x11-drivers/xf86-video-i810? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Optimal File System config for 2.5TB RAID5
Hello, I am building a 6x500GB SATA HARDWARE RAID5 storage server to - Store large files, 10BM~1GB/file - Handling 500+ concurrent connections - Transfer rate around 100~200Mbit/s I am thinking of using the patch from Wojciech Puchar to reduce hard drive data seek in order to handle large number of concurrent connections whilst outputting 100~200Mbit/s. patch /usr/src/sys/sys/param.h #ifndef DFLTPHYS #define DFLTPHYS(1024 * 1024) /* default max raw I/O transfer size */ #endif #ifndef MAXPHYS #define MAXPHYS (1024 * 1024) /* max raw I/O transfer size */ #endif #ifndef MAXDUMPPGS To store files greater than 10MB, I come up with the following proposal for my File System: - UFS2 - Soft Update Enable - block-size 1,048,576 I am not completely sure what advantage I got from this configuration but I am pretty sure that FSCK is much quicker with 1M file system block-size. Is there any other thing I need to consider in term of performance and reliability? I hope that this system will perform much better than my current 6x300GB SCSI 10K RPM system. Appreciate any advice, Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Command to rechown
I had to ( chown -R /etc/ ) I to edit the ( pf.conf ), how do I rechowm or restore ( /etc ) ? Can you please send me the command. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SPP qmail
Dear all, I installed freebsd 7.0 install qmail from /usr/ports/mail/qmail instal courier vpopmail. Now i wanna use spp i don't know to how to patch it. Please help me. Yours, Mohsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't add interfaces to bridge
On Monday 29 September 2008 19:40:56 Steve Franks wrote: Just trying to string some old printers the like off my rl0 and get them onto the local wifi net via ath0. ath0 is connected to an AP. Well, currently, you can't bridge rl0 and ath0. If I understood correctly, you want to make the printers available to others computers living on the wifi net, right? 1) Isn't plain IP forwarding enough? You can add a static route to the AP and it will redirect every request for the ethernet_segment to your FreeBSD box, which will forward them to the printers, etc. 2) You can use 1:1 NAT to map each IP address attached to rl0 ethernet segment to another IP on the wifi Is this helping? Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SPP qmail
Of course, i need to know which patch is build in to qmail now. On Tue, 2008-09-30 at 14:02 +0330, Mohsen Pahlevanzadeh wrote: Dear all, I installed freebsd 7.0 install qmail from /usr/ports/mail/qmail instal courier vpopmail. Now i wanna use spp i don't know to how to patch it. Please help me. Yours, Mohsen ___ 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]
error installing smb4k with cups
Hi, Below is the error message. How do I trouble shoot it? Thanks Siju === Patching for cups-base-1.3.5_2 === Applying FreeBSD patches for cups-base-1.3.5_2 Ignoring previously applied (or reversed) patch. 10 out of 10 hunks ignored--saving rejects to cups/ipp.c.rej = Patch patch-CVE-2007-4351 failed to apply cleanly. *** Error code 1 Stop in /usr/ports/print/cups-base. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt33. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt33. *** Error code 1 Stop in /usr/ports/net/smb4k. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Optimal File System config for 2.5TB RAID5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Do wrote: Hello, I am building a 6x500GB SATA HARDWARE RAID5 storage server to - Store large files, 10BM~1GB/file - Handling 500+ concurrent connections - Transfer rate around 100~200Mbit/s I am thinking of using the patch from Wojciech Puchar to reduce hard drive data seek in order to handle large number of concurrent connections whilst outputting 100~200Mbit/s. patch /usr/src/sys/sys/param.h #ifndef DFLTPHYS #define DFLTPHYS(1024 * 1024) /* default max raw I/O transfer size */ #endif #ifndef MAXPHYS #define MAXPHYS (1024 * 1024) /* max raw I/O transfer size */ #endif #ifndef MAXDUMPPGS To store files greater than 10MB, I come up with the following proposal for my File System: - UFS2 - Soft Update Enable - block-size 1,048,576 I am not completely sure what advantage I got from this configuration but I am pretty sure that FSCK is much quicker with 1M file system block-size. Is there any other thing I need to consider in term of performance and reliability? I hope that this system will perform much better than my current 6x300GB SCSI 10K RPM system. Appreciate any advice, Danny Why do you think slower drives using an interface that has known problems handling concurrent connections will be faster than faster drives using an interface designed for concurrency? Based on my experiences with SATA vs. U160/U320 SCSI or SAS your likely outcome is to see a marked decrease in performance. I'd be interested to hear your results. - -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5ABC 11B4 26F9 01F1 27AF AECB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFI4hxmJvkB8SevrssRAqErAJ0Tt9WPT25RhkUfGVLxEzSykEMvtwCeKXRV jdgJ/whLeeAQ3E97i7FkB4w= =UyD6 -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]
Re: Command to rechown
Mike Price wrote: I had to ( chown -R /etc/ ) I to edit the ( pf.conf ), how do I rechowm or restore ( /etc ) ? Can you please send me the command. Hmm, why did you have to chown an entire directory to edit one file? su(1), and, perhaps even better, sudo(8) are meant for such things AFAIK. As for restoring permissions on /etc/, mtree(8) is your friend ... I'd recommend taking a look at the manpage, however, because IANAE. However, all disclaimers included, I *think* you want % cd / % mtree -U -f /etc/mtree/BSD.root.dist Kevin Kinsey -- It is now pitch dark. If you proceed, you will likely fall into a pit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Optimal File System config for 2.5TB RAID5
On Tue, Sep 30, 2008 at 7:32 AM, Josh Paetzel [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Do wrote: Hello, I am building a 6x500GB SATA HARDWARE RAID5 storage server to - Store large files, 10BM~1GB/file - Handling 500+ concurrent connections - Transfer rate around 100~200Mbit/s I am thinking of using the patch from Wojciech Puchar to reduce hard drive data seek in order to handle large number of concurrent connections whilst outputting 100~200Mbit/s. patch /usr/src/sys/sys/param.h #ifndef DFLTPHYS #define DFLTPHYS(1024 * 1024) /* default max raw I/O transfer size */ #endif #ifndef MAXPHYS #define MAXPHYS (1024 * 1024) /* max raw I/O transfer size */ #endif #ifndef MAXDUMPPGS To store files greater than 10MB, I come up with the following proposal for my File System: - UFS2 - Soft Update Enable - block-size 1,048,576 I am not completely sure what advantage I got from this configuration but I am pretty sure that FSCK is much quicker with 1M file system block-size. Is there any other thing I need to consider in term of performance and reliability? I hope that this system will perform much better than my current 6x300GB SCSI 10K RPM system. Appreciate any advice, Danny Why do you think slower drives using an interface that has known problems handling concurrent connections will be faster than faster drives using an interface designed for concurrency? Based on my experiences with SATA vs. U160/U320 SCSI or SAS your likely outcome is to see a marked decrease in performance. I'd be interested to hear your results. - -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5ABC 11B4 26F9 01F1 27AF AECB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFI4hxmJvkB8SevrssRAqErAJ0Tt9WPT25RhkUfGVLxEzSykEMvtwCeKXRV jdgJ/whLeeAQ3E97i7FkB4w= =UyD6 -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] Interface concurrent connection problems?, do you have a link or something? actually i recommend again the RAID 10, if you want performance for heavy I/O (multiple reading,not only one file lineal reading) for storage intensive apps its the way to go. -- mmm, interesante. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Optimal File System config for 2.5TB RAID5
Why do you think slower drives using an interface that has known problems handling concurrent connections will be faster than faster drives using an interface designed for concurrency? My current 6x300GB SCSI system using the FreeBSD default max raw I/O transfer size (64KB). Assume that all reads are random. In order to read 1MB from the hard drive, it would cost: - 1024/64 * (seek time + time to read 64K) - 16 * (8ms + 1ms) [average seek time on SATA 7200RPM is 8ms, make it 0ms for read time] - 128ms to read 1MB If I change the default max raw I/O transfer size to 1MB it would only cost (8ms seek time + 2.6ms read 1MB using SATA300). So, the time to read 1MB is only about 10.6ms. As we can see here reading 1MB from the hard disk is at least 10 times better if we increase the default max raw I/O transfer size to 1MB. This is mainly because the main cost for reading random data from hard disk is seek time. I think the drawback from such configuration is that our server will consume at least: - n concurrent connections * default max raw I/O transfer size of memory just for reading the data from hard disk. RAM quite cheap these days, I think it's ok. Based on my experiences with SATA vs. U160/U320 SCSI or SAS your likely outcome is to see a marked decrease in performance. I'd be interested to hear your results. If both SATA and SCSI system using the same configuration, the end result should be obvious. However, If SCSI system using 64K IO transfer size whilst SATA using 1MB IO transfer size, I don't know! I think the SATA system will outperform the SCSI system. I'll let you know when I get the new SATA system from my ISP. Cheers, Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Optimal File System config for 2.5TB RAID5
SATA using 1MB IO transfer size, I don't know! I think the SATA system will SATA drives aren't much slower than SCSI. simply make this 1MB IO transfer size. as you still want hardware RAID5 it looks you simply read maybe every second word from my mails we exchanged privately. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recompile kernel or module for ipfw+nat?
however, there is a kernel module called ipdivert.ko Is it still necessary to recompile the kernel in order to use nat with ipfw? Or, to put it another way, is there a possibility to use nat and keep the generic kernel? You can choose to use the modules or make it static by recompile the kernel. IMHO the ipnat(8) is a more simple way to get nat. Thank you for your input. I'd prefer to use the module, however it doesn't seem to work: # ipfw add nat 123 all from any to any -- example from the man page gives: ipfw: getsockopt(IP_FW_ADD): Invalid argument even though: # kldstat Id Refs AddressSize Name ... 62 0xc440 d000 ipfw.ko 71 0xc9b33000 4000 ipdivert.ko So, the original question remains - do I really need to recompile the kernel in order to use NAT with IPFW? As far as ipnat(8) goes, switching to ipfilter (which is mandatory if I intend to use ipnat?) is not really an option. Thanks, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Optimal File System config for 2.5TB RAID5
Hi Wojciech Puchar, The reason I want to use hardware RAID is because I got so much problem with software RAID5 4 years ago on FreeBSD 5.4. I still remember those nightmares. Furthermore, hardware RAID5 doesn't require much knowledge and management. But you could be right, the CPU speed is triple now, software RAID gets smarter and more stable, it could perform better than hardware RAID because it's more flexible. But again, I still prefer hardware because it's easy to use and easy to manage. Thanks all the tips Wojciech Puchar, Danny -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Tuesday, 30 September 2008 9:16 PM To: Danny Do Cc: 'Josh Paetzel'; freebsd-questions@freebsd.org Subject: RE: Optimal File System config for 2.5TB RAID5 SATA using 1MB IO transfer size, I don't know! I think the SATA system will SATA drives aren't much slower than SCSI. simply make this 1MB IO transfer size. as you still want hardware RAID5 it looks you simply read maybe every second word from my mails we exchanged privately. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
built-in samba mount
Hello all, Is it possible to mount the samba share //pc/share/folder? It is possible to do this in Windows and it works. I have troubles in FreeBSD: I'm able to mount only //pc/share (not //pc/share/folder) and I do not have read access to read contents of //pc/share and FreeBSD does not let me to change the directory to //pc/share/folder. Windows allows to mount //pc/share/folder and I have no access problems in Windows. Is there any solution for FreeBSD? Thanks beforehand. Best regards, EforeZZ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA READ_DMA timeouts - SOLVED?
Jeremy Chadwick wrote: (I'm not subscribed to freebsd-questions, so please CC me on replies. I'm also not sure how I ended up getting this mail in the first place; it looks like someone BCC'd my [EMAIL PROTECTED] address). Yes, I BCC'd you since you are maintaining a page on the wiki documenting SATA DMA problems. Furthermore, one of the most common reports on the FreeBSD lists is the exact opposite -- users complaining that their disks are SATA300 but only operate at SATA150 (caused by that jumper). Users are told to remove the jumper, and are reminded that the reason the jumper is enabled by default is said chipset incompatibilities. That said, your mail confuses me for one reason: Were you receiving DMA errors with the jumper REMOVED (e.g. SATA300 operation), or with the jumper ENABLED (SATA150 operation)? Your below description does not state what exactly you did with the jumper to make your drives work reliably, only that the jumper capability on your disks was available. I should have been more clear. My disks came with no cap on the SATA150 jumper, although FreeBSD reported that they were in SATA150 mode. The system would be unusable from READ_DMA timeouts if the system was ever powered off and brought back up. I had to do some voodoo of booting in single user mode with ACPI turned off to repair filesystems and rebuild my gmirror, then load ACPI and drop back into multi-user mode. I even had to do this if the system was powered off gracefully. So far, since I capped the jumpers this has not been the case. I still get them periodically if I do something like rebuild a gmirror component, so I can no longer say my problem is completely resolved. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA READ_DMA timeouts - SOLVED?
On Tuesday 30 September 2008 18:54:12 Reid Linnemann wrote: Jeremy Chadwick wrote: (I'm not subscribed to freebsd-questions, so please CC me on replies. I'm also not sure how I ended up getting this mail in the first place; it looks like someone BCC'd my [EMAIL PROTECTED] address). Yes, I BCC'd you since you are maintaining a page on the wiki documenting SATA DMA problems. Furthermore, one of the most common reports on the FreeBSD lists is the exact opposite -- users complaining that their disks are SATA300 but only operate at SATA150 (caused by that jumper). Users are told to remove the jumper, and are reminded that the reason the jumper is enabled by default is said chipset incompatibilities. That said, your mail confuses me for one reason: Were you receiving DMA errors with the jumper REMOVED (e.g. SATA300 operation), or with the jumper ENABLED (SATA150 operation)? Your below description does not state what exactly you did with the jumper to make your drives work reliably, only that the jumper capability on your disks was available. I should have been more clear. My disks came with no cap on the SATA150 jumper, although FreeBSD reported that they were in SATA150 mode. The system would be unusable from READ_DMA timeouts if the system was ever powered off and brought back up. I had to do some voodoo of booting in single user mode with ACPI turned off to repair filesystems and rebuild my gmirror, then load ACPI and drop back into multi-user mode. I even had to do this if the system was powered off gracefully. So far, since I capped the jumpers this has not been the case. I still get them periodically if I do something like rebuild a gmirror component, so I can no longer say my problem is completely resolved. Is this on 7.x? Sounds very similar to my experience described in: http://www.freebsd.org/cgi/query-pr.cgi?pr=122572cat=kern The machine is now operational and working in UDMA33 mode with two gmirror'ed SATA, using 6.3-p4. Unfortunately, I can't risk trying 7.x anymore, since it's emergency storage for the main fileserver, so dataloss is unacceptable :/. I do not know about the jumper state at the moment. I will inform if there will be a window real soon now, to check for jumpers. Ata info: # atacontrol list ATA channel 0: Master: acd0 HL-DT-STDVD-ROM GDR-T10N/1.02 ATA/ATAPI revision 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 WDC WD6400AAKS-65A7B0/01.03B01 Serial ATA II Slave: no device present ATA channel 3: Master: ad6 WDC WD6400AAKS-65A7B0/01.03B01 Serial ATA II Slave: no device present # atacontrol cap ad4 Protocol Serial ATA II device model WDC WD6400AAKS-65A7B0 serial number WD-WMASY1885186 firmware revision 01.03B01 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 1250263728 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security no no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes yes 128/0x80128/0x80 # atacontrol mode ad4 current mode = UDMA33 -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: built-in samba mount
On Tue, Sep 30, 2008 at 07:18:32PM +0300, EforeZZ wrote: Hello all, Is it possible to mount the samba share //pc/share/folder? It should be. I have troubles in FreeBSD: I'm able to mount only //pc/share (not //pc/share/folder) and I do not have read access to read contents of //pc/share and FreeBSD does not let me to change the directory to //pc/share/folder. Windows allows to mount //pc/share/folder and I have no access problems in Windows. Is there any solution for FreeBSD? Read the mount_smbfs manual page (with the command 'man mount_smbfs'). A quick look tells us that you'll need to use //[EMAIL PROTECTED]/share/folder instead of //pc/share/folder. Other options allow you to configure access rights and owner/group attributes. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp8NCvPIJvjH.pgp Description: PGP signature
RE: Optimal File System config for 2.5TB RAID5
The reason I want to use hardware RAID is because I got so much problem with software RAID5 4 years ago on FreeBSD 5.4. I still remember those nightmares. Furthermore, hardware RAID5 doesn't require much knowledge and management. But you could be right, the CPU speed is triple now, software RAID gets smarter and more stable, it could perform better than hardware RAID because it's more flexible. But again, I still prefer hardware because it's easy to it's someone more than that, still - you don't read my mails carefully. you will get better performance with my patch, but still it will be crappy with your hardware RAIDs compared to what it should be ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
chrooting in a 32-bit world from a 64-bit kernel+world
Hello hackers, I'm trying to cross-compile an i386 FreeBSD system (kernel+world+ports) under my amd64 host : % uname -srm FreeBSD 8.0-CURRENT amd64 I updated my CURRENT sources yesterday. So far I've got a working FreeBSD (kernel+world) in a 512MB image I can dump on a CompactFlash card : # cd /usr/src # make buildworld TARGET=i386 # make buildkernel TARGET=i386 # mount /dev/md0a /mnt (md0 is a 512MB file backed image I bsdlabel'd and newfs'd before) # make installworld TARGET=i386 DESTDIR=/mnt # make distribution TARGET=i386 DESTDIR=/mnt # make installkernel TARGET=i386 DESTDIR=/mnt The problem is that I can't chroot in this 32-bit world. Say I want to install the sysutils/screen port in /mnt : # mkdir /mnt/usr/ports # mount -t nullfs /usr/ports /mnt/usr/ports # mount -t devfs devfs /mnt/dev # chroot /mnt /bin/sh -c cd /usr/ports/sysutils/screen make BATCH=yes \ install clean ELF interpreter /libexec/ld-elf.so.1 not found Abort trap Of course it's the same with the new (new since a year or so) ports DESTDIR since it's based on chroot : # cd /usr/ports/sysutils/screen # make DESTDIR=/mnt install clean === Creating some important subdirectories === Starting chrooted make in /mnt... ELF interpreter /libexec/ld-elf.so.1 not found Abort trap === Chrooted make in /mnt failed === Cleaning up... I can directly execute /mnt/bin/sh or any program in /mnt without problems. As expected, file gives me : /libexec/ld-elf.so.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), stripped /mnt/libexec/ld-elf.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, stripped Host kernel with COMPAT_IA32 and world without WITHOUT_LIB32 didn't help. I tried temporarily replacing /mnt/libexec/ld-elf.so.1 with the 64-bit one, but the same problem occurs. Using ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-current/ is not an option because I don't use default OPTIONS. Is there a way or another to chroot in this i386 world from my amd64 host ? Olivier -- Olivier Smedts _ ASCII ribbon campaign( ) e-mail: [EMAIL PROTECTED] - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: chrooting in a 32-bit world from a 64-bit kernel+world
On Tuesday 30 September 2008 20:44:02 Olivier Smedts wrote: So far I've got a working FreeBSD (kernel+world) in a 512MB image I can dump on a CompactFlash card : # cd /usr/src # make buildworld TARGET=i386 # make buildkernel TARGET=i386 # mount /dev/md0a /mnt (md0 is a 512MB file backed image I bsdlabel'd and newfs'd before) # make installworld TARGET=i386 DESTDIR=/mnt # make distribution TARGET=i386 DESTDIR=/mnt # make installkernel TARGET=i386 DESTDIR=/mnt The problem is that I can't chroot in this 32-bit world. Say I want to install the sysutils/screen port in /mnt : # mkdir /mnt/usr/ports # mount -t nullfs /usr/ports /mnt/usr/ports # mount -t devfs devfs /mnt/dev It's a guess, but at this point: chroot /mnt /etc/rc.d/ldconfig start If that don't work: /sbin/ldconfig -32 -s -f /mnt/var/run/ld-elf.so.hints /mnt/lib \ /mnt/usr/lib Does that work / change the error or no change at all? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: chrooting in a 32-bit world from a 64-bit kernel+world
chroot /mnt /etc/rc.d/ldconfig start If that don't work: /sbin/ldconfig -32 -s -f /mnt/var/run/ld-elf.so.hints /mnt/lib \ /mnt/usr/lib Does that work / change the error or no change at all? -- lost of 32-bit programs won't work, like those assuming some kernel data is some format, ps, top, netstat for example ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Server setup
I am setting up a new server and have a question. This server has three 8GB SCSIs, and one 160 GB IDE. I was interested in striping the SCSIs, which I have done. After installing FreeBSD 7 on the IDE, I set up the stripe and moved /var over to it. So, my first question would be whether I should put /var on the stripe or /usr ? My next question might be whether it was even worth striping the SCSI's and just installing, say, /var/log to one drive, /usr/home to another, etc Final question, assuming I go ahead with putting /var on the SCSI's, how do I now recover the partition that was being used by /var? There's about 3 Gb on there. Perhaps I could just mount it as /usr/ports? or should I choose a different approach? Thanks for any input. OH! BTW. This is going to be a backup server using BackupPC, so I will be installing an additional IDE later. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Writing hald .fdi files
Mon, 29 Sep 2008 22:13:09 +0200 -n
Mel [EMAIL PROTECTED] írta:
On Monday 29 September 2008 21:27:36 Zahemszky Gábor wrote:
So my question: how can I make an .fdi file, which tells to these
automounters:
if this is device X from vendor Y, mount it with mount option XY!
Add a noauto mountpoint to /etc/fstab, with all the correct options.
Though, hal is one of those projects that sparked my sig - too many
ways to possibly do it, not enough straight ways to really do it.
So, maybe check this too:
http://www.freebsd.org/gnome/docs/halfaq.html#q3
Hi!
Thanks for your help, but it doesn't work. I read your mail, and that
faq - btw, yo suggested to put that device info fstab, that faq suggest
the opposite of that.
I tried this line in /etc/fstab (this is line 13.)
/dev/msdosfs/VERBATIM /home/zgabor/VERBATIM
msdosfs large,noauto0 0
- and tried it with /media/VERBATIM, /media, /mnt neither of them
worked. I got the next error box:
fstab: /etc/fstab:13: Inappropriate file type or format
fstab: /etc/fstab:13: Inappropriate file type or format
org.freedesktop.Hal.Device.Volume.UnknownFailure
I tried it with a none string as the mountdir, didn't work, too.
Any other?
Thanks,
Gábor
--
#!/bin/ksh
Z='21N16I25C25E30, 40M30E33E25T15U!';IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ
';set -- $Z;for i;{ [[ $i = ? ]]print $ibreak;[[ $i
= ??? ]]j=$ii=${i%?};typeset -i40 i=8#$i;print -n ${i#???};[[ $j
= ??? ]]print -n ${j#??} j=;typeset +i i;};IFS=' 0123456789 ';set
-- $Z;for i;{ [[ $i = , ]]i=2;[[ $i = ?? ]]||typeset -l i;j=$j
$i;typeset +l i;};print $j
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: chrooting in a 32-bit world from a 64-bit kernel+world
On Tue, Sep 30, 2008 at 09:28:39PM +0200, Mel wrote: On Tuesday 30 September 2008 20:44:02 Olivier Smedts wrote: So far I've got a working FreeBSD (kernel+world) in a 512MB image I can dump on a CompactFlash card : # cd /usr/src # make buildworld TARGET=i386 # make buildkernel TARGET=i386 # mount /dev/md0a /mnt (md0 is a 512MB file backed image I bsdlabel'd and newfs'd before) # make installworld TARGET=i386 DESTDIR=/mnt # make distribution TARGET=i386 DESTDIR=/mnt # make installkernel TARGET=i386 DESTDIR=/mnt The problem is that I can't chroot in this 32-bit world. Say I want to install the sysutils/screen port in /mnt : # mkdir /mnt/usr/ports # mount -t nullfs /usr/ports /mnt/usr/ports # mount -t devfs devfs /mnt/dev It's a guess, but at this point: chroot /mnt /etc/rc.d/ldconfig start First, thank you for replying so fast ! /etc/rc.d/ldconfig is a /bin/sh script, and I can't run /bin/sh in this chroot. Same errors. If that don't work: /sbin/ldconfig -32 -s -f /mnt/var/run/ld-elf.so.hints /mnt/lib \ /mnt/usr/lib After that command, the shared libraries are found, but ld refers to /mnt : # ldconfig -rf /mnt/var/run/ld-elf.so.hints /mnt/var/run/ld-elf.so.hints: search directories: /mnt/lib:/mnt/usr/lib 0:-lc.7 = /mnt/lib/libc.so.7 1:-lcrypt.4 = /mnt/lib/libcrypt.so.4 [...] And then when trying to chroot, still the same problem. I also can't launch ldconfig in the jail : # chroot /mnt/ /sbin/ldconfig -32 -s -f /var/run/ld-elf.so.hints /lib /usr/lib ELF interpreter /libexec/ld-elf.so.1 not found Abandon Cheers, Olivier Does that work / change the error or no change at all? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. -- Olivier Smedts _ ASCII ribbon campaign( ) e-mail: [EMAIL PROTECTED] - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Writing hald .fdi files
On Tuesday 30 September 2008 21:43:20 Zahemszky Gábor wrote: Mon, 29 Sep 2008 22:13:09 +0200 -n Mel [EMAIL PROTECTED] írta: On Monday 29 September 2008 21:27:36 Zahemszky Gábor wrote: So my question: how can I make an .fdi file, which tells to these automounters: if this is device X from vendor Y, mount it with mount option XY! Add a noauto mountpoint to /etc/fstab, with all the correct options. Though, hal is one of those projects that sparked my sig - too many ways to possibly do it, not enough straight ways to really do it. So, maybe check this too: http://www.freebsd.org/gnome/docs/halfaq.html#q3 Hi! Thanks for your help, but it doesn't work. I read your mail, and that faq - btw, yo suggested to put that device info fstab, that faq suggest the opposite of that. Yeah, I just saw that. I distinctly remember a pkg-message from a port that said the opposite. I tried this line in /etc/fstab (this is line 13.) /dev/msdosfs/VERBATIM /home/zgabor/VERBATIM msdosfs large,noauto0 0 Just to make sure, mount /home/zgabor/VERBATIM works with this line? - and tried it with /media/VERBATIM, /media, /mnt neither of them worked. I got the next error box: fstab: /etc/fstab:13: Inappropriate file type or format fstab: /etc/fstab:13: Inappropriate file type or format org.freedesktop.Hal.Device.Volume.UnknownFailure I tried it with a none string as the mountdir, didn't work, too. No idea, I see 'large' is in /usr/local/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi, under vfat allowed options. Maybe you should match on device/vendor string, rather then glabel device node. I've been using devd succesfully, since I last battled with hal, so I'm out of answers. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: chrooting in a 32-bit world from a 64-bit kernel+world
On Tuesday 30 September 2008 21:57:22 Olivier Smedts wrote: On Tue, Sep 30, 2008 at 09:28:39PM +0200, Mel wrote: On Tuesday 30 September 2008 20:44:02 Olivier Smedts wrote: So far I've got a working FreeBSD (kernel+world) in a 512MB image I can dump on a CompactFlash card : # cd /usr/src # make buildworld TARGET=i386 # make buildkernel TARGET=i386 # mount /dev/md0a /mnt (md0 is a 512MB file backed image I bsdlabel'd and newfs'd before) # make installworld TARGET=i386 DESTDIR=/mnt # make distribution TARGET=i386 DESTDIR=/mnt # make installkernel TARGET=i386 DESTDIR=/mnt The problem is that I can't chroot in this 32-bit world. Say I want to install the sysutils/screen port in /mnt : # mkdir /mnt/usr/ports # mount -t nullfs /usr/ports /mnt/usr/ports # mount -t devfs devfs /mnt/dev It's a guess, but at this point: chroot /mnt /etc/rc.d/ldconfig start First, thank you for replying so fast ! /etc/rc.d/ldconfig is a /bin/sh script, and I can't run /bin/sh in this chroot. Same errors. If that don't work: /sbin/ldconfig -32 -s -f /mnt/var/run/ld-elf.so.hints /mnt/lib \ /mnt/usr/lib After that command, the shared libraries are found, but ld refers to /mnt : # ldconfig -rf /mnt/var/run/ld-elf.so.hints /mnt/var/run/ld-elf.so.hints: search directories: /mnt/lib:/mnt/usr/lib 0:-lc.7 = /mnt/lib/libc.so.7 1:-lcrypt.4 = /mnt/lib/libcrypt.so.4 [...] Right. cd /mnt rmdir mnt ln -s . mnt The old chroot symlink hack. And then when trying to chroot, still the same problem. I also can't launch ldconfig in the jail : # chroot /mnt/ /sbin/ldconfig -32 -s -f /var/run/ld-elf.so.hints /lib /usr/lib ELF interpreter /libexec/ld-elf.so.1 not found Abandon If you have /rescue there, maybe chroot /mnt /rescue/ldconfig /lib /usr/lib will help you. I'm pretty sure it's the missing hints causing this. If all this fails, I'd try running /mnt as a jail. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA READ_DMA timeouts - SOLVED?
On Tue, Sep 30, 2008 at 07:29:26PM +0200, Mel wrote: On Tuesday 30 September 2008 18:54:12 Reid Linnemann wrote: Jeremy Chadwick wrote: (I'm not subscribed to freebsd-questions, so please CC me on replies. I'm also not sure how I ended up getting this mail in the first place; it looks like someone BCC'd my [EMAIL PROTECTED] address). Yes, I BCC'd you since you are maintaining a page on the wiki documenting SATA DMA problems. Furthermore, one of the most common reports on the FreeBSD lists is the exact opposite -- users complaining that their disks are SATA300 but only operate at SATA150 (caused by that jumper). Users are told to remove the jumper, and are reminded that the reason the jumper is enabled by default is said chipset incompatibilities. That said, your mail confuses me for one reason: Were you receiving DMA errors with the jumper REMOVED (e.g. SATA300 operation), or with the jumper ENABLED (SATA150 operation)? Your below description does not state what exactly you did with the jumper to make your drives work reliably, only that the jumper capability on your disks was available. I should have been more clear. My disks came with no cap on the SATA150 jumper, although FreeBSD reported that they were in SATA150 mode. The system would be unusable from READ_DMA timeouts if the system was ever powered off and brought back up. I had to do some voodoo of booting in single user mode with ACPI turned off to repair filesystems and rebuild my gmirror, then load ACPI and drop back into multi-user mode. I even had to do this if the system was powered off gracefully. So far, since I capped the jumpers this has not been the case. I still get them periodically if I do something like rebuild a gmirror component, so I can no longer say my problem is completely resolved. Is this on 7.x? Sounds very similar to my experience described in: http://www.freebsd.org/cgi/query-pr.cgi?pr=122572cat=kern The machine is now operational and working in UDMA33 mode with two gmirror'ed SATA, using 6.3-p4. Unfortunately, I can't risk trying 7.x anymore, since it's emergency storage for the main fileserver, so dataloss is unacceptable :/. I do not know about the jumper state at the moment. I will inform if there will be a window real soon now, to check for jumpers. Ata info: # atacontrol list ATA channel 0: Master: acd0 HL-DT-STDVD-ROM GDR-T10N/1.02 ATA/ATAPI revision 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 WDC WD6400AAKS-65A7B0/01.03B01 Serial ATA II Slave: no device present ATA channel 3: Master: ad6 WDC WD6400AAKS-65A7B0/01.03B01 Serial ATA II Slave: no device present # atacontrol cap ad4 Protocol Serial ATA II device model WDC WD6400AAKS-65A7B0 serial number WD-WMASY1885186 firmware revision 01.03B01 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 1250263728 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security no no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes yes 128/0x80128/0x80 # atacontrol mode ad4 current mode = UDMA33 No -- what Reid is reporting is very different. His problem is that his disks came out-of-the-box operating at SATA300 speeds, and his SATA chipset does not work reliably with SATA300. He found that by setting the SAT150-limiting jumper, he achieved stability. What you're seeing here (a SATA drive being limited to ATA33 speed) could be due to one of the following things: 1) BIOS options have set the SATA ports to Compatible or Emulated. What this does is tell your southbridge to emulate the SATA disks as old PATA disks, and I believe the emulation layer does use ATA33 (not ATA66/100/133). This is available so you can use SATA disks on very old operating systems (possibly things like MS-DOS). Enhanced means to run the disks and controller in a standard SATA fashion. Enhanced can also provide you extra functionality, such as Enhanced IDE, Enhanced AHCI, or Enhanced RAID. It depends greatly on the chip being used, and what features it has. 2) Board is using a SATA chipset which lacks a PCI ID table entry in FreeBSD, yet is somehow operating in a generic fashion (I'm not referring to generic AHCI either,
Re: chrooting in a 32-bit world from a 64-bit kernel+world
On Tue, Sep 30, 2008 at 10:38:10PM +0200, Mel wrote: On Tuesday 30 September 2008 21:57:22 Olivier Smedts wrote: On Tue, Sep 30, 2008 at 09:28:39PM +0200, Mel wrote: On Tuesday 30 September 2008 20:44:02 Olivier Smedts wrote: So far I've got a working FreeBSD (kernel+world) in a 512MB image I can dump on a CompactFlash card : # cd /usr/src # make buildworld TARGET=i386 # make buildkernel TARGET=i386 # mount /dev/md0a /mnt (md0 is a 512MB file backed image I bsdlabel'd and newfs'd before) # make installworld TARGET=i386 DESTDIR=/mnt # make distribution TARGET=i386 DESTDIR=/mnt # make installkernel TARGET=i386 DESTDIR=/mnt The problem is that I can't chroot in this 32-bit world. Say I want to install the sysutils/screen port in /mnt : # mkdir /mnt/usr/ports # mount -t nullfs /usr/ports /mnt/usr/ports # mount -t devfs devfs /mnt/dev It's a guess, but at this point: chroot /mnt /etc/rc.d/ldconfig start First, thank you for replying so fast ! /etc/rc.d/ldconfig is a /bin/sh script, and I can't run /bin/sh in this chroot. Same errors. If that don't work: /sbin/ldconfig -32 -s -f /mnt/var/run/ld-elf.so.hints /mnt/lib \ /mnt/usr/lib After that command, the shared libraries are found, but ld refers to /mnt : # ldconfig -rf /mnt/var/run/ld-elf.so.hints /mnt/var/run/ld-elf.so.hints: search directories: /mnt/lib:/mnt/usr/lib 0:-lc.7 = /mnt/lib/libc.so.7 1:-lcrypt.4 = /mnt/lib/libcrypt.so.4 [...] Right. cd /mnt rmdir mnt ln -s . mnt The old chroot symlink hack. And then when trying to chroot, still the same problem. I also can't launch ldconfig in the jail : # chroot /mnt/ /sbin/ldconfig -32 -s -f /var/run/ld-elf.so.hints /lib /usr/lib ELF interpreter /libexec/ld-elf.so.1 not found Abandon If you have /rescue there, maybe chroot /mnt /rescue/ldconfig /lib /usr/lib will help you. I'm pretty sure it's the missing hints causing this. If all this fails, I'd try running /mnt as a jail. Thanks for the advices. At least statically compiled binaries in /rescue work. # chroot /mnt /rescue/sh # /rescue/ldconfig /lib /usr/lib # /rescue/ldconfig -r /var/run/ld-elf.so.hints: search directories: /lib:/usr/lib 0:-lc.7 = /lib/libc.so.7 1:-lcrypt.4 = /lib/libcrypt.so.4 [...] # sh ELF interpreter /libexec/ld-elf.so.1 not found Abort trap # No luck with the symlink hack or a jail : Configuring jails:. Starting jails:ELF interpreter /libexec/ld-elf.so.1 not found cannot start jail fanless: Abort trap . I'll try to boot directly in the 32-bit world with my 64-bit kernel. I think it should work. In that case, there's maybe something to configure in the amd64 host's ldconfig or ld-elf.so.1 before chrooting in a 32-bit world. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. -- Olivier Smedts _ ASCII ribbon campaign( ) e-mail: [EMAIL PROTECTED] - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA READ_DMA timeouts - SOLVED?
Some people have reported that when UDMA33 is shown with SATA disks, that it's purely cosmetical -- that is to say, the actual transfer speed can exceed 33MByte/sec. A series of dd tests reading/writing to the yes it can, but it's much slower than native SATA, at least on system where i tested it. it gets near 60MB/s instead of 90 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Optimal File System config for 2.5TB RAID5
Hi Wojciech Puchar, I got Perc 4E-DI Embedded Raid Adapter (256MB) from DELL for my current SCSI system. They said it's the enterprise class. I don't know much about the performance between software RAID and hardware RAID. Could you please tell me if this type of hardware RAID controller could match the software RAID you were talking about? I don't want to pay for it if I don't really need it. Thanks, Danny -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Wednesday, 1 October 2008 1:56 AM To: Danny Do Cc: freebsd-questions@freebsd.org Subject: RE: Optimal File System config for 2.5TB RAID5 The reason I want to use hardware RAID is because I got so much problem with software RAID5 4 years ago on FreeBSD 5.4. I still remember those nightmares. Furthermore, hardware RAID5 doesn't require much knowledge and management. But you could be right, the CPU speed is triple now, software RAID gets smarter and more stable, it could perform better than hardware RAID because it's more flexible. But again, I still prefer hardware because it's easy to it's someone more than that, still - you don't read my mails carefully. you will get better performance with my patch, but still it will be crappy with your hardware RAIDs compared to what it should be ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Best way to back up mysql database
First, I wanted to say how great this list is. I'm a newbie FreeBSD admin and, besides the Handbook and Absolute FreeBSD (which never seems to leave my desk), this list is the best resource I have. I just had a huge scare today... One of the websites on my server uses a large Mysql database. Somehow, one of the tables got corrupted today. I have been blithely backing up mysql with a simple cron script that ran mysqldump every night. Simple, reliable, and I've never needed it. Today, when I realized the database was corrupted, I scrambled for my backup, and realized that if I hadn't caught the problem today, tomorrow my backup would have been overwritten, and I would have been... well, not a happy camper. Again, I have run into a problem which is stupidly obvious to experienced admins, I'm sure. I want to slap myself, but don't have time. I'll do that after I have a better backup system in place. I am just about to dive into Google in search of a solution, but thought I would fire off a quick request, in case there is an obvious solution that everyone uses. If there is, a name or URL will do. I'll figure out the rest. Any hints much appreciated. Not going home until this is fixed... -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
On Tue, Sep 30, 2008, John Almberg wrote: First, I wanted to say how great this list is. I'm a newbie FreeBSD admin and, besides the Handbook and Absolute FreeBSD (which never seems to leave my desk), this list is the best resource I have. I just had a huge scare today... One of the websites on my server uses a large Mysql database. Somehow, one of the tables got corrupted today. I have been blithely backing up mysql with a simple cron script that ran mysqldump every night. Simple, reliable, and I've never needed it. Today, when I realized the database was corrupted, I scrambled for my backup, and realized that if I hadn't caught the problem today, tomorrow my backup would have been overwritten, and I would have been... well, not a happy camper. I would suggest using something like logrotate to rotate the backups giving you several days of backup files. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 There is nothing as stupid as an educated man if you get him off the thing he was educated in. Will Rogers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
John Almberg [EMAIL PROTECTED] 09/30/08 3:18 PM First, I wanted to say how great this list is. I'm a newbie FreeBSD admin and, besides the Handbook and Absolute FreeBSD (which never seems to leave my desk), this list is the best resource I have. I just had a huge scare today... One of the websites on my server uses a large Mysql database. Somehow, one of the tables got corrupted today. I have been blithely backing up mysql with a simple cron script that ran mysqldump every night. Simple, reliable, and I've never needed it. Today, when I realized the database was corrupted, I scrambled for my backup, and realized that if I hadn't caught the problem today, tomorrow my backup would have been overwritten, and I would have been... well, not a happy camper. Again, I have run into a problem which is stupidly obvious to experienced admins, I'm sure. I want to slap myself, but don't have time. I'll do that after I have a better backup system in place. I am just about to dive into Google in search of a solution, but thought I would fire off a quick request, in case there is an obvious solution that everyone uses. If there is, a name or URL will do. I'll figure out the rest. Any hints much appreciated. Not going home until this is fixed... -- John Off the top of my head, (someone else probably has a better solution, they always do ;) ) why don't you keep more than one backup and rotate them like logs and not overwrite yesterdays backup every day? Hope my 1¢ at least gives you an idea or two. :D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
On Tue, Sep 30, 2008 at 06:18:35PM -0400, John Almberg wrote: I just had a huge scare today... One of the websites on my server uses a large Mysql database. Somehow, one of the tables got corrupted today. Do you know if the table corruption was a result of 1) a MySQL bug (and there are many), 2) filesystem corruption, or 3) disk bit rot? Did you repair the table using myisamchk (assuming it's a MyISAM table), or was the corruption in InnoDB? I have been blithely backing up mysql with a simple cron script that ran mysqldump every night. Simple, reliable, and I've never needed it. Today, when I realized the database was corrupted, I scrambled for my backup, and realized that if I hadn't caught the problem today, tomorrow my backup would have been overwritten, and I would have been... well, not a happy camper. Others have recommended good solutions to you -- improve your cronjob to handle rotations of those mysqldumps, so that you have 1-2 weeks worth of data, that way you can sleep easier if you don't notice the problem for a day or two. There are programs out there (usually in ports) which can help you with this task. Also, just for the record: the fact you're doing a mysqldump is good. It's better than just blindly copying the database files using cp or rsync (there's no locking done in that case so you could risk backing up the tables in the middle of an INSERT); and the cp/rsync method won't work reliably if you're using InnoDB. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Optimal File System config for 2.5TB RAID5
On Wed, Oct 01, 2008 at 04:49:27AM +0700, Danny Do wrote: I got Perc 4E-DI Embedded Raid Adapter (256MB) from DELL for my current SCSI system. They said it's the enterprise class. I don't know much about the performance between software RAID and hardware RAID. I'm not familiar with PERC (LSI) controllers, just for the record. Could you please tell me if this type of hardware RAID controller could match the software RAID you were talking about? What you're asking for is too much -- and this conversation is starting to delve into freebsd-hardware, not freebsd-questions. Unless someone out there has done full benchmarks comparing FreeBSD ZFS or FreeBSD gvinum to a PERC 4E-DI, with all kinds of test cases (what sort of server it is, what it's doing disk-wise, etc.), I doubt you'll be able to get a conclusive answer here. Such benchmarking would require weeks of effort by someone. Heck, I'm not even sure FreeBSD supports the PERC 4E-DI. That said, if you go with that controller, you should be aware of the following things: there are many problems with hardware RAID. 1) If the controller goes bad after the lifetime of the controller has expired, there is very little chance the vendor will give you a replacement controller that understands the metadata of the previous/bad controller. You are flat out stuck with that model of controller for the rest of your life, unless the vendor can *guarantee* backwards compatibility when providing a newer controller. And I'm willing to bet money that general technical support has no idea what metadata is, or any technical details; they just know what they're told (controller X is no longer available, give them controller Y) 2) Driver support is often iffy with such controllers, at least under FreeBSD. FreeBSD SCSI CAM is quite reliable, so that's not the problem. Here's some past evidence of mfi(4) and mpt(4) having problems administrating arrays, or experiencing horrible performance, requiring tuning be done and much troubleshooting: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues 3) You are at the whim of the hardware RAID controller's BIOS. Performance can be affected by bugs in the BIOS, or BIOS bugs can cause you trouble down the road. You have to ask yourself how much you ultimately trust the technical support people at Dell vs. the FreeBSD community. 4) Driver regressions may hurt you. There may be a day when you go to upgrade to FreeBSD 8.0 (when it becomes stable), only to find that your controller isn't recognised, or has odd problems. (I myself just ran into this situation with -CURRENT last week, where my SATA controller isn't detected, while works perfectly in RELENG_7). You're then stuck on an older FreeBSD until those problems can be worked out. The only hardware RAID controller I've seen praise for, under FreeBSD, are Areca controllers. I'm told the performance (on a purely general level) is absolutely incredible/blazing fast. I don't know what those people are comparing against, though. Be aware that many developers, including folks like Matt Dillon (of DragonflyBSD) and Ade Lovett (very familiar with filers and disk storage) recommend you *completely avoid* hardware RAID controllers or on-motherboard RAID (e.g. Intel MatrixRAID), and go with OS-based RAID (ZFS, gvinum, or standalone UFS2+SU filesystems). If you reach a point where disk I/O on that server is becoming so heavy that you feel you need a hardware RAID controller, that would be when you should come back to the list (freebsd-stable, freebsd-hardware, or freebsd-isp) to discuss the problems you're having with performance. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Optimal File System config for 2.5TB RAID5
On Tuesday, September 30, 2008, at 02:44PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: The only hardware RAID controller I've seen praise for, under FreeBSD, are Areca controllers. 3ware has provided very good FreeBSD support as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
I am just about to dive into Google in search of a solution, but thought I would fire off a quick request, in case there is an obvious solution that everyone uses. If there is, a name or URL will do. I'll figure out the rest. Any hints much appreciated. Not going home until this is fixed... Most certainly would want you to not not go home having been there before. Here is a crude way to do this. Find an elegant solution at leisure. The downside is that you if you crash at the wrong time, your job won't start for the next day. Be forewarned, then you stop making backups. You just need to monitor your atq. The gzip step should probably be part of a pipe for efficiency. You could cron this to get around that. I saw the response about repairing corruptions, REPAIR TABLE has thus far kept me from ever reloading. See man on date and use something other than %a to generate a numeric date unique back, that would give you numerous backups if you have the storage. DATE=`date +%a` # echo $DATE # echo Backup Mysql database mysqldump -h localhost -u YOURSQLUSERID -pYOURPASSWORD YOURDATABASE / usr/somedirectory/somefile_$DATE.backup gzip -f /usr/somedirectory/somefile_$DATE.backup /usr/bin/at -f /usr/somedirectory/mysqlbackup.sh midnight ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
On Tue, Sep 30, 2008 at 06:18:35PM -0400, John Almberg wrote: I just had a huge scare today... One of the websites on my server uses a large Mysql database. Somehow, one of the tables got corrupted today. Do you know if the table corruption was a result of 1) a MySQL bug (and there are many), 2) filesystem corruption, or 3) disk bit rot? Did you repair the table using myisamchk (assuming it's a MyISAM table), or was the corruption in InnoDB? 'Corrupted' is the wrong word. I believe it was a software error that destroyed a self-referential relationship within the table. The 'parent_id' field was altered incorrectly. So, it was not a MySQL error, per se. I have been blithely backing up mysql with a simple cron script that ran mysqldump every night. Simple, reliable, and I've never needed it. Today, when I realized the database was corrupted, I scrambled for my backup, and realized that if I hadn't caught the problem today, tomorrow my backup would have been overwritten, and I would have been... well, not a happy camper. Others have recommended good solutions to you -- improve your cronjob to handle rotations of those mysqldumps, so that you have 1-2 weeks worth of data, that way you can sleep easier if you don't notice the problem for a day or two. There are programs out there (usually in ports) which can help you with this task. Also, just for the record: the fact you're doing a mysqldump is good. It's better than just blindly copying the database files using cp or rsync (there's no locking done in that case so you could risk backing up the tables in the middle of an INSERT); and the cp/rsync method won't work reliably if you're using InnoDB. Okay, so I've written a ruby script that will give me one month's worth of backups to a remote server. Each backup looks like 'all.mysql.12.txt', where the number is the day of the week. I'm using scp to copy the backup to a backup server, so I don't lose the backups if the whole server tanks. A month's worth of backups might be overkill, but I have plenty of room on the backup server. Whew... that added a few grey hairs to my collection. Time for a beer and a few slaps upside the head! Thanks to everyone who confirmed a script and mysqldump are an adequate solution. -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
DATE=`date +%a` # echo $DATE # echo Backup Mysql database mysqldump -h localhost -u YOURSQLUSERID -pYOURPASSWORD YOURDATABASE /usr/somedirectory/somefile_$DATE.backup gzip -f /usr/somedirectory/somefile_$DATE.backup /usr/bin/at -f /usr/somedirectory/mysqlbackup.sh midnight Ah, a much simpler solution than my ruby script. I hadn't thought to zip up the file before transferring it. That's an improvement I must add. Thanks: John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to back up mysql database
I run a script from root's crontab (not /etc/crontab) and keep the
login credentials in /root/.my.cnf so they don't have to be embedded
in the script. Not that $gzip is defined as /bin/cat because I move
copies offsite via rsync and disk space is abundant. This script keeps
30 daily backups (configurable).
Crontab entry:
13 20 * * * cd /bak/databases /root/db_backup
db_backup perl script:
#! /usr/bin/perl
use strict;
my $maxbackups = 30;
my $gz='gz';
my $mysqldump = '/usr/local/bin/mysqldump';
my $gzip = '/bin/cat';
my $newfile;
my $filename = 'all_databases.sql';
my $curfile = $filename . .$maxbackups;
unlink $curfile if -f $curfile;
my ($i, $j);
for ($i = $maxbackups - 2; $i = 0; $i--) {
$j = $i + 1;
$curfile = $filename . '.' . $i;
$newfile = $filename . '.' . $j;
rename $curfile, $newfile if -f $curfile;
}
$curfile = $filename . '.' . '0';
my $command = $mysqldump --opt --all-databases | $gzip $curfile;
my $result;
$result = system $command and warn $result;
On Sep 30, 2008, at 4:22 PM, John Almberg wrote:
DATE=`date +%a`
#
echo $DATE
#
echo Backup Mysql database
mysqldump -h localhost -u YOURSQLUSERID -pYOURPASSWORD YOURDATABASE
/usr/somedirectory/somefile_$DATE.backup
gzip -f /usr/somedirectory/somefile_$DATE.backup
/usr/bin/at -f /usr/somedirectory/mysqlbackup.sh midnight
Ah, a much simpler solution than my ruby script. I hadn't thought to
zip up the file before transferring it. That's an improvement I must
add.
Thanks: John
___
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: Best way to back up mysql database
--On September 30, 2008 6:18:35 PM -0400 John Almberg [EMAIL PROTECTED] wrote: First, I wanted to say how great this list is. I'm a newbie FreeBSD admin and, besides the Handbook and Absolute FreeBSD (which never seems to leave my desk), this list is the best resource I have. I just had a huge scare today... One of the websites on my server uses a large Mysql database. Somehow, one of the tables got corrupted today. I have been blithely backing up mysql with a simple cron script that ran mysqldump every night. Simple, reliable, and I've never needed it. Today, when I realized the database was corrupted, I scrambled for my backup, and realized that if I hadn't caught the problem today, tomorrow my backup would have been overwritten, and I would have been... well, not a happy camper. Again, I have run into a problem which is stupidly obvious to experienced admins, I'm sure. I want to slap myself, but don't have time. I'll do that after I have a better backup system in place. I am just about to dive into Google in search of a solution, but thought I would fire off a quick request, in case there is an obvious solution that everyone uses. If there is, a name or URL will do. I'll figure out the rest. Any hints much appreciated. Not going home until this is fixed... Found this on the mysql documentation site: #!/bin/sh date=`date -I` mysqldump --opt --all-databases | bzip2 -c /var/backup/databasebackup-$date.sql.bz2 The date must be something from linux, but you can do it like this in FSBD: #!/bin/sh date=`date +%Y-%m-%d.%H:%M:%S` mysqldump --opt --all-databases | bzip2 -c /var/backup/databasebackup-$date.sql.bz2 Using this makes every dump uniquely named, even if you run several a day, so you would need to edit newsyslog.conf to rotate the dumps after a number of dumps that you choose so you don't keep writing dumps until the hard drive is full. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying
Definition of off64_t
Hi, I am trying to port an application written on Linux to FreeBSD. During compile, I am getting an error saying that off64_t is not defined. Which header file do I need to include to get the definition for off64_t ? Thanks in advance, Chandan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Need to ( re-chown /etc )
I needed to edit the /etc/pf.conf so I accidentally typed: chown -r /etc Can someone please help me with a command to change /etc back to the way it was? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need to ( re-chown /etc )
On Tue, Sep 30, 2008 at 06:57:20PM -0700, Mike Price wrote: I needed to edit the /etc/pf.conf so I accidentally typed: chown -r /etc Can someone please help me with a command to change /etc back to the way it was? Please stop asking this question over and over. You've posted it to the -questions list twice, and to the -hackers list once. Kevin Kinsey [EMAIL PROTECTED] responded to you with an mtree command that should do the trick. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need to ( re-chown /etc )
--On September 30, 2008 6:57:20 PM -0700 Mike Price [EMAIL PROTECTED] wrote: I needed to edit the /etc/pf.conf so I accidentally typed: chown -r /etc Can someone please help me with a command to change /etc back to the way it was? If that is literally the command you typed, you should have gotten an error message, and nothing should have been changed. Chown requires at least one identifier (uid) before it will work. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying
Re: Need to ( re-chown /etc )
Mike Price wrote: I needed to edit the /etc/pf.conf so I accidentally typed: chown -r /etc Can someone please help me with a command to change /etc back to the way it was? Did Kevin Kinsey's suggestion not work? It would be helpful if you gave some hint as to why you're asking this again. However, you should realize that you destroy information when you change all the ownership information to a uniform value. You need to: 1) Know what the value for each file was so you can set it back, or 2) Use your backups, or 3) Check what the standard files are set to in the distribution (as Kevin suggested), or 4) Know that most, but not all, files in /etc are user root and group wheel, use those values, and hope for the best. In other words, there really isn't a command to fix the damage you've done. However, as I'm sure you realize by now, recursively destroying information in or about system files tends to be a bad idea. As is, as a general rule, using chown as a privileged user just so that you can edit a file such as this as an unprivileged user. --Jon Radel [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
RE: Optimal File System config for 2.5TB RAID5
Thanks for the concrete example of the pitfall of hardware RAID Jeremy. I never had any problem with hardware driver, that's why I never thought of it. But you are quite right! I should be avoiding hardware RAID whenever possible. I get much more support and quicker response here than from hardware vendor. Ok, I have to pickup gVinum where I left it 4 years ago. Hopefully, the software is stable now. Thanks again Jeremy Chadwick, Wojciech Puchar and this wonderful community, Danny -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Chadwick Sent: Wednesday, 1 October 2008 5:45 AM To: Danny Do Cc: 'Wojciech Puchar'; freebsd-questions@freebsd.org Subject: Re: Optimal File System config for 2.5TB RAID5 On Wed, Oct 01, 2008 at 04:49:27AM +0700, Danny Do wrote: I got Perc 4E-DI Embedded Raid Adapter (256MB) from DELL for my current SCSI system. They said it's the enterprise class. I don't know much about the performance between software RAID and hardware RAID. I'm not familiar with PERC (LSI) controllers, just for the record. Could you please tell me if this type of hardware RAID controller could match the software RAID you were talking about? What you're asking for is too much -- and this conversation is starting to delve into freebsd-hardware, not freebsd-questions. Unless someone out there has done full benchmarks comparing FreeBSD ZFS or FreeBSD gvinum to a PERC 4E-DI, with all kinds of test cases (what sort of server it is, what it's doing disk-wise, etc.), I doubt you'll be able to get a conclusive answer here. Such benchmarking would require weeks of effort by someone. Heck, I'm not even sure FreeBSD supports the PERC 4E-DI. That said, if you go with that controller, you should be aware of the following things: there are many problems with hardware RAID. 1) If the controller goes bad after the lifetime of the controller has expired, there is very little chance the vendor will give you a replacement controller that understands the metadata of the previous/bad controller. You are flat out stuck with that model of controller for the rest of your life, unless the vendor can *guarantee* backwards compatibility when providing a newer controller. And I'm willing to bet money that general technical support has no idea what metadata is, or any technical details; they just know what they're told (controller X is no longer available, give them controller Y) 2) Driver support is often iffy with such controllers, at least under FreeBSD. FreeBSD SCSI CAM is quite reliable, so that's not the problem. Here's some past evidence of mfi(4) and mpt(4) having problems administrating arrays, or experiencing horrible performance, requiring tuning be done and much troubleshooting: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues 3) You are at the whim of the hardware RAID controller's BIOS. Performance can be affected by bugs in the BIOS, or BIOS bugs can cause you trouble down the road. You have to ask yourself how much you ultimately trust the technical support people at Dell vs. the FreeBSD community. 4) Driver regressions may hurt you. There may be a day when you go to upgrade to FreeBSD 8.0 (when it becomes stable), only to find that your controller isn't recognised, or has odd problems. (I myself just ran into this situation with -CURRENT last week, where my SATA controller isn't detected, while works perfectly in RELENG_7). You're then stuck on an older FreeBSD until those problems can be worked out. The only hardware RAID controller I've seen praise for, under FreeBSD, are Areca controllers. I'm told the performance (on a purely general level) is absolutely incredible/blazing fast. I don't know what those people are comparing against, though. Be aware that many developers, including folks like Matt Dillon (of DragonflyBSD) and Ade Lovett (very familiar with filers and disk storage) recommend you *completely avoid* hardware RAID controllers or on-motherboard RAID (e.g. Intel MatrixRAID), and go with OS-based RAID (ZFS, gvinum, or standalone UFS2+SU filesystems). If you reach a point where disk I/O on that server is becoming so heavy that you feel you need a hardware RAID controller, that would be when you should come back to the list (freebsd-stable, freebsd-hardware, or freebsd-isp) to discuss the problems you're having with performance. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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
Re: Realtek 8111C?
On Mon, Sep 22, 2008 at 8:58 PM, Sebastian [EMAIL PROTECTED] wrote: Andrew Falanga wrote: On Saturday 20 September 2008 12:14:57 Sebastian wrote: Da Rock wrote: I have used the compiled driver on 6.3 with success- but then I've used the driver linked in a post to drivers list. 7.0 is a no go. I tried to compile the current OEM Realtek driver under (v176) on fbsd 6.3, but couldn't get it to build. My foo is a little thin here. :) Where did you get this OEM driver? The oem driver can be found here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PNid=13PFid=5Level=5Conn=4DownTypeID=3GetDown=false It builds just fine on 6.3, once I read the file manual on how to build a kernel module. So far no problems running it with a fair amount of traffic. Awesome! Thanks. If I've been understanding another thread on here, it sounds like there's a FreeBSD driver coming in 7.1. Andy -- A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Definition of off64_t
In the last episode (Sep 30), hibablu said: I am trying to port an application written on Linux to FreeBSD. During compile, I am getting an error saying that off64_t is not defined. Which header file do I need to include to get the definition for off64_t ? There is no need for an off64_t on FreeBSD. The program should use off_t instead, and on Linux, they should add the compiler flags -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 so that off_t is 64 bits on Linux as well. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Setting up gmirror
Hi, I've just finished setting up a new web server, and if I get my DNS stuff correct hopefully an e-mail server too, for my church. Originally, the intention was to use RAID1 on the MOBO. However, the RAID controller on the MOBO consistently tried to make the SATA DVD drive part of the RAID array and wouldn't boot the FreeBSD boot disk. So, at the suggestion of another respondent here, I've decided to use gmirror. Now, it seems that gmirror is, perhaps, newer to FreeBSD than the software RAID stuff in the Handbook. That mentions ccd(4) and doesn't make any mention of gmirror(8). It seems like gmirror is rather easy to work with, and more important, easy to recover from is hardware fails. In any event, I want to make sure I'm understanding the manual page correctly because I don't have anything else to test this on except the churches computer. We have two Seagate 250gb SATA drives. Identical drive models so their sizes are the same. Is this the command, from gmirror(8), the one I'll want to use? Create a mirror on disk with valid data (note that the last sector of the disk will be overwritten). Add another disk to this mirror, so it will be synchronized with existing disk: gmirror label -v -b round-robin data da0 gmirror insert data da1 Though in my case, da0 and da1 will be ad4 and ad5. This seems to be the one I'm looking for, I'm just scared of wiping out more than I bargain for. Andy -- A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql rc script failure
Has anyone else had trouble with starting mysql server with the rc script? I've only just installed from ports (as a dependency, mind) and technically it should just start when you run the rc script - it sets up the db dirs and stuff so it can just run. But I can't get it to do the setup stuff automatically, and so the script fails. I've done the setup manually before so its no real biggy, but I imagine others would be more than a little frustrated. Anyone else have this trouble? I just realised I had to do this last time too... For reference: I'm starting the script manually for testing at this point (if that makes a difference- which I believe it shouldn't). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
