On Wed, Jun 10, 2009 at 10:58 PM, Dan Naumov wrote:
> You need to mount your /dev/ad6s1d.journal as /usr and not
> /dev/ad6s1d, because this is the new device provided to you by GEOM.
>
> - Dan Naumov
>
>
>
> On Thu, Jun 11, 2009 at 5:50 AM, Garrett Cooper wrote:
>> On Wed, Jun 10, 2009 at 7:44 PM,
You need to mount your /dev/ad6s1d.journal as /usr and not
/dev/ad6s1d, because this is the new device provided to you by GEOM.
- Dan Naumov
On Thu, Jun 11, 2009 at 5:50 AM, Garrett Cooper wrote:
> On Wed, Jun 10, 2009 at 7:44 PM, Garrett Cooper wrote:
>> Hi Pawel, ATA, and Stable folks,
>>
>>
Hi Pawel, ATA, and Stable folks,
This time when I did a reinstall I took the bullet and tried to
use gjournaling instead of softupdates. The unfortunate thing is that
I can't seem to get it to work.
Here's the procedure that I'm trying to follow (based off of [1]):
- sysinstall from scratch w
On Wed, Jun 10, 2009 at 7:44 PM, Garrett Cooper wrote:
> Hi Pawel, ATA, and Stable folks,
>
> This time when I did a reinstall I took the bullet and tried to
> use gjournaling instead of softupdates. The unfortunate thing is that
> I can't seem to get it to work.
>
> Here's the procedure that I'
On Wed, 10 Jun 2009, Marc G. Fournier wrote:
MGF>
MGF> I'm running a couple of brand new servers ... 32G of RAM, very little load
MGF> on it right now, and this morning it locked up with that 'kern.maxswzone'
MGF> error on the console ...
MGF>
MGF> The server is running a reasonably current 7.2-
On Wednesday 10 June 2009 11:04:48 am Marc G. Fournier wrote:
>
> I'm running a couple of brand new servers ... 32G of RAM, very little load
> on it right now, and this morning it locked up with that 'kern.maxswzone'
> error on the console ...
>
> The server is running a reasonably current 7.2-
On Wednesday 10 June 2009 1:15:16 pm M. Warner Losh wrote:
> In message: <200906101307.37181@freebsd.org>
> John Baldwin writes:
> : On Wednesday 10 June 2009 12:45:03 pm Robert wrote:
> : > On Wed, 10 Jun 2009 10:38:36 -0400
> : > John Baldwin wrote:
> : >
> : > > On Wednesday 1
On 10 jun 2009, at 18:58, Paul Schmehl wrote:
--On Wednesday, June 10, 2009 10:02:39 -0500 Ben Stuyts > wrote:
I've upgrade two FreeBSD 7-stable workstations to the latest kernel/
world of today, and now the mouse and keyboard don't react anymore in
the Xorg / KDE login window. Mouse doesn't
In message: <200906101307.37181@freebsd.org>
John Baldwin writes:
: On Wednesday 10 June 2009 12:45:03 pm Robert wrote:
: > On Wed, 10 Jun 2009 10:38:36 -0400
: > John Baldwin wrote:
: >
: > > On Wednesday 10 June 2009 9:19:13 am Robert wrote:
: > > > On Mon, 8 Jun 2009 10:45:39
On Wednesday 10 June 2009 12:45:03 pm Robert wrote:
> On Wed, 10 Jun 2009 10:38:36 -0400
> John Baldwin wrote:
>
> > On Wednesday 10 June 2009 9:19:13 am Robert wrote:
> > > On Mon, 8 Jun 2009 10:45:39 -0400
> > > John Baldwin wrote:
> > >
> > > > On Saturday 06 June 2009 10:14:31 am Robert wro
--On Wednesday, June 10, 2009 10:02:39 -0500 Ben Stuyts wrote:
Hi,
I've upgrade two FreeBSD 7-stable workstations to the latest kernel/
world of today, and now the mouse and keyboard don't react anymore in
the Xorg / KDE login window. Mouse doesn't move, keyboard characters
don't appear in th
Scott Long wrote:
Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got
a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07
ARECA
On Wed, 10 Jun 2009 10:38:36 -0400
John Baldwin wrote:
> On Wednesday 10 June 2009 9:19:13 am Robert wrote:
> > On Mon, 8 Jun 2009 10:45:39 -0400
> > John Baldwin wrote:
> >
> > > On Saturday 06 June 2009 10:14:31 am Robert wrote:
> > > > Greetings
> > > >
> > > > This problem seems the same a
On Wednesday 10 June 2009 9:19:13 am Robert wrote:
> On Mon, 8 Jun 2009 10:45:39 -0400
> John Baldwin wrote:
>
> > On Saturday 06 June 2009 10:14:31 am Robert wrote:
> > > Greetings
> > >
> > > This problem seems the same as this one from May of this year
> > >
> > > http://lists.freebsd.org/pi
Hello all,
I wanted to ask if anyone had issues with Dell R710 4GB with PERC 6/i
on heavy I/O.
I cannot for sure determine that the issue is indeed with the PERC 6/i
controller or hardware problem.
I got the following output after some hammering with creating localy
files 1-10GB with dd and doing
Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07
ARECA RAID ADAPTER0: FIRM
I'm running a couple of brand new servers ... 32G of RAM, very little load
on it right now, and this morning it locked up with that 'kern.maxswzone'
error on the console ...
The server is running a reasonably current 7.2-STABLE:
FreeBSD pluto.hub.org 7.2-STABLE FreeBSD 7.2-STABLE #0: Sun May
Mike Tancsa wrote:
At 08:19 AM 6/10/2009, Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got
a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.2
Thanks Kip I greatly appreciate the
fix!___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Mike Tancsa wrote:
At 08:19 AM 6/10/2009, Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got
a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.2
At 08:19 AM 6/10/2009, Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07
AR
On Mon, 8 Jun 2009 10:45:39 -0400
John Baldwin wrote:
> On Saturday 06 June 2009 10:14:31 am Robert wrote:
> > Greetings
> >
> > This problem seems the same as this one from May of this year
> >
> > http://lists.freebsd.org/pipermail/freebsd-stable/2009-May/050088.html
> >
> > This happens on
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07
ARECA RAID ADAPTER0: FIRMWARE VERSION V1.46 2009-
TB --- 2009-06-10 06:35:37 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-06-10 06:35:37 - starting RELENG_7 tinderbox run for i386/i386
TB --- 2009-06-10 06:35:37 - cleaning the object tree
TB --- 2009-06-10 06:35:52 - cvsupping the source tree
TB --- 2009-06-10 06:35:52 - /usr/bi
hi,
sporadically, I see this:
lockmgr: thread 0xff0004a8b390 unlocking unheld lock
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_lockmgr() at _lockmgr+0x6ae
VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
unionfs_unlock() at unionfs_unlock+0x22f
VOP_UNLOCK_APV()
25 matches
Mail list logo