On Sat, 29 Nov 2008 11:46:40 +0100 Pawel Jakub Dawidek [EMAIL PROTECTED]
wrote about Re: Curious failure of ZFS snapshots:
PJD GK mclane# ll /tank/home/pt/.zfs/
PJD GK ls: snapshot: Bad file descriptor
PJD GK total 0
PJD Is there a way for me to reproduce that?
None that I could tell you
On Sun, 30 Nov 2008 01:05:48 + Pete French
[EMAIL PROTECTED] wrote about Re: Curious failure of ZFS
snapshots:
PF Here is what I am doing - this script is run with an argument '7am' or
PF '7pm' once per day. the mysql database is a slave replication from a
PF master, so there is a continuous
Sorry for the cross-post, but this could be either lists problem.
I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is
running ISC DHCPD 3.0.x from recent ports, and the other dhclient from
make world.
The server is refusing to answer the DISCOVER request, as it thinks the
The make distribution phase of a full build of 7.1 Prerelease, sourced today
(Mon Dec 1 10:34:45 UTC 2008), unfortunately failed.
make distribution DESTDIR=/differentplace
failed (see below), however the following worked ok: buildkernel,
installkernerl, buildworld, installworld. Two systems
Hi,
I am seeing extremely poor performance (~100kB/s) when untaring large tar
files into fresh ufs filesystems. I see the problem with softupdates and
without softupdates but with an async mount. This is a Supermicro X7DB8
board, 4GB, 2 x Xeon 5140.
Sample gstat output:
dT: 1.033s w:
On Nov 26, 2008, at 1:12 PM, Ken Smith wrote:
Unfortunately no. As John indicated in the earlier thread BIOS
issues tend to be extremely hard to diagnose and so far it seems
like its specific to this one motherboard.
Given this problem does cause issues with installs I'd be willing
to provide
Just FYI we are seeing the exact same problem with PS/2 keyboards and
the 6.4 loader, so this may not be a USB-only issue.
The complete lack of response to serious bug reports about 6.4-REL is
fairly shocking.
On Nov 28, 2008, at 5:24 AM, Andriy Gapon wrote:
I did more testing and it
On Mon, 2008-12-01 at 10:20 -0800, Jo Rhett wrote:
On Nov 26, 2008, at 1:12 PM, Ken Smith wrote:
Unfortunately no. As John indicated in the earlier thread BIOS
issues tend to be extremely hard to diagnose and so far it seems
like its specific to this one motherboard.
Given this problem
On Dec 1, 2008, at 11:30 AM, Ken Smith wrote:
Both John and Xin Li have chimed in on the two threads I've seen that
are related to this specific topic. John diagnosed it as a issue with
the BIOS. That's what makes it a nebulous problem. When working on
those sorts of things most people liken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jo Rhett wrote:
On Dec 1, 2008, at 11:30 AM, Ken Smith wrote:
Both John and Xin Li have chimed in on the two threads I've seen that
are related to this specific topic. John diagnosed it as a issue with
the BIOS. That's what makes it a nebulous
On Dec 1, 2008, at 11:59 AM, George V. Neville-Neil wrote:
I have mostly stayed away from these threads because they've often
devolved into unproductive finger pointing.
Please leave the hyperbole out of your posts, or at least attempt to
cut it back. People on these lists are working quite
On Dec 1, 2008, at 12:25 PM, Xin LI wrote:
What I proposed is, to *narrow down* the problem so we can diagnose
further, since nobody has idea at the moment about how the problem
was,
we do need to have further information, or, to get the whole 6.3-6.4
diff reviewed, which is (in my opinion)
At Mon, 1 Dec 2008 10:22:31 -0800,
Jo Rhett wrote:
Just FYI we are seeing the exact same problem with PS/2 keyboards and
the 6.4 loader, so this may not be a USB-only issue.
The complete lack of response to serious bug reports about 6.4-REL is
fairly shocking.
Jo,
I have mostly
At Mon, 1 Dec 2008 12:27:57 -0800,
Jo Rhett wrote:
Now that Core has clearly spoken their mind on this issue, by refusing
to ask freebsd developers to avoid violating the list charter and then
publicly calling out someone for just saying yeah, it's a widely
reported problem ... leaves
Hi,
Just FYI we are seeing the exact same problem with PS/2
keyboards and
the 6.4 loader, so this may not be a USB-only issue.
[ ... ]
On Nov 28, 2008, at 5:24 AM, Andriy Gapon wrote:
I did more testing and it seems that our loader does have
something to
do with the problem.
Hi,
As per my previous message, I've spent about 3 months trying to debug
a problem that was causing all disk I/O to go very slowly.
A first glance this sounds similar to the problem I am having with very slow
I/O on the Areca controller. (see: 7.1-PRERELEASE: arcmsr write
performance
My earlier post falls into the embarrassing, wish that I hadn't category. To
prevent anyone wasting effort, I'm replying.
make distribution DESTDIR=/newplace
requires a
make world DESTDIR=/newplace
as a prerequisite.
The earlier post, caused me to believe that there was an error in
Can someone please confirm or rule out my issue with dhclient sending
bad IP checksum packets. It would really suck if 7.1 was released with a
broken DHCP client.
Jonathan Feally wrote:
Sorry for the cross-post, but this could be either lists problem.
I have 2 boxes running 7-STABLE as of
Replying to my own post ...
I have done a test on the same machine comparing 6.3-p1 to 7.1-PRE. The
performance is the expected ~6MB/s (because of the lack of cache) on
6.3-p1, so the BIOS change doesn't seem to be at fault.
This seems to be a regression somewhere between 6.3 to 7.1. The
Hi all,
Running Exim 4.69 on 7.0-RELEASE-p6 FreeBSD.
The box has been recently upgraded from 6.3 (like 24 hours ago).
Currently Exim is sending the following lines to the log files.
2008-12-01 19:02:35 Failed to get write lock for
/var/spool/exim/db/callout.lockfile: Invalid argument
On Tuesday 02 December 2008 15:57:15 Jonathan Feally wrote:
Can someone please confirm or rule out my issue with dhclient sending
bad IP checksum packets. It would really suck if 7.1 was released with a
broken DHCP client.
I had 7.1-PRE (early Octover) send out DHCP requests without issue,
21 matches
Mail list logo
