Re: vnd and softraid panic
On Wed, 30 Jan 2013, Eivind Evensen wrote: On Wed, Jan 23, 2013 at 02:33:16AM +1100, Joel Sing wrote: On Thu, 3 Jan 2013, Eivind Evensen wrote: On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... FWIW this should now be rectified in -current. I tried a snapshot downloaded on 21.th (OpenBSD 5.2-current (GENERIC) #17: Fri Jan 18 19:42:57 MST 2013) which produced the same results. I waited a few days in case the snapshot was too old and built from sources from yesterday, still giving the same results. I don't need such a setup so it's not a big deal, but here's output and dmesg in case it may be helpful: Thanks for the report. For some reason I thought you had tried using softraid crypto on a vnd and overlooked the fact that you were trying to use RAID 5 (and now RAID 1). To clarify, RAID 0, CONCAT and CRYPTO should all now work on top of a vnd - RAID 1, RAID 4 and RAID 5 will still break in the manner given below (panic related to active workunits). These disciplines require the same changes that I've made to the other three, however they're a little more complex and time consuming. I'll try to get to them fixed soon. root:skoeske dd if=/dev/zero of=disk1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.875 secs (36462177 bytes/sec) root:skoeske r disk1=disk2 dd if=/dev/zero of=disk2 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.219 secs (32567739 bytes/sec) root:skoeske r disk2=disk3 dd if=/dev/zero of=disk3 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.569 secs (29378164 bytes/sec) root:skoeske vnconfig vnd0 disk1 root:skoeske vnconfig vnd1 disk2 root:skoeske vnconfig vnd2 disk3 root:skoeske fdisk -iy vnd0 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd1 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd2 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd0 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd1 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd2 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske bioctl -c 1 -l /dev/vnd0a,/dev/vnd1a,/dev/vnd2a softraid0 sd0 at scsibus1 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd0: 99MB, 512 bytes/sector, 204144 sectors softraid0: SR RAID 1 volume attached as sd0 panic: softraid0: sr_wu_init got active wu Stopped at Debugger+0x4: popl%ebp RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger(d08fcddc,f2087de8,d08d0da4,f2087de8,d0a7e540) at Debugger+0x4 panic(d08d0da4,d0f8c014,f2087dfc,d036ccf3,d0fedab8) at panic+0x5d sr_wu_init(d1055000,d0fedab8,f2087e3c,d1055a30,d1057f00) at sr_wu_init+0x73 sr_wu_put(d1055000,d0fedab8,f2087e3c,f2087e3c,d02030dd) at sr_wu_put+0x2f scsi_io_put(d1055a30,d0fedab8,8000,d0fedab8,d0fedab8) at scsi_io_put+0x19 scsi_xs_put(f2027000,f2027000,f2087e8c,d041de18,d1055000) at scsi_xs_put+0x37 sr_raid1_intr(d1065000,f1fabdc4,f17dc000,200,52000) at sr_raid1_intr+0x107 vndstrategy(d1065000,0,0,50,d1065000) at vndstrategy+0x70 spec_strategy(f2087f48,0,f2087f6c,d03f2c28,d1053d90) at spec_strategy+0x3d VOP_STRATEGY(d1065000,0,0,0,d0fedaf8) at VOP_STRATEGY+0x2c sr_startwu_callback(d1055000,d0fedab8,d02008bf,d1053d80,d03f2c50) at sr_startwu _callback+0x39 workq_thread(d1053d80) at workq_thread+0x36 Bad frame pointer: 0xd0bc8ed8 ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND *23369 0 0 0 70x100200srdis 19292 1571 6315 1000 30x80 ttyin less 1571 6315 6315 1000 30x88 pause sh 6315 30722 6315 1000 30x80 wait man 30722 11048 30722 1000 30x88 pause ksh 11048 2130 2130 1000 30x80 selectsshd 2130 1703 2130 0 30x80 poll sshd 2513 1 2513 0 20x80ksh 20983 1 20983 0 30x80 ttyin
Re: vnd and softraid panic
On Thu, Jan 31, 2013 at 12:20:14AM +1100, Joel Sing wrote: On Wed, 30 Jan 2013, Eivind Evensen wrote: On Wed, Jan 23, 2013 at 02:33:16AM +1100, Joel Sing wrote: On Thu, 3 Jan 2013, Eivind Evensen wrote: On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... FWIW this should now be rectified in -current. I tried a snapshot downloaded on 21.th (OpenBSD 5.2-current (GENERIC) #17: Fri Jan 18 19:42:57 MST 2013) which produced the same results. I waited a few days in case the snapshot was too old and built from sources from yesterday, still giving the same results. I don't need such a setup so it's not a big deal, but here's output and dmesg in case it may be helpful: Thanks for the report. For some reason I thought you had tried using softraid crypto on a vnd and overlooked the fact that you were trying to use RAID 5 (and now RAID 1). To clarify, RAID 0, CONCAT and CRYPTO should all now work on top of a vnd - RAID 1, RAID 4 and RAID 5 will still break in the manner given below (panic related to active workunits). These disciplines require the same changes that I've made to the other three, however they're a little more complex and time consuming. I'll try to get to them fixed soon. I see, thanks for the explanation. Eivind.
Re: vnd and softraid panic
On Wed, Jan 23, 2013 at 02:33:16AM +1100, Joel Sing wrote: On Thu, 3 Jan 2013, Eivind Evensen wrote: On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... FWIW this should now be rectified in -current. I tried a snapshot downloaded on 21.th (OpenBSD 5.2-current (GENERIC) #17: Fri Jan 18 19:42:57 MST 2013) which produced the same results. I waited a few days in case the snapshot was too old and built from sources from yesterday, still giving the same results. I don't need such a setup so it's not a big deal, but here's output and dmesg in case it may be helpful: root:skoeske dd if=/dev/zero of=disk1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.875 secs (36462177 bytes/sec) root:skoeske r disk1=disk2 dd if=/dev/zero of=disk2 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.219 secs (32567739 bytes/sec) root:skoeske r disk2=disk3 dd if=/dev/zero of=disk3 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.569 secs (29378164 bytes/sec) root:skoeske vnconfig vnd0 disk1 root:skoeske vnconfig vnd1 disk2 root:skoeske vnconfig vnd2 disk3 root:skoeske fdisk -iy vnd0 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd1 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd2 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd0 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd1 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd2 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske bioctl -c 1 -l /dev/vnd0a,/dev/vnd1a,/dev/vnd2a softraid0 sd0 at scsibus1 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd0: 99MB, 512 bytes/sector, 204144 sectors softraid0: SR RAID 1 volume attached as sd0 panic: softraid0: sr_wu_init got active wu Stopped at Debugger+0x4: popl%ebp RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger(d08fcddc,f2087de8,d08d0da4,f2087de8,d0a7e540) at Debugger+0x4 panic(d08d0da4,d0f8c014,f2087dfc,d036ccf3,d0fedab8) at panic+0x5d sr_wu_init(d1055000,d0fedab8,f2087e3c,d1055a30,d1057f00) at sr_wu_init+0x73 sr_wu_put(d1055000,d0fedab8,f2087e3c,f2087e3c,d02030dd) at sr_wu_put+0x2f scsi_io_put(d1055a30,d0fedab8,8000,d0fedab8,d0fedab8) at scsi_io_put+0x19 scsi_xs_put(f2027000,f2027000,f2087e8c,d041de18,d1055000) at scsi_xs_put+0x37 sr_raid1_intr(d1065000,f1fabdc4,f17dc000,200,52000) at sr_raid1_intr+0x107 vndstrategy(d1065000,0,0,50,d1065000) at vndstrategy+0x70 spec_strategy(f2087f48,0,f2087f6c,d03f2c28,d1053d90) at spec_strategy+0x3d VOP_STRATEGY(d1065000,0,0,0,d0fedaf8) at VOP_STRATEGY+0x2c sr_startwu_callback(d1055000,d0fedab8,d02008bf,d1053d80,d03f2c50) at sr_startwu _callback+0x39 workq_thread(d1053d80) at workq_thread+0x36 Bad frame pointer: 0xd0bc8ed8 ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND *23369 0 0 0 70x100200srdis 19292 1571 6315 1000 30x80 ttyin less 1571 6315 6315 1000 30x88 pause sh 6315 30722 6315 1000 30x80 wait man 30722 11048 30722 1000 30x88 pause ksh 11048 2130 2130 1000 30x80 selectsshd 2130 1703 2130 0 30x80 poll sshd 2513 1 2513 0 20x80ksh 20983 1 20983 0 30x80 ttyin getty 22576 1 22576 0 30x80 ttyin getty 19748 1 19748 0 30x80 ttyin getty 21880 1 21880 0 30x80 ttyin getty 5243 1 5243 0 30x80 ttyin getty 32690 1 32690 0 30x80 selectcron 24485 1 24485 99 30x80 poll sndiod 99 1 99 0 30x80 selectinetd 22458 15830 15830 95 30x80 kqreadsmtpd 17649 15830 15830 95 30x80 kqreadsmtpd 17949 15830 15830 95 30x80 kqreadsmtpd 3934
Re: vnd and softraid panic
On Thu, 3 Jan 2013, Eivind Evensen wrote: On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... ddb trace Debugger(d08fa43c,f2017e08,d08ce53b,f2017e08,0) at Debugger+0x4 panic(d08ce53b,d0f8a014,f2017e3c,d105fa30,d105ce00) at panic+0x5d sr_wu_put(d105f000,d0ff12b8,f2017e3c,f2017e3c,d02030dd) at sr_wu_put+0x104 scsi_io_put(d105fa30,d0ff12b8,8000,d1068000,d1068000) at scsi_io_put+0x19 scsi_xs_put(f1f4d000,d1068000,f2017e8c,d0418d98,f1f4d000) at scsi_xs_put+0x37 sr_raidp_intr(d1068000,f1e8601c,f11ec000,200,52000) at sr_raidp_intr+0x15b vndstrategy(d1068000,0,0,50,d1068000) at vndstrategy+0x70 spec_strategy(f2017f48,0,f2017f6c,d03ee028,d1053f50) at spec_strategy+0x3d VOP_STRATEGY(d1068000,0,0,0,d0ff12f8) at VOP_STRATEGY+0x2c sr_startwu_callback(d105f000,d0ff12b8,d02008bf,d1053f40,d03ee050) at sr_startwu _callback+0x39 workq_thread(d1053f40) at workq_thread+0x36 Bad frame pointer: 0xd0bc6ed8 Thanks - it is a known issue, which I hope to be able to finish addressing during the next hackathon. Nice to know. If it helps, I can test patches. FWIW this should now be rectified in -current. -- Reason is not automatic. Those who deny it cannot be conquered by it. Do not count on them. Leave them alone. -- Ayn Rand
Re: vnd and softraid panic
On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... ddb trace Debugger(d08fa43c,f2017e08,d08ce53b,f2017e08,0) at Debugger+0x4 panic(d08ce53b,d0f8a014,f2017e3c,d105fa30,d105ce00) at panic+0x5d sr_wu_put(d105f000,d0ff12b8,f2017e3c,f2017e3c,d02030dd) at sr_wu_put+0x104 scsi_io_put(d105fa30,d0ff12b8,8000,d1068000,d1068000) at scsi_io_put+0x19 scsi_xs_put(f1f4d000,d1068000,f2017e8c,d0418d98,f1f4d000) at scsi_xs_put+0x37 sr_raidp_intr(d1068000,f1e8601c,f11ec000,200,52000) at sr_raidp_intr+0x15b vndstrategy(d1068000,0,0,50,d1068000) at vndstrategy+0x70 spec_strategy(f2017f48,0,f2017f6c,d03ee028,d1053f50) at spec_strategy+0x3d VOP_STRATEGY(d1068000,0,0,0,d0ff12f8) at VOP_STRATEGY+0x2c sr_startwu_callback(d105f000,d0ff12b8,d02008bf,d1053f40,d03ee050) at sr_startwu _callback+0x39 workq_thread(d1053f40) at workq_thread+0x36 Bad frame pointer: 0xd0bc6ed8 Thanks - it is a known issue, which I hope to be able to finish addressing during the next hackathon. Nice to know. If it helps, I can test patches. Regards, Eivind
Re: vnd and softraid panic
On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. While the combination of vnd and softraid may not be useful for any real purpose, I noticed this while hoping to be able to fail a disk in a somewhat simpler to retry manner than the nailgun approach I read about here recently... I don't know if it's important, but also after the trace and ps listed below, boot reboot won't reboot the first time, but I can enter ddb again by sending a serial break and then get the machine to reboot by reexecuting the boot reboot command. Regards, Eivind root:skoeske dd if=/dev/zero of=disk1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.852 secs (27215650 bytes/sec) root:skoeske r disk1=disk2 dd if=/dev/zero of=disk2 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.569 secs (40802861 bytes/sec) root:skoeske r disk2=disk3 dd if=/dev/zero of=disk3 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.750 secs (27957919 bytes/sec) root:skoeske vnconfig vnd0 disk1 root:skoeske vnconfig vnd1 disk2 root:skoeske vnconfig vnd2 disk3 root:skoeske fdisk -iy vnd0 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd1 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd2 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd0 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd1 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd2 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske bioctl -c 5 -l /dev/vnd0a,/dev/vnd1a,/dev/vnd2a softraid0 sd0 at scsibus1 targ 1 lun 0: OPENBSD, SR RAID 5, 005 SCSI2 0/direct fixed sd0: 199MB, 512 bytes/sector, 408064 sectors softraid0: SR RAID 5 volume attached as sd0 panic: softraid0: sr_wu_put got active wu Stopped at Debugger+0x4: popl%ebp RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger(d08fa43c,f2017e08,d08ce53b,f2017e08,0) at Debugger+0x4 panic(d08ce53b,d0f8a014,f2017e3c,d105fa30,d105ce00) at panic+0x5d sr_wu_put(d105f000,d0ff12b8,f2017e3c,f2017e3c,d02030dd) at sr_wu_put+0x104 scsi_io_put(d105fa30,d0ff12b8,8000,d1068000,d1068000) at scsi_io_put+0x19 scsi_xs_put(f1f4d000,d1068000,f2017e8c,d0418d98,f1f4d000) at scsi_xs_put+0x37 sr_raidp_intr(d1068000,f1e8601c,f11ec000,200,52000) at sr_raidp_intr+0x15b vndstrategy(d1068000,0,0,50,d1068000) at vndstrategy+0x70 spec_strategy(f2017f48,0,f2017f6c,d03ee028,d1053f50) at spec_strategy+0x3d VOP_STRATEGY(d1068000,0,0,0,d0ff12f8) at VOP_STRATEGY+0x2c sr_startwu_callback(d105f000,d0ff12b8,d02008bf,d1053f40,d03ee050) at sr_startwu _callback+0x39 workq_thread(d1053f40) at workq_thread+0x36 Bad frame pointer: 0xd0bc6ed8 Thanks - it is a known issue, which I hope to be able to finish addressing during the next hackathon. ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND * 4458 0 0 0 70x100200srdis 9614 9263 31326 1000 30x80 ttyin less 9263 31326 31326 1000 30x88 pause sh 31326 8662 31326 1000 30x80 wait man 8662 24219 8662 1000 30x88 pause ksh 24219 7388 7388 1000 30x80 selectsshd 7388 1358 7388 0 30x80 poll sshd 8332 1 8332 0 20x80ksh 21947 1 21947 0 30x80 ttyin getty 28840 1 28840 0 30x80 ttyin getty 32669 1 32669 0 30x80 ttyin getty 25686 1 25686 0 30x80 ttyin getty 19769 1 19769 0 30x80 ttyin getty 10627 1 10627 0 30x80 selectcron 14888 1 14888 99 30x80 poll sndiod 5483 1 5483 0 30x80 selectinetd 27714 10979 10979 95 30x80 kqreadsmtpd 9877 10979 10979 95 30x80 kqreadsmtpd 31352 10979 10979 95 30x80 kqreadsmtpd 17499
