-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/06/2010 24:04:48, Matthew Lear wrote:
Incidentally, is there a way to easily migrate from a atacontrol created
array to a gmirror created array? I'm running FreeBSD 8.0 on another
machine with a gmirror created RAID1 array with no problem
On Sun, 2010-06-27 at 09:36 +0100, Matthew Seaman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/06/2010 24:04:48, Matthew Lear wrote:
Incidentally, is there a way to easily migrate from a atacontrol created
array to a gmirror created array? I'm running FreeBSD 8.0 on another
Hi,
I moved my installation to a ZFS boot partition today (ad6s1a).
I had an ext2 logical partition living inside slice 4 (ad6s4).
geom_mbr.ko used to take care of that and populate (ad6s[5-9]) and
the correct entry under /dev/ext2fs/.
Now with zfsboot, weird entries (ad6s4s{1,2,5}) are
First off, many thanks to Rick Macklem for making NFSv4 possible in
FreeBSD!
I recently updated my NFS server and clients to v4, but have since noticed
significant performance penalties. For instance, when I try ls a b c (if
a, b, and c are empty directories) on the client, it takes up to 1.87
On Sun, 27 Jun 2010, Rick C. Petty wrote:
First off, many thanks to Rick Macklem for making NFSv4 possible in
FreeBSD!
I recently updated my NFS server and clients to v4, but have since noticed
significant performance penalties. For instance, when I try ls a b c (if
a, b, and c are empty
Hello all,
I just joined this mailing list because I don't know where to look for
help. I hope someone can help me on my problem.
I first installed FreeBSD 8.0 a few weeks after it was officially
released. It was working fine and was able to upgrade it until 8.0-p3.
The system was last rebooted
GNUbie,
Kindly check the screenshot at http://imagebin.org/102605 for the
screen output during bootup. I don't know how to recover this system
and hopefully someone could help me on how to do it.
Can you boot the old kernel[1]?
[1] See
On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote:
Weird, I don't see that here. The only thing I can think of is that the
experimental client/server will try to do I/O at the size of MAXBSIZE
by default, which might be causing a burst of traffic your net interface
can't keep up
On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote:
Weird, I don't see that here. The only thing I can think of is that the
experimental client/server will try to do I/O at the size of MAXBSIZE
by default, which might be causing a burst of traffic your net interface
can't keep up
On Sun, 27 Jun 2010, Rick C. Petty wrote:
Hmm. When I mounted the same filesystem with nfs3 from a different client,
everything started working at almost normal speed (still a little slower
though).
Now on that same host I saw a file get corrupted. On the server, I see
the following:
%
On Sun, 27 Jun 2010, Rick C. Petty wrote:
On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote:
Weird, I don't see that here. The only thing I can think of is that the
experimental client/server will try to do I/O at the size of MAXBSIZE
by default, which might be causing a burst of
On Sun, Jun 27, 2010 at 10:47:41PM -0500, Rick C. Petty wrote:
On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote:
Weird, I don't see that here. The only thing I can think of is that the
experimental client/server will try to do I/O at the size of MAXBSIZE
by default, which
12 matches
Mail list logo
