Re: Some days, it doesn't pay to upgrade ...

2007-03-02 Thread Marc G. Fournier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't know how critical this is, but I just thought about it ... this is my only system running gmirror ... everything seems fine according ot gmirror status, but maybe something iswron gthere I'm not seeing: Mar 3 01:25:52 mars kernel: GEOM_MIR

Re: Problem with portupgrade

2007-03-02 Thread Peter Jeremy
On 2007-Mar-03 10:12:53 +1100, Phillip Ledger <[EMAIL PROTECTED]> wrote: >Even after a complete reinstall of the toll and rebuildig the database >its still giving the same error. anyumore ideas? Exactly what have you re-installed? What versions of ruby* and portupgrade do you have? Have you compa

Re: Some days, it doesn't pay to upgrade ...

2007-03-02 Thread Marc G. Fournier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Based on the suggestion by someone on this list, I setup a screen session with top running, to watch things ... again, after 3 days, the server goes 'out of process' ... this time, of course, I could get in to look around and kill off processes ...

Re: Problem with portupgrade

2007-03-02 Thread Phillip Ledger
Sergey Matveychuk wrote: Michael Proto wrote: Phillip Ledger wrote: i have been trying to get portupgrade working, however everything i try to run it im getting an error with the portsdb. now i have tryed to rebuild it as requested initaly by portupgrade but im still getting an error

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Jeremy Chadwick wrote: ... Is there something I'm missing? I can't see anything missing there from the reproduction steps. Was ad0s1g also ok? The slight differences I did here where the following but I cant seem them being significant: 1. dump -a0uL -C 32 -f /nfs/usr.dmp /usr 2. restore rf u

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Jeremy Chadwick
On Fri, Mar 02, 2007 at 05:00:24PM -, Steven Hartland wrote: > No problem if you have the resources / time to test this now > thats great. > > Here's the steps I used, if you have any questions just shout: > 1. Boot a normal 6.2 install Done. Booted CD image #1, did a standard install, chose

Re: Problem with portupgrade

2007-03-02 Thread Matt
On 3/2/07, Michael Proto <[EMAIL PROTECTED]> wrote: Phillip Ledger wrote: > i have been trying to get portupgrade working, however everything i try > to run it im getting an error with the portsdb. now i have tryed to > rebuild it as requested initaly by portupgrade but im still getting an > erro

Re: Problem with portupgrade

2007-03-02 Thread Sergey Matveychuk
Michael Proto wrote: > Phillip Ledger wrote: >> i have been trying to get portupgrade working, however everything i try >> to run it im getting an error with the portsdb. now i have tryed to >> rebuild it as requested initaly by portupgrade but im still getting an >> error >> >> portupgrade -aRr >>

Re: SATA: AHCI controller reset failure - After Upgrade

2007-03-02 Thread Sven Petai
On Friday 02 March 2007 16:37, Rômulo Lima wrote: > Hi, > > Good morning, my name is Rômulo Lima, I had a problem when make an upgrade > in my Freebsd Server from version 6.1 to 6.2. Before upgrade my SATA disc > controller was working normally: > > atapci1: port > 0xec00-0xec0f,0xe480-0xe487,0xe4

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Jeremy Chadwick wrote: Pardon my ignorance, but can you give me a step-by-step on how to reproduce this? I have a couple VMware FreeBSD sessions up and want to see if I can reproduce it there. I also have an actual FreeBSD testbox at home which I can format and reinstall. (I'm not denying the

Re: Mount on non-empty directories (Was: sysinstall createscorruptfilesystems after repartitioning)

2007-03-02 Thread Steven Hartland
Mike Meyer wrote: You can make that happen: # cd /usr # mount /dev/ /usr # vim vim: not found # ls /usr/bin ls: /usr/bin: No such file or directory # ls bin This will show the contents of /usr/bin before the mount, because it looks in "./bin", and "." is on the original /usr, not the new one. #

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Eric Anderson wrote: So try the same test, with *only* the data partition, without messing with the /usr stuff.. Will do, will be a little while need to wait for some new machines to come in before I can test again. Steve This e.mail is pri

Re: Mount on non-empty directories (Was: sysinstall creates corruptfilesystems after repartitioning)

2007-03-02 Thread Mike Meyer
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed: > Mike Meyer wrote: > > In <[EMAIL PROTECTED]>, Steven Hartland > > As a general rule, deciding that something is "useless and dangerous" > > and removing it isn't the Unix way of doing things. Just because you > > can't see a use f

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Jeremy Chadwick
On Fri, Mar 02, 2007 at 03:37:21PM -, Steven Hartland wrote: > I've rerun the test just to confirm but there are definitely > two seperate issues here: > 1. The ufs created by sysinstall after a repartition is corrupt. > This is totally unrelated to the overlay of /usr as both /usr > and /data

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Mike Meyer
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed: > 2. Once the blank /usr was mounted over the working nfs /usr > apps under /usr couldnt be run e.g. vim gave me no such file.. This is correct behavior. If you want to see the files underneath a mounted file system, you need to us

Re: Mount on non-empty directories (Was: sysinstall creates corruptfilesystems after repartitioning)

2007-03-02 Thread Eric Anderson
On 03/02/07 09:56, Steven Hartland wrote: Mike Meyer wrote: In <[EMAIL PROTECTED]>, Steven Hartland This is just a special case of mounting on a non-empty directory. It should work right. The last mounted file system is the one you get (unless you're using a file system that's designed to behave

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Eric Anderson
On 03/02/07 09:37, Steven Hartland wrote: Jeremy Chadwick wrote: On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote: Mounting an NFS share on top of a skimmed down /usr is very common, and very desirable. You may mount /usr from a small read-only partition (vnode file, etc) and then

Re: Mount on non-empty directories (Was: sysinstall creates corruptfilesystems after repartitioning)

2007-03-02 Thread Steven Hartland
Mike Meyer wrote: In <[EMAIL PROTECTED]>, Steven Hartland This is just a special case of mounting on a non-empty directory. It should work right. The last mounted file system is the one you get (unless you're using a file system that's designed to behave another way). If you unmount the directory

Re: Clamav-90_2 Lockup with freebsd 6.2

2007-03-02 Thread Alexandre Biancalana
Anybody tested today released clamav-0.90.1 ?? On 3/2/07, Carlos Horowicz <[EMAIL PROTECTED]> wrote: Hi, Anybody tried this additionally in /etc/libmap.conf ? [/usr/local/lib/libclamav.so.1] libpthread.so.2 libthr.so.2 clamav-0.90_2 reduced CPU consumption for me on 6.2-Stable since

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Jeremy Chadwick wrote: On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote: Mounting an NFS share on top of a skimmed down /usr is very common, and very desirable. You may mount /usr from a small read-only partition (vnode file, etc) and then mount a different partition or NFS over it

Mount on non-empty directories (Was: sysinstall creates corrupt filesystems after repartitioning)

2007-03-02 Thread Mike Meyer
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed: > Eric Anderson wrote: > > I don't know about the fs corruption, but the double mounts is > > something you asked it to do (maybe unknowingly). When you added > > that partition, one of the options is to mount it. > Clearly an easy

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Eric Anderson
On 03/02/07 08:44, Jeremy Chadwick wrote: On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote: Mounting an NFS share on top of a skimmed down /usr is very common, and very desirable. You may mount /usr from a small read-only partition (vnode file, etc) and then mount a different part

SATA: AHCI controller reset failure - After Upgrade

2007-03-02 Thread Rômulo Lima
Hi, Good morning, my name is Rômulo Lima, I had a problem when make an upgrade in my Freebsd Server from version 6.1 to 6.2. Before upgrade my SATA disc controller was working normally: atapci1: port 0xec00-0xec0f,0xe480-0xe487,0xe400-0xe40f,0xe080-0xe087,0xe000-0xe01f mem 0xd800-0xdfff

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Eric Anderson
On 03/02/07 08:37, Steven Hartland wrote: Eric Anderson wrote: On 03/02/07 07:46, Steven Hartland wrote: Mounting an NFS share on top of a skimmed down /usr is very common, and very desirable. You may mount /usr from a small read-only partition (vnode file, etc) and then mount a different parti

Re: Problem with portupgrade

2007-03-02 Thread Michael Proto
Phillip Ledger wrote: > i have been trying to get portupgrade working, however everything i try > to run it im getting an error with the portsdb. now i have tryed to > rebuild it as requested initaly by portupgrade but im still getting an > error > > portupgrade -aRr > [missing key: categories] [U

Re: Clamav-90_2 Lockup with freebsd 6.2

2007-03-02 Thread Carlos Horowicz
Hi, Anybody tried this additionally in /etc/libmap.conf ? [/usr/local/lib/libclamav.so.1] libpthread.so.2 libthr.so.2 clamav-0.90_2 reduced CPU consumption for me on 6.2-Stable since I added the two sections in libmap.conf -Carlos 2007/3/1, Doug Barton <[EMAIL PROTECTED]>: Martin Bl

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Jeremy Chadwick
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote: > Mounting an NFS share on top of a skimmed down /usr is very common, and > very desirable. You may mount /usr from a small read-only partition > (vnode file, etc) and then mount a different partition or NFS over it if > you detect

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Eric Anderson wrote: On 03/02/07 07:46, Steven Hartland wrote: Mounting an NFS share on top of a skimmed down /usr is very common, and very desirable. You may mount /usr from a small read-only partition (vnode file, etc) and then mount a different partition or NFS over it if you detect the one y

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Eric Anderson
On 03/02/07 07:46, Steven Hartland wrote: Eric Anderson wrote: I don't know about the fs corruption, but the double mounts is something you asked it to do (maybe unknowingly). When you added that partition, one of the options is to mount it. Clearly an easy work around in that case then but p

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Eric Anderson wrote: I don't know about the fs corruption, but the double mounts is something you asked it to do (maybe unknowingly). When you added that partition, one of the options is to mount it. Clearly an easy work around in that case then but personally I would expect a mount to a direc

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Eric Anderson
On 03/01/07 17:42, Steven Hartland wrote: I've been repartitioning some of our machines here and found that using the following method sysinstall creates corrupt filesystems. 1. Boot a machine using an nfs mounted /usr 2. Run: sysctl kern.geom.debugflags=16 to enable writing to the disk mbr 3. r

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Steven Hartland
Sam Leffler wrote: There's a debug flag you can turn on somewhere in the sysinstall menus. It may help diagnose what sysinstall is doing wrong by checking the log msgs. I find sysinstall is best diagnosed inside qemu or vmware so you destructively operate on disk images w/o hosing a real system.

Re: Fixit cd for AMD64 on 6.2-RELEASE problem?

2007-03-02 Thread Steven Hartland
Sam Leffler wrote: Sometime back I needed the fixit CD and hit various problems like this (generated a 1/2 dozen items on my TODO list not all of which have been crossed off yet). This stuff gets precious little testing and could use a champion to help improve it. Seems like a chore most anyone

Re: Apache13/MoinMoin/Python vs PATH? What changed?

2007-03-02 Thread Andrew Reilly
On Thu, Mar 01, 2007 at 02:05:14PM -0500, Daniel Eischen wrote: > >What is the approved "fix" for this problem? Setting a PATH that > >includes /usr/local/bin in /usr/local/etc/rc.d/apache.sh? Or the > >shebang patch to the python script itself, that I have already made? > > Has anyone answered

Re: Clamav-90_2 Lockup with freebsd 6.2

2007-03-02 Thread Martin Blapp
Hi, [/usr/local/sbin/clamd] libpthread.so.2 libthr.so.2 libpthread.so libthr.so libc_r.so.6 libpthread.so.2 Correct, just delete the last line. I forgot to delete the only entry. The right side of that last line should probably refer to libthr.so.2. AFAICS, w

Re: sysinstall creates corrupt filesystems after repartitioning

2007-03-02 Thread Sam Leffler
Steven Hartland wrote: > I've been repartitioning some of our machines here and > found that using the following method sysinstall creates > corrupt filesystems. > > 1. Boot a machine using an nfs mounted /usr > 2. Run: sysctl kern.geom.debugflags=16 to enable writing > to the disk mbr > 3. run sy

Re: Fixit cd for AMD64 on 6.2-RELEASE problem?

2007-03-02 Thread Sam Leffler
Steven Hartland wrote: > I'm currently trying to use the Fixit cd on AMD64 ( 6.2 ) > and it appears it has issues. When trying to fsck a > disk it reports: > fsck: exec fsck_4.2bsd for in /sbin:/usr/sbin: No such file or > directory > > When looking on the mounted volumes for fsck_4.2bsd its

Re: Problems installing JDK 1.5

2007-03-02 Thread Juergen Nickelsen
Dan Nelson <[EMAIL PROTECTED]> writes: > You could also install the native diablo-jdk15 port instead of a Linux > one. I was installing the native port /usr/ports/java/jdk15, only it needs the Linux JDK 1.4.2 to compile the Java sources. But indeed I was ignorant of the diablo port. What is the

Re: Problems installing JDK 1.5

2007-03-02 Thread Juergen Nickelsen
Juergen Nickelsen <[EMAIL PROTECTED]> writes: > On Tue, Feb 27, 2007 at 11:22:44AM -0500, Sam Baskinger wrote: > >> I'm assuming that you installed linux compatibility and then the >> linux-jdk 1.4? I failed to do that and saw a very similar error a while >> back. :) > > That may well be the cas