On Wed, Jul 16, 2008 at 2:42 PM, Jo Rhett [EMAIL PROTECTED] wrote:
On Fri, Jul 11, 2008 at 12:59:33AM -0700, Jo Rhett wrote:
Every time it is rebuilding ad0. Every single boot in the last two
weeks.
On Jul 11, 2008, at 9:49 AM, Clifton Royston wrote:
That just means that it halted
jonathan michaels wrote:
Doug, et al,
i for one appreciate this over-engieered responce because it has
given me (and those like me) a chance to get answers to questions that
we have asked for over a year in my case, about this whole bind setup
issue.
I have no idea what you mean by questions
It seems to be something was changed with ACPI support on 7.0-STABLE
so my next system upgrade ended with ACPI HPET not working anymore on
my ASUS A9Rp laptop.
Here is the part of /var/log/dmesg.today dated July 13:
FreeBSD 7.0-STABLE #65: Tue Jul 8 22:05:07 EEST 2008
[EMAIL
On Sat, Jul 19, 2008 at 10:03:15AM +0300, Oleg V. Nauman wrote:
It seems to be something was changed with ACPI support on 7.0-STABLE so
my next system upgrade ended with ACPI HPET not working anymore on my
ASUS A9Rp laptop.
Here is the part of /var/log/dmesg.today dated July 13:
FreeBSD
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
On Sat, Jul 19, 2008 at 10:03:15AM +0300, Oleg V. Nauman wrote:
It seems to be something was changed with ACPI support on 7.0-STABLE so
my next system upgrade ended with ACPI HPET not working anymore on my
ASUS A9Rp laptop.
Here is the part of
I have a large ZFS pool that seems to be partially corrupt, causing a
panic on ZFS startup. This is on a RELENG_7_0 machine.
This is what happens when I try to start ZFS (written down by hand):
ZFS: WARNING: can't process intent log for tank02/home
ZFS: WARNING: can't process intent log for
I've tried neither of these in your particular case, but they might be
worth a try:
Just a suggestion, but try specify vfs.zfs.zil_disable=1 or as a kernel
variable in the boot cli.
You may want to try export and import the pool and see how it likes it
then.
--
Alex
On Sat, 2008-07-19 at 10:51
Alex Trull wrote:
I've tried neither of these in your particular case, but they might be
worth a try:
Just a suggestion, but try specify vfs.zfs.zil_disable=1 or
as a kernel
variable in the boot cli.
You may want to try export and import the pool and see how it likes it
then.
I
On 2008-Jul-18 18:38:36 -0700, Unga [EMAIL PROTECTED] wrote:
As per FAQ, http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html, I
tried to increase the number of ptys:
10.19.1
Build and install a new kernel with the line in the
configuration file:
device pty N
where N is the number
--- On Sat, 7/19/08, Peter Jeremy [EMAIL PROTECTED] wrote:
From: Peter Jeremy [EMAIL PROTECTED]
Subject: Re: Pseudoterminals increase: compilation error
To: Unga [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Date: Saturday, July 19, 2008, 8:04 PM
On 2008-Jul-18 18:38:36 -0700, Unga
Alex Trull wrote:
Just a suggestion, but try specify vfs.zfs.zil_disable=1 or
as a kernel variable in the boot cli.
I just tried this and unfortunately it didn't work. I got the exact same
kernel panic.
I've been looking through the code to try to find a way to fool ZFS into
thinking the
On Sat, 19 Jul 2008, Daniel Eriksson wrote:
DE Just a suggestion, but try specify vfs.zfs.zil_disable=1 or
DE as a kernel variable in the boot cli.
DE
DE I just tried this and unfortunately it didn't work. I got the exact same
DE kernel panic.
DE
DE I've been looking through the code to try
In the last episode (Jul 19), Unga said:
On Sat, 7/19/08, Peter Jeremy wrote:
On 2008-Jul-18 18:38:36 -0700, Unga wrote:
As per FAQ,
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html,
I tried to increase the number of ptys: 10.19.1 Build and
install a new kernel with
On Sat, Jul 19, 2008 at 10:51:21AM +0200, Daniel Eriksson wrote:
I have a large ZFS pool that seems to be partially corrupt, causing a
panic on ZFS startup. This is on a RELENG_7_0 machine.
This is what happens when I try to start ZFS (written down by hand):
ZFS: WARNING: can't process
--- On Sun, 7/20/08, Dan Nelson [EMAIL PROTECTED] wrote:
Expect's error message doesn't say anything except
something isn't
working but I won't tell you what. Run
truss -o truss.log -f expect -c spawn ls
and determine which syscall is failing, with what error
number, just
before
Everyone:
Will FreeBSD 7.1 be released in time to use it as an upgrade to
close the BIND cache poisoning hole? We'd like to upgrade affected
servers to the latest FreeBSD at the same time that we upgrade
BIND if possible.
--Brett Glass
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Glass wrote:
| Everyone:
|
| Will FreeBSD 7.1 be released in time to use it as an upgrade to
| close the BIND cache poisoning hole? We'd like to upgrade affected
| servers to the latest FreeBSD at the same time that we upgrade
| BIND if
I'd like to install a fully tested 7.1-RELEASE, rather than
a snapshot of 7-STABLE (in which there have, apparently, been
some problems due to driver updates and work on the TCP stack).
Alas, I haven't seen any schedule or to do list for the release
process yet -- just a note saying that
At 09:28 PM 7/19/2008, Subhro wrote:
You need to understand the release engineering process of FreeeBSD.
I've been watching it (and testing release candidates) since 2.x, so
I think I may possibly have some understanding of it by now. ;-)
The release edition is essential created from the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Glass wrote:
| I'd like to install a fully tested 7.1-RELEASE, rather than
| a snapshot of 7-STABLE (in which there have, apparently, been
| some problems due to driver updates and work on the TCP stack).
If you presently installed FreeBSD
Brett,
You need to understand the release engineering process of FreeeBSD.
The release edition is essential created from the stabe edition. 7.1R
would not be something new which is *not* present on 7-STABLE today.
In addition, while a particular branch is alive (not declared as end
of life) all
On Sat, Jul 19, 2008 at 09:36:38PM -0600, Brett Glass wrote:
At 09:28 PM 7/19/2008, Subhro wrote:
You need to understand the release engineering process of FreeeBSD.
I've been watching it (and testing release candidates) since 2.x, so
I think I may possibly have some understanding of it by
--- On Sun, 7/20/08, Unga [EMAIL PROTECTED] wrote:
From: Unga [EMAIL PROTECTED]
Subject: Re: Pseudoterminals increase: compilation error
To: Dan Nelson [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Date: Sunday, July 20, 2008, 10:44 AM
--- On Sun, 7/20/08, Dan Nelson
[EMAIL PROTECTED]
23 matches
Mail list logo
