Re: panic on boot

> On Wednesday, December 22, 2010 10:58:56 am Daniel Braniss wrote: > > > On Wednesday, December 22, 2010 5:12:03 am Daniel Braniss wrote: > > > > the hardware is Sun Fire X2200 M2, and it's discless, PXE booted. > > > > > > > > this seems to have started sometime before 8.2, and it > > > > 'somet

Re: ZFS v28 on 8.2-PRERELEASE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/22/2010 08:48, ciaby wrote: > P.S. Can i remove the SSD ZIL without upgrading the pool? Simply put `NO' Longer answer, ZFS will complain at the point where you try to replace the log device or remove it and tell you it was formatted using an ol

Re: panic on boot

On Wednesday, December 22, 2010 10:58:56 am Daniel Braniss wrote: > > On Wednesday, December 22, 2010 5:12:03 am Daniel Braniss wrote: > > > the hardware is Sun Fire X2200 M2, and it's discless, PXE booted. > > > > > > this seems to have started sometime before 8.2, and it > > > 'sometimes happens

Re: panic on boot

ok, it happened ... Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. but a- the 15 seconds never happen :-) b- there is some magic to ge

Re: panic on boot

> On Wednesday, December 22, 2010 5:12:03 am Daniel Braniss wrote: > > the hardware is Sun Fire X2200 M2, and it's discless, PXE booted. > > > > this seems to have started sometime before 8.2, and it > > 'sometimes happens': > > > > FreeBSD 8.2-PRERELEASE #15 r4274: Wed Dec 22 09:11:27 IST 2010c4

Re: MCA messages after upgrade to 8.2-BEAT1

On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: > Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 > Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, > Status 0x > Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", I

Re: panic on boot

On Wednesday, December 22, 2010 5:12:03 am Daniel Braniss wrote: > the hardware is Sun Fire X2200 M2, and it's discless, PXE booted. > > this seems to have started sometime before 8.2, and it > 'sometimes happens': > > FreeBSD 8.2-PRERELEASE #15 r4274: Wed Dec 22 09:11:27 IST 2010c40, rbp = > 0x

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

Am 22.12.2010 14:53, schrieb Paul B Mahol: > On 12/22/10, Jeremy Chadwick wrote: >> On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote: >>> Am 22.12.2010 13:44, schrieb Mike Tancsa: >>> > On 12/22/2010 7:03 AM, Matthias Andree wrote: >>> >> Greetings, >>> >> >>> >> I'm tracking 8.2-PR

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

On 12/22/10, Jeremy Chadwick wrote: > On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote: >> Am 22.12.2010 13:44, schrieb Mike Tancsa: >> > On 12/22/2010 7:03 AM, Matthias Andree wrote: >> >> Greetings, >> >> >> >> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to >>

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

Am 22.12.2010 14:29, schrieb Jeremy Chadwick: > On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote: >> Am 22.12.2010 13:44, schrieb Mike Tancsa: >> > On 12/22/2010 7:03 AM, Matthias Andree wrote: >> >> Greetings, >> >> >> >> I'm tracking 8.2-PRERELEASE, and it appears that recent comm

ZFS v28 on 8.2-PRERELEASE

I just downloaded and installed the latest zfs v28 patch (this one: http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101218.patch.xz). System boots fine, a 4-disks RAIDZ set get mounted properly, no problems so far. Thanks a lot to all the FreeBSD community for this great piece of

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

On 12/22/2010 8:21 AM, Matthias Andree wrote: > Am 22.12.2010 13:44, schrieb Mike Tancsa: >> On 12/22/2010 7:03 AM, Matthias Andree wrote: >>> Greetings, >>> >>> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, >>> zfs, >>> vfs, or thereabouts have broken Tinderbox for me

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote: > Am 22.12.2010 13:44, schrieb Mike Tancsa: > > On 12/22/2010 7:03 AM, Matthias Andree wrote: > >> Greetings, > >> > >> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, > >> zfs, > >> vfs, or thereabouts ha

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

Am 22.12.2010 13:44, schrieb Mike Tancsa: > On 12/22/2010 7:03 AM, Matthias Andree wrote: >> Greetings, >> >> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, >> zfs, >> vfs, or thereabouts have broken Tinderbox for me. >> >> I'm mounting my ports tree via nullfs, which

Re: recent 8.2-STABLE commits break nullfs for tinderbox?

On 12/22/2010 7:03 AM, Matthias Andree wrote: > Greetings, > > I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, > zfs, > vfs, or thereabouts have broken Tinderbox for me. > > I'm mounting my ports tree via nullfs, which has been working fine for a year. > > Any ideas,

MCA messages after upgrade to 8.2-BEAT1

Hi, the machine in question was upgraded from 7.3 to FreeBSD 8.2-BETA1 i386 GENERIC After this upgrade, i got following mesages in /var/log/messages every hour. The machine is almost idle (for testing only) Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 Dec 21 12:42:26 k

recent 8.2-STABLE commits break nullfs for tinderbox?

Greetings, I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, zfs, vfs, or thereabouts have broken Tinderbox for me. I'm mounting my ports tree via nullfs, which has been working fine for a year. Any ideas, or further info needed? Best regards Matthias __

panic on boot

the hardware is Sun Fire X2200 M2, and it's discless, PXE booted. this seems to have started sometime before 8.2, and it 'sometimes happens': FreeBSD 8.2-PRERELEASE #15 r4274: Wed Dec 22 09:11:27 IST 2010c40, rbp = 0x80ef5c60 --- da...@rnd:/home/obj/rnd/r+d/stable/8/sys/HUJI amd64 Ti