Re: repeating crashes with 8.1

2010-10-21 Thread Jeremy Chadwick
On Thu, Oct 21, 2010 at 03:28:41PM -0700, Randy Bush wrote: > em0: port 0x2000-0x201f mem > 0xe800-0xe801 irq 16 at device 0.0 on pci13 > > randy > > Jeremy Chadwick wrote: > > > > On Thu, Oct 21, 2010 at 12:08:23PM -0700, Randy Bush wrote: > > > FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30

Re: repeating crashes with 8.1

2010-10-21 Thread Joel Jaeggli
e...@pci0:13:0:0: class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (82573E)' class = network subclass = ethernet e...@pci0:14:0:0: class=0x

Re: repeating crashes with 8.1

2010-10-21 Thread Jack Vogel
pciconf -l I need to know which hardware it is and that doesnt show me. Jack On Thu, Oct 21, 2010 at 3:28 PM, Randy Bush wrote: > em0: port 0x2000-0x201f mem > 0xe800-0xe801 irq 16 at device 0.0 on pci13 > > randy > > Jeremy Chadwick wrote: > > > > On Thu, Oct 21, 2010 at 12:08:23PM

Re: repeating crashes with 8.1

2010-10-21 Thread Mike Tancsa
At 06:51 PM 10/21/2010, Randy Bush wrote: > I need to know which hardware it is and that doesnt show me. how do i find out. pciconf -lvc It will show something like e...@pci0:10:0:0:class=0x02 card=0x34ec8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation

Re: repeating crashes with 8.1

2010-10-21 Thread Randy Bush
> I need to know which hardware it is and that doesnt show me. how do i find out. >> em0: port 0x2000-0x201f mem >> 0xe800-0xe801 irq 16 at device 0.0 on pci13 joel, do you know? randy ___ freebsd-stable@freebsd.org mailing list http://lists.

Re: repeating crashes with 8.1

2010-10-21 Thread Randy Bush
em0: port 0x2000-0x201f mem 0xe800-0xe801 irq 16 at device 0.0 on pci13 randy Jeremy Chadwick wrote: > > On Thu, Oct 21, 2010 at 12:08:23PM -0700, Randy Bush wrote: > > FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30:45 UTC 2010 > > r...@rip.psg.com:/usr/obj/usr/src/sys/RIP amd64 > > > >

Re: repeating crashes with 8.1

2010-10-21 Thread Jeremy Chadwick
On Thu, Oct 21, 2010 at 12:08:23PM -0700, Randy Bush wrote: > FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30:45 UTC 2010 > r...@rip.psg.com:/usr/obj/usr/src/sys/RIP amd64 > > console recording > > em0: discard frame w/o packet header > em0: discard frame w/o packet header > em0: discard frame w/o pa

repeating crashes with 8.1

2010-10-21 Thread Randy Bush
FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30:45 UTC 2010 r...@rip.psg.com:/usr/obj/usr/src/sys/RIP amd64 console recording em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o pack

Re: BIOS limitations on size of bootable zpool?

2010-10-21 Thread Matthew Seaman
On 21/10/2010 18:32, Emil Smolenski wrote: > I think I've encountered the same problem as you. In my configuration > there is also HP server with HP SmartArray with six disks configured as > single disk RAID0 logical units. I don't think it is related to size of > the pool (try to test with small

Re: kpanic on install >32GB of RAM [SEC=UNCLASSIFIED]

2010-10-21 Thread Kostik Belousov
On Thu, Oct 21, 2010 at 09:50:03AM -0700, Sean Bruno wrote: > On Thu, 2010-10-21 at 05:48 -0700, Andriy Gapon wrote: > > on 20/10/2010 21:28 Sean Bruno said the following: > > > I guess, I could replace the kernel on the CD and have them reburn it? > > > > That should work. > > BTW, here I describ

Re: BIOS limitations on size of bootable zpool?

2010-10-21 Thread Emil Smolenski
On Thu, 21 Oct 2010 14:01:09 +0200, Matthew Seaman wrote: Dear all, I'm happy that gptzfsloader will work with just about any zpool configuration you could imagine, but... We have an HP DL185 G5 with a P400 raid array, fully populated with 12 drives. Since there's no JBOD mode (or at least

Re: kpanic on install >32GB of RAM [SEC=UNCLASSIFIED]

2010-10-21 Thread Sean Bruno
On Thu, 2010-10-21 at 05:48 -0700, Andriy Gapon wrote: > on 20/10/2010 21:28 Sean Bruno said the following: > > I guess, I could replace the kernel on the CD and have them reburn it? > > That should work. > BTW, here I described "yet another" way of building custom > recovery/installation > CDs t

Re: BIOS limitations on size of bootable zpool?

2010-10-21 Thread Boris Samorodov
On Thu, 21 Oct 2010 13:01:09 +0100 Matthew Seaman wrote: > Our current > plan is to set up a USB memstick with /boot on it, by adapting the > instructions here: http://wiki.freebsd.org/RootOnZFS/UFSBoot -- which > isn't ideal as the memstick will be a single point of failure. We always use gmirro

Re: kpanic on install >32GB of RAM [SEC=UNCLASSIFIED]

2010-10-21 Thread Andriy Gapon
on 20/10/2010 21:28 Sean Bruno said the following: > I guess, I could replace the kernel on the CD and have them reburn it? That should work. BTW, here I described "yet another" way of building custom recovery/installation CDs that I use: http://wiki.freebsd.org/AvgLiveCD -- Andriy Gapon ___

hast vs ggate+gmirror sychrnoisation speed

2010-10-21 Thread Pete French
Well, I bit the bullet and moved to using hast - all went beautifully, and I migrated the pool with no downtime. The one thing I do notice, however, is that the synchronisation with hast is much slower than the older ggate+gmirror combination. It's about half the speed in fact. When I orginaly set

BIOS limitations on size of bootable zpool?

2010-10-21 Thread Matthew Seaman
Dear all, I'm happy that gptzfsloader will work with just about any zpool configuration you could imagine, but... We have an HP DL185 G5 with a P400 raid array, fully populated with 12 drives. Since there's no JBOD mode (or at least, not one you can get to from the BIOS configuration screens),

Re: 'zfs send -i': destination has been modified

2010-10-21 Thread Alexander Leidinger
Quoting Derek Buttineau (from Wed, 20 Oct 2010 08:56:11 -0400): Seeing similar here Dan, my destination filesystems are becoming modified sometime after the previous snapshot has been sent so the incremental fails to be received. However, the server I'm sending to is not in use so I can