Re: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
on 23/05/2009 05:26 Alexander Motin said the following: Hi. Joe Karthauser wrote: I spoke too soon. It must have just randomly booted, because it is now hanging again. No amount of jiggling cables has made any difference. Can you provide verbose boot messages of your system from the beginning up to the problem? Especially, all related to the ATA. Attached. Do you have AHCI mode enabled in BIOS, or you using legacy ATA emulation? It's set up as AHCI in the bios. What is strange is that it has now started working again. I can't make any sense of it. The machine boots up fine. It was definitely hanging at the ata probes though, just after the ZFS messages are output. Joe Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #7: Fri May 22 23:10:15 BST 2009 r...@athenaeum.tao.org.uk:/usr/obj/usr/src/sys/ATHENAEUM Preloaded elf kernel /boot/kernel/kernel at 0x80b47000. Preloaded elf module /boot/kernel/zfs.ko at 0x80b4719c. Preloaded elf module /boot/kernel/opensolaris.ko at 0x80b47244. Preloaded elf module /boot/kernel/geom_eli.ko at 0x80b472f4. Preloaded elf module /boot/kernel/crypto.ko at 0x80b473a4. Preloaded elf module /boot/kernel/zlib.ko at 0x80b47450. Preloaded elf module /boot/kernel/geom_label.ko at 0x80b474fc. Preloaded elf module /boot/kernel/geom_mirror.ko at 0x80b475ac. Preloaded /boot/zfs/zpool.cache /boot/zfs/zpool.cache at 0x80b4765c. Preloaded elf module /boot/kernel/acpi.ko at 0x80b476b4. module_register: module g_label already exists! Module g_label failed to register: 17 Calibrating clock(s) ... i8254 clock: 1192003 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2402413236 Hz CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz (2402.41-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 4096 kbytes, 16-way associative, 64 bytes/line real memory = 3756916736 (3582 MB) Physical memory chunk(s): 0x1000 - 0x0009dfff, 643072 bytes (157 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0xdbf7, 3677728768 bytes (897883 pages) avail memory = 3673681920 (3503 MB) Table 'FACP' at 0xdfee30c0 Table 'HPET' at 0xdfee7e00 Table 'MCFG' at 0xdfee7e80 Table 'APIC' at 0xdfee7d00 MADT: Found table at 0xdfee7d00 MP Configuration Table version 1.4 found at 0x800f0d00 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 3 ACPI ID 1: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 2 ACPI ID 2: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 1 ACPI ID 3: enabled SMP: Added CPU 1 (AP) ACPI APIC Table: GBTGBTUACPI INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 bios32: Found BIOS32 Service Directory header at 0x800fad30 bios32: Entry = 0xfb3f0 (800fb3f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb420 pnpbios: Found PnP BIOS data at 0x800fbf90 pnpbios: Entry = f:bfc0 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 3 APIC: CPU 2 has ACPI ID 2 APIC: CPU 3 has ACPI ID 1 ULE: setup cpu group 0 ULE: setup cpu 0 ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 ULE: setup cpu group 1 ULE: setup cpu 1 ULE: adding cpu 1 to group 1: cpus 1 mask 0x2 ULE: setup cpu group 2 ULE: setup cpu 2 ULE: adding cpu 2 to group 2: cpus 1 mask 0x4 ULE: setup cpu group 3 ULE: setup cpu 3 ULE: adding cpu 3 to group 3: cpus 1 mask 0x8 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ACPI: RSDP @ 0x0xf6c30/0x0014 (v 0 GBT ) ACPI: RSDT @ 0x0xdfee3040/0x0034 (v 1 GBTGBTUACPI 0x42302E31 GBTU 0x01010101) ACPI: FACP @ 0x0xdfee30c0/0x0074 (v 1 GBTGBTUACPI 0x42302E31 GBTU 0x01010101) ACPI: DSDT @ 0x0xdfee3180/0x4B32 (v 1 GBTGBTUACPI 0x1000 MSFT 0x010C) ACPI: FACS @ 0x0xdfee/0x0040 ACPI: HPET @
Re: ZFS MFC heads up
Kip, On Thu, 21 May 2009, Kip Macy wrote: KM Looks like a (corrupted) space management bug. I'll take a closer look KM this weekend to see if it can be recovered from. Any news on our subject? I would be happy to provide additional info/resources to pinpoint and fix the problem. Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
Kirk Strauser wrote: On Thursday 21 May 2009 09:12:14 am Louis Mamakos wrote: Any pointers to running multiple jails with ZFS? I was looking for something like a union-mount capability for ZFS. I don't necessarily need a jail to run divergent /bin, /usr/local, etc. just the isolation. Making a clone doesn't exactly do the same thing.. FWIW, I love sysutils/ezjail. It uses nullfs to mount many jails on top of the same read-only base system, and provides a way (ezjail-admin update -i) to upgrade that base system with installworld. And ezjail supports managing jails in ZFS filesystems in the CVS version since yesterday. greetings, Philipp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up)
Hi Kip, I seriously don't understand what has happened. If I boot kernel.old I still get the same problem. Very confusing. :(. Joe on 21/05/2009 19:28 Kip Macy said the following: I have no idea what is happening. I think our best bet is having someone with insight into ATA provide us with help in adding diagnostics. Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. Cheers, Kip On Thu, May 21, 2009 at 10:50 AM, Joe Karthauserj...@freebsd.org wrote: Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up)
Motin is your best bet in tracking down ATA problems. Cheers, Kip On Fri, May 22, 2009 at 10:40 AM, Joe Karthauser j...@freebsd.org wrote: Hi Kip, I seriously don't understand what has happened. If I boot kernel.old I still get the same problem. Very confusing. :(. Joe on 21/05/2009 19:28 Kip Macy said the following: I have no idea what is happening. I think our best bet is having someone with insight into ATA provide us with help in adding diagnostics. Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. Cheers, Kip On Thu, May 21, 2009 at 10:50 AM, Joe Karthauserj...@freebsd.org wrote: Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
Hi Alexander, I've love it if you were able to provide some insight into this problem. I'm going to try switching sata cables around next to see if the problem goes away if I disconnect some combination of bays. Thanks, Joe on 22/05/2009 19:39 Kip Macy said the following: Motin is your best bet in tracking down ATA problems. Cheers, Kip On Fri, May 22, 2009 at 10:40 AM, Joe Karthauserj...@freebsd.org wrote: Hi Kip, I seriously don't understand what has happened. If I boot kernel.old I still get the same problem. Very confusing. :(. Joe on 21/05/2009 19:28 Kip Macy said the following: I have no idea what is happening. I think our best bet is having someone with insight into ATA provide us with help in adding diagnostics. Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. Cheers, Kip On Thu, May 21, 2009 at 10:50 AM, Joe Karthauserj...@freebsd.orgwrote: Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
This appears to have gone away now. I unplugged the bay that was causing the trouble, and the system booted just fine on the remaining 4 drives. Then I plugged the bay back in (live) and did an atacontrol detach/attach on that bus (I wonder why I always have to do that). The drive was seen, and ZFS resilvered itself. I'm doing a ZFS scrub now to make sure that everything is good, and I'll do a reboot and see if it's all ok after that. Strange, so it looks like a cable might have got a little loose or something. I wonder why that would have hung the kernel probe though. Joe on 22/05/2009 20:40 Joe Karthauser said the following: Hi Alexander, I've love it if you were able to provide some insight into this problem. I'm going to try switching sata cables around next to see if the problem goes away if I disconnect some combination of bays. Thanks, Joe on 22/05/2009 19:39 Kip Macy said the following: Motin is your best bet in tracking down ATA problems. Cheers, Kip On Fri, May 22, 2009 at 10:40 AM, Joe Karthauserj...@freebsd.org wrote: Hi Kip, I seriously don't understand what has happened. If I boot kernel.old I still get the same problem. Very confusing. :(. Joe on 21/05/2009 19:28 Kip Macy said the following: I have no idea what is happening. I think our best bet is having someone with insight into ATA provide us with help in adding diagnostics. Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. Cheers, Kip On Thu, May 21, 2009 at 10:50 AM, Joe Karthauserj...@freebsd.org wrote: Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
I saw really strange stuff with one bad SATA cable on my 6 drive ZFS array. It would work most of the time, but the scrub would either cough up CRC's or hang. I wound up replacing the disk *AND* the cable, and it's been fine since. This is on a SuperMicro chassis with Intel chips. YMMV -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Joe Karthauser Sent: Friday, May 22, 2009 3:45 PM To: Alexander Motin Cc: freebsd-stable@freebsd.org; Kip Macy Subject: Re: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up)) This appears to have gone away now. I unplugged the bay that was causing the trouble, and the system booted just fine on the remaining 4 drives. Then I plugged the bay back in (live) and did an atacontrol detach/attach on that bus (I wonder why I always have to do that). The drive was seen, and ZFS resilvered itself. I'm doing a ZFS scrub now to make sure that everything is good, and I'll do a reboot and see if it's all ok after that. Strange, so it looks like a cable might have got a little loose or something. I wonder why that would have hung the kernel probe though. Joe on 22/05/2009 20:40 Joe Karthauser said the following: Hi Alexander, I've love it if you were able to provide some insight into this problem. I'm going to try switching sata cables around next to see if the problem goes away if I disconnect some combination of bays. Thanks, Joe on 22/05/2009 19:39 Kip Macy said the following: Motin is your best bet in tracking down ATA problems. Cheers, Kip On Fri, May 22, 2009 at 10:40 AM, Joe Karthauserj...@freebsd.org wrote: Hi Kip, I seriously don't understand what has happened. If I boot kernel.old I still get the same problem. Very confusing. :(. Joe on 21/05/2009 19:28 Kip Macy said the following: I have no idea what is happening. I think our best bet is having someone with insight into ATA provide us with help in adding diagnostics. Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. Cheers, Kip On Thu, May 21, 2009 at 10:50 AM, Joe Karthauserj...@freebsd.org wrote: Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Produ ctID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo
Re: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
I spoke too soon. It must have just randomly booted, because it is now hanging again. No amount of jiggling cables has made any difference. :(. Joe on 22/05/2009 20:40 Joe Karthauser said the following: Hi Alexander, I've love it if you were able to provide some insight into this problem. I'm going to try switching sata cables around next to see if the problem goes away if I disconnect some combination of bays. Thanks, Joe on 22/05/2009 19:39 Kip Macy said the following: Motin is your best bet in tracking down ATA problems. Cheers, Kip On Fri, May 22, 2009 at 10:40 AM, Joe Karthauserj...@freebsd.org wrote: Hi Kip, I seriously don't understand what has happened. If I boot kernel.old I still get the same problem. Very confusing. :(. Joe on 21/05/2009 19:28 Kip Macy said the following: I have no idea what is happening. I think our best bet is having someone with insight into ATA provide us with help in adding diagnostics. Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. Cheers, Kip On Thu, May 21, 2009 at 10:50 AM, Joe Karthauserj...@freebsd.org wrote: Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
Hi. Joe Karthauser wrote: I spoke too soon. It must have just randomly booted, because it is now hanging again. No amount of jiggling cables has made any difference. Can you provide verbose boot messages of your system from the beginning up to the problem? Especially, all related to the ATA. Do you have AHCI mode enabled in BIOS, or you using legacy ATA emulation? -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. If you choose to upgrade a pool to take advantage of new features you will no longer be able to use it with sources prior to today. 'zfs send/recv' is not expected to inter-operate between different pool versions. I think this is not a zfs issue, but it does trigger the problem: on a zfs mounted system via nfs, from linux, an ls .zfs used to panic the server, now it just doesn't work :-). (http://lists.freebsd.org/pipermail/freebsd-fs/2008-October/005217.html) so is this being worked on? btw, i will be trying the new version over the weekend. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On 20.05.2009, at 22:41, Kip Macy wrote: On Wed, May 20, 2009 at 3:11 PM, Mike Tancsa m...@sentex.net wrote: At 05:59 PM 5/20/2009, Kip Macy wrote: If you choose to upgrade a pool to take advantage of new features you will no longer be able to use it with sources prior to today. 'zfs send/recv' is not expected to inter-operate between different pool versions. Primarily what was in Pawel's commit to HEAD (see below). The following changes have also been brought in: - the recurring deadlock was fixed by deferring vinactive to a dedicated thread - zfs boot for all types now works - kmem now goes up to 512GB so arc is now limited by physmem - the arc now experiences backpressure from the vm (which can be too much - but allows ZFS to work without any tunables on amd64) great awesome incredible gorgeous superb fantastic excellent supercool THANX! :-) * dancing around with loud music csupping all over the place... * Lorenzo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
Kip Macy wrote: I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. Mounting local file systems:. internal error: out of memory internal error: out of memory internal error: out of memory internal error: out of memory I get this in dmesg after make installkernel shutdown -r now, zfs pool is not mounted. /usr is on zfs so can't installworld. 2GB memory and 4x 1TB raid-z on amd64, / is 2x 2GB gmirror. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
I get this in dmesg after make installkernel shutdown -r now, zfs pool is not mounted. /usr is on zfs so can't installworld. I can't help, but thanks for the bug report as it prompted me to upgarde both kernel and world at the same time. Which works fine after reboot. If I were you I would reboot the old kerenl and just installworld/meregmaster so you ahhve the whole system in sync. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
Pertti Kosunen pertti.kosu...@pp.nic.fi wrote: Kip Macy wrote: I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. Mounting local file systems:. internal error: out of memory internal error: out of memory internal error: out of memory internal error: out of memory I get this in dmesg after make installkernel shutdown -r now, zfs pool is not mounted. /usr is on zfs so can't installworld. IIRC, that's what happens if ZFS kernel and userland aren't in sync. You'll either have to install the new kernel and userland together (not supported, but I do it all the time), or install the userland from a non-ZFS file system. Fabian signature.asc Description: PGP signature
Re: ZFS MFC heads up
Ran into the same thing on -CURRENT when we went version 13. Some manual intervention fixed it. http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000508.html /glz --On Thursday, May 21, 2009 12:42 PM +0300 Pertti Kosunen pertti.kosu...@pp.nic.fi wrote: Kip Macy wrote: I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. Mounting local file systems:. internal error: out of memory internal error: out of memory internal error: out of memory internal error: out of memory I get this in dmesg after make installkernel shutdown -r now, zfs pool is not mounted. /usr is on zfs so can't installworld. 2GB memory and 4x 1TB raid-z on amd64, / is 2x 2GB gmirror. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
Goran Lowkrantz wrote: Ran into the same thing on -CURRENT when we went version 13. Some manual intervention fixed it. http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000508.html mount -t zfs ... cd /usr/src make NO_FSCHG= installworld This did the job with new kernel. Recommend easier way without reboot.. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
FYI, I just did an upgrade of my RELENG_7 machine with the new ZFS merged in, and it seems to have gone mostly trouble-free. I noticed one weirdness that could be confusion on my part - I'm no longer seeing snapshots when I do 'zfs list'. There's a UI change in the zfs command, and to see snapshots, you have to explicitly ask for them: zfs list -t snapshot scared me there for a moment.. Thanks for all the great work on ZFS in FreeBSD to everyone involved. I look forward to really beating on this now in RELENG_7. Any pointers to running multiple jails with ZFS? I was looking for something like a union-mount capability for ZFS. I don't necessarily need a jail to run divergent /bin, /usr/local, etc. just the isolation. Making a clone doesn't exactly do the same thing.. louie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
on 21/05/2009 17:12 Louis Mamakos said the following: FYI, I just did an upgrade of my RELENG_7 machine with the new ZFS merged in, and it seems to have gone mostly trouble-free. I noticed one weirdness that could be confusion on my part - I'm no longer seeing snapshots when I do 'zfs list'. There's a UI change in the zfs command, and to see snapshots, you have to explicitly ask for them: zfs list -t snapshot scared me there for a moment.. Do 'zpool get all poolname', it might give you a hint as to why :-) -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On Thu, May 21, 2009 at 7:12 AM, Louis Mamakos lo...@transsys.com wrote: FYI, I just did an upgrade of my RELENG_7 machine with the new ZFS merged in, and it seems to have gone mostly trouble-free. I noticed one weirdness that could be confusion on my part - I'm no longer seeing snapshots when I do 'zfs list'. There's a UI change in the zfs command, and to see snapshots, you have to explicitly ask for them: It's a known change made to the zfs tool somewhere around v11 or so. It's documented in all the Solaris notes about ZFS. You have to explicitily list the type of dataset(s) you want to list with zfs list. By default, it only shows filesystems. You even have to use -t if you want to list volumes. Reading up on the Solaris docs for ZFS is quite enlightening. :) -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On May 21, 2009, at 11:22 AM, Freddie Cash wrote: On Thu, May 21, 2009 at 7:12 AM, Louis Mamakos lo...@transsys.com wrote: FYI, I just did an upgrade of my RELENG_7 machine with the new ZFS merged in, and it seems to have gone mostly trouble-free. I noticed one weirdness that could be confusion on my part - I'm no longer seeing snapshots when I do 'zfs list'. There's a UI change in the zfs command, and to see snapshots, you have to explicitly ask for them: It's a known change made to the zfs tool somewhere around v11 or so. It's documented in all the Solaris notes about ZFS. You have to explicitily list the type of dataset(s) you want to list with zfs list. By default, it only shows filesystems. You even have to use -t if you want to list volumes. Reading up on the Solaris docs for ZFS is quite enlightening. :) We might want to update the zfs(1) man page in the examples for the 'list' subcommand. I think I actually like the new behavior, it was just a little unnerving at first to have the snapshots be missing after the MFC. louie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up)
Hmm, I've had a bit of a miserable afternoon trying to fight my RELENG_7 server, which now doesn't boot. :(. So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 disks (gmirror on 500Mb partition on each of five disks, and zraid2 over the rest of each drive). What I did was to update the userland, and then reboot. I didn't upgrade the kernel (but I've subsequently done that and have the same problem). What happens is that the kernel hangs booting just after displaying a LABEL message or ZFS pool/spool message. I _can_ get it to boot if I boot single user with acpi switched off. When I do that I can manually start zfs, and mount all the partitions. However, one of the disks is missing more on that next. The machine is running a gigabyte motherboard (domestic gamer P35 board, similar to this http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2533, although it might be a DS4 variant). I've got 5 of the 6 sata ports wired to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 5-1/4 bays kind of thing). Now, because of the gmirror I can boot the system on any disk, or combination of plugged in disks. I should be able to succeed with the kernel probe up to the attempt to mount the root filesystem irrespective of any zfs pool, etc. And, indeed, this has been working fine for about two years. But, now it hangs in the same place no matter what disk I boot on (I've tried every bay). But, without ACPI enabled it does appear to boot ok... what's going on here? Is it possible that the machine has developed a hardware fault? Ok, finally, if I boot with ACPI disabled then one of the disks is missing. If I unplug it I get a disconnect message from the ata device, and a reconnect and reinit attempt when I plug it back in, but no device appears on the bus. Usually I can do a 'atacontrol detach sata4; sleep 1; atacontrol attach sata4' and the device reappears. This happens on the other buses, but not on the last one. It's not the disk, because if I swap it into another bay, it comes up and appears on the bus. On the other hand it doesn't appear to be that controller or slow in the drive bay because if I unplug all the over disks the system will boot that disk and get as far as the hang hmm. Is this a consequence of disabling the ACPI? Does anyone have a clue what might be going on? Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On Thursday 21 May 2009 09:12:14 am Louis Mamakos wrote: Any pointers to running multiple jails with ZFS? I was looking for something like a union-mount capability for ZFS. I don't necessarily need a jail to run divergent /bin, /usr/local, etc. just the isolation. Making a clone doesn't exactly do the same thing.. FWIW, I love sysutils/ezjail. It uses nullfs to mount many jails on top of the same read-only base system, and provides a way (ezjail-admin update -i) to upgrade that base system with installworld. -- Kirk Strauser ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On Wed, 20 May 2009, Kip Macy wrote: KM I will be MFC'ing the newer ZFS support some time this afternoon. Both KM world and kernel will need to be re-built. Existing pools will KM continue to work without upgrade. KM KM KM If you choose to upgrade a pool to take advantage of new features you KM will no longer be able to use it with sources prior to today. 'zfs KM send/recv' is not expected to inter-operate between different pool KM versions. I updated my poor old moose to the fresh RELENG_7, and panic is still in place: r...@moose:/ar/.bad# ls -la 200807/ total 9089 drwxr-xr-x 3 rscript wheel4 Nov 5 2008 ./ drwxr-xr-x 3 root wheel3 Apr 12 21:33 ../ drwxr-xr-x 2 rscript wheel 36 Apr 2 22:12 daily/ -rw-r--r-- 1 rscript wheel 9207828 Aug 1 2008 total.200807 r...@moose:/ar/.bad# ls -la 200807/daily/ panic: avl_find() succeeded inside avl_add() cpuid = 1 Uptime: 1m27s Physical memory: 2039 MB Dumping 247 MB: 232 216 200 184 168 152 136 120 104 88 72 56 40 24 8 Dump complete on the dump: (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc05352e7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc05355f5 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0843b60 in avl_add (tree=Variable tree is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/common/avl/avl.c:635 #4 0xc08b0edf in zap_lockdir (os=0xc55dfa60, obj=6108, tx=0x0, lti=RW_READER, fatreader=1, adding=0, zapp=0xfc755ba0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c:335 #5 0xc08b13af in zap_cursor_retrieve (zc=0xfc755b9c, za=0xfc755a84) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c:993 #6 0xc08d6340 in zfs_freebsd_readdir (ap=0xfc755c00) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:2156 #7 0xc06de842 in VOP_READDIR_APV (vop=0xc093c560, a=0xfc755c00) at vnode_if.c:1407 #8 0xc05bf88a in kern_getdirentries (td=0xc55c0900, fd=5, buf=0x48215000 Address 0x48215000 out of bounds, count=4096, basep=0xfc755c74) at vnode_if.h:747 #9 0xc05bfab1 in getdirentries (td=0xc55c0900, uap=0xfc755cfc) at /usr/src/sys/kern/vfs_syscalls.c:3785 #10 0xc06d3588 in syscall (frame=0xfc755d38) at /usr/src/sys/i386/i386/trap.c:1090 #11 0xc06b8f40 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:255 #12 0x0033 in ?? () Previous frame inner to this frame (corrupt stack?) Any other info we need to examine this further? Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
Looks like a (corrupted) space management bug. I'll take a closer look this weekend to see if it can be recovered from. -Kip On Thu, May 21, 2009 at 12:50 PM, Dmitry Morozovsky ma...@rinet.ru wrote: On Wed, 20 May 2009, Kip Macy wrote: KM I will be MFC'ing the newer ZFS support some time this afternoon. Both KM world and kernel will need to be re-built. Existing pools will KM continue to work without upgrade. KM KM KM If you choose to upgrade a pool to take advantage of new features you KM will no longer be able to use it with sources prior to today. 'zfs KM send/recv' is not expected to inter-operate between different pool KM versions. I updated my poor old moose to the fresh RELENG_7, and panic is still in place: r...@moose:/ar/.bad# ls -la 200807/ total 9089 drwxr-xr-x 3 rscript wheel 4 Nov 5 2008 ./ drwxr-xr-x 3 root wheel 3 Apr 12 21:33 ../ drwxr-xr-x 2 rscript wheel 36 Apr 2 22:12 daily/ -rw-r--r-- 1 rscript wheel 9207828 Aug 1 2008 total.200807 r...@moose:/ar/.bad# ls -la 200807/daily/ panic: avl_find() succeeded inside avl_add() cpuid = 1 Uptime: 1m27s Physical memory: 2039 MB Dumping 247 MB: 232 216 200 184 168 152 136 120 104 88 72 56 40 24 8 Dump complete on the dump: (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc05352e7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc05355f5 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0843b60 in avl_add (tree=Variable tree is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/common/avl/avl.c:635 #4 0xc08b0edf in zap_lockdir (os=0xc55dfa60, obj=6108, tx=0x0, lti=RW_READER, fatreader=1, adding=0, zapp=0xfc755ba0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c:335 #5 0xc08b13af in zap_cursor_retrieve (zc=0xfc755b9c, za=0xfc755a84) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c:993 #6 0xc08d6340 in zfs_freebsd_readdir (ap=0xfc755c00) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:2156 #7 0xc06de842 in VOP_READDIR_APV (vop=0xc093c560, a=0xfc755c00) at vnode_if.c:1407 #8 0xc05bf88a in kern_getdirentries (td=0xc55c0900, fd=5, buf=0x48215000 Address 0x48215000 out of bounds, count=4096, basep=0xfc755c74) at vnode_if.h:747 #9 0xc05bfab1 in getdirentries (td=0xc55c0900, uap=0xfc755cfc) at /usr/src/sys/kern/vfs_syscalls.c:3785 #10 0xc06d3588 in syscall (frame=0xfc755d38) at /usr/src/sys/i386/i386/trap.c:1090 #11 0xc06b8f40 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:255 #12 0x0033 in ?? () Previous frame inner to this frame (corrupt stack?) Any other info we need to examine this further? Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On Thursday 21 May 2009 04:32:56 am Lorenzo Perone wrote: * dancing around with loud music csupping all over the place... * I'll know I've been hacking too long when my music starts csupping all over the place.. :) Ditto though, huge thanks to Kip! JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS MFC heads up
I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. If you choose to upgrade a pool to take advantage of new features you will no longer be able to use it with sources prior to today. 'zfs send/recv' is not expected to inter-operate between different pool versions. Cheers, Kip -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
At 05:59 PM 5/20/2009, Kip Macy wrote: If you choose to upgrade a pool to take advantage of new features you will no longer be able to use it with sources prior to today. 'zfs send/recv' is not expected to inter-operate between different pool versions. Hi, Thanks for working on ZFS! Is there a summary of the new features somewhere ? ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS MFC heads up
On Wed, May 20, 2009 at 3:11 PM, Mike Tancsa m...@sentex.net wrote: At 05:59 PM 5/20/2009, Kip Macy wrote: If you choose to upgrade a pool to take advantage of new features you will no longer be able to use it with sources prior to today. 'zfs send/recv' is not expected to inter-operate between different pool versions. Hi, Thanks for working on ZFS! Is there a summary of the new features somewhere ? ---Mike Primarily what was in Pawel's commit to HEAD (see below). The following changes have also been brought in: - the recurring deadlock was fixed by deferring vinactive to a dedicated thread - zfs boot for all types now works - kmem now goes up to 512GB so arc is now limited by physmem - the arc now experiences backpressure from the vm (which can be too much - but allows ZFS to work without any tunables on amd64) Revision 185029 - (view) (annotate) - [select for diffs] Modified Mon Nov 17 20:49:29 2008 UTC (6 months ago) by pjd File length: 38244 byte(s) Diff to previous 177698 Update ZFS from version 6 to 13 and bring some FreeBSD-specific changes. This bring huge amount of changes, I'll enumerate only user-visible changes: - Delegated Administration Allows regular users to perform ZFS operations, like file system creation, snapshot creation, etc. - L2ARC Level 2 cache for ZFS - allows to use additional disks for cache. Huge performance improvements mostly for random read of mostly static content. - slog Allow to use additional disks for ZFS Intent Log to speed up operations like fsync(2). - vfs.zfs.super_owner Allows regular users to perform privileged operations on files stored on ZFS file systems owned by him. Very careful with this one. - chflags(2) Not all the flags are supported. This still needs work. - ZFSBoot Support to boot off of ZFS pool. Not finished, AFAIK. Submitted by: dfr - Snapshot properties - New failure modes Before if write requested failed, system paniced. Now one can select from one of three failure modes: - panic - panic on write error - wait - wait for disk to reappear - continue - serve read requests if possible, block write requests - Refquota, refreservation properties Just quota and reservation properties, but don't count space consumed by children file systems, clones and snapshots. - Sparse volumes ZVOLs that don't reserve space in the pool. - External attributes Compatible with extattr(2). - NFSv4-ACLs Not sure about the status, might not be complete yet. Submitted by: trasz - Creation-time properties - Regression tests for zpool(8) command. Obtained from: OpenSolaris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
