Re: ZFS v28 is ready for wider testing.
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek p...@freebsd.org wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. Woohoo! Thanks for all your hard work on this! Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT]: ClangBSD is selfhosting, we need testers now
On Fri, Apr 16, 2010 at 9:08 AM, Roman Divacky rdiva...@freebsd.org wrote: Hi, ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler. Recently, we've achieved the state when clang can compile all of FreeBSD world on i386/amd64 platforms (including all the C++ apps we have and itself) and a bootable kernel. Thus we feel that the time has come to ask the FreeBSD community for wider testing on i386/amd64 (you sure can help with other platforms too :)). Good job, and thank you! Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Tue, Feb 23, 2010 at 8:20 AM, John Baldwin j...@freebsd.org wrote: On Thursday 18 February 2010 10:38:38 pm Chris wrote: I'm seeing some difference in the bootloader output between using the F12 workaround or not: F12 workaround mode: FreeBSD/i386 boot Default: zroot:/boot/zfsloader boot: status config: NAME STATE zrootONLINE gpt/disk0 ONLINE No F12 key pressed: FreeBSD/i386 boot Default: zroot:/boot/kernel/kernel config: NAME STATE zrootONLINE gpt/disk0 ONLINE What's up with the differences between the Default boot setting? Sorry for the spam but I'm seeing something else very interesting If I boot to Good Mode (F12) and break to the boot: prompt, the system boots if I type /boot/zfsloader. However, if I type /boot/kernel/kernel (as was seen in the Default setting when I didn't hit F12), I get a crash that looks like the following: - FreeBSD/i386 boot Default: zroot:/boot/zfsloader boot: /boot/kernel/kernel int=0006err= efl=00010882 eip=0020 eax=0018b070 ebx=ed7706bd ecx=c72e2ca8 edx= esi=0040 edi=000929d0 ebp=0009279c esp=9401 cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 cs:eip=ff ff ff ff ff ff ff ff 7f-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ss:esp=36 80 0d 07 90 00 00 01-e9 c4 fc ff ff aa ac 84 c0 0f 84 86 00 00 00 a8-80 74 f2 88 c5 b0 3d aa BTX halted - I'm not sure how well we support booting a kernel from boot2 anymore, much less from zfsboot. Using /boot/loader (or /boot/zfsloader) is probably the only tested (and realistically supported) case. Yeah, the last time I tried this it didn't work, but I didn't hunt down why. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Thu, Feb 18, 2010 at 5:31 AM, Chris behrnetwo...@gmail.com wrote: Can you paste the exact error? Are you getting something like: error 1: lba 32 error 1: lba 1 When I've seen the above sequence, it was due to a stack overflow (IIRC), with the result that the loader would start a second time and barf out these errors. The large number in the error might give us a clue as to what's going on. If the number is really large, it might be an indication that your BIOS doesn't reliably read past a certain threshold. ZFS writes a sort of label at the beginning and end of its drives; perhaps the loader is trying to read the label at the end of the disk and is failing (I don't recall whether it tries to read both labels). Matt Matt, Here's exactly what I'm seeing after POST: error 1 lba 179552888 error 1 lba 59243926 ZFS: i/o error - all block copies unavailable Hmm, both those LBAs fit in 28 bits. With a modern BIOS I wouldn't expect problems with those LBAs. It may or may not be related, but I notice that while in this state my hard drive activity light stays on. I think you're probably right about this being a BIOS problem. Does the gptzfsboot 'status' command show the same output when you run it with and without the F12 workaround? Here's what I see from FreeBSD and from gptzfsboot: [root ~]# zpool status pool: glamdring state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM glamdring ONLINE 0 0 0 raidz2 ONLINE 0 0 0 label/glamdring-0 ONLINE 0 0 0 label/glamdring-1 ONLINE 0 0 0 label/glamdring-2 ONLINE 0 0 0 label/glamdring-3 ONLINE 0 0 0 label/glamdring-4 ONLINE 0 0 0 label/glamdring-5 ONLINE 0 0 0 errors: No known data errors ... /boot.config: -Dh Default: glamdring:/boot/zfsloader boot: status pool: glamdring config: NAME STATE glamdring ONLINE raidz2 ONLINE label/glamdring-0 ONLINE label/glamdring-1 ONLINE label/glamdring-2 ONLINE label/glamdring-3 ONLINE label/glamdring-4 ONLINE label/glamdring-5 ONLINE Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Wed, Feb 17, 2010 at 7:46 AM, Chris behrnetwo...@gmail.com wrote: Ok, went back to my 8.0-RELEASE memstick image and after playing with the GPT settings a little and dd'ing all zeros to the disk first, I get a little farther this time. I'm seeing the following: - BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 631kB/1832448kB available memory FreeBSD/i386 bootstrap loader, Revision 1.0 (root@, Wed Feb 17 10:27:40 UTC 2010) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x8924d8 - And that's as far as it gets. Per the handbook, that appears to be stuck somewhere between boot2 and /boot/loader. To me, it looks like it's having a problem loading the kernel. As far as my suspicion of the BIOS not correctly reporting the drives, it looks to me like the bootloader is seeing them so maybe that can be ruled out. I'm glad to see it get farther this time but this is still weird. Any ideas on this one? IIRC the 8.0-RELEASE gptzfsboot/loader lacked some bugfixes. Try using gptzfsboot and zfsloader from -STABLE. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Wed, Feb 17, 2010 at 10:18 AM, Chris behrnetwo...@gmail.com wrote: Shouldn't those bug fixes have been included in CURRENT? If so, my original post shows the problems there. I've also tried using the 8.0-STABLE snapshot dvd1 and got the same errors I got when using CURRENT. Again, not sure why this worked on my desktop box and is failing on the laptop. I'll try copying over gptzfsboot and zfsloader from my 8.0-STABLE machine. My bad, I wasn't reading carefully. -CURRENT has fixes for all the problems I know of. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Wed, Feb 17, 2010 at 7:49 PM, Chris behrnetwo...@gmail.com wrote: As a follow-up to this, I rebuilt world and kernel and updated my system to the latest 8.0-STABLE. I'm still seeing the problem and I can still get around it by choosing my hard drive from the F12 boot menu. I did notice that the bootloader now says it's ZFS enabled whereas it didn't while on 8.0-RELEASE. I also updated the bootcode with: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 adX after installing world. No help there. It seems to me that there's a difference in the way the ZFS-enabled bootloader sees the drives that the BIOS reports as opposed to the non-ZFS-enabled bootloader. Anyone have any ideas on that? I checked for any BIOS updates but it looks like I'm current. It sure would be nice to not have to select my hard drive each time. Can you paste the exact error? Are you getting something like: error 1: lba 32 error 1: lba 1 When I've seen the above sequence, it was due to a stack overflow (IIRC), with the result that the loader would start a second time and barf out these errors. The large number in the error might give us a clue as to what's going on. If the number is really large, it might be an indication that your BIOS doesn't reliably read past a certain threshold. ZFS writes a sort of label at the beginning and end of its drives; perhaps the loader is trying to read the label at the end of the disk and is failing (I don't recall whether it tries to read both labels). Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
