Re: [osol-discuss] PANIC! mounting cdrom slice on b78
Hi Kyle, given that what happens looks ever-so-slightly different each time, a hardware glitch could be possible; to exclude this, would you happen to know whether these panics occurred before build 78 as well ? If they occur if you use the b77 hsfs module on your post-b78 system ? Does the machine you're using have a history of hardware issues, or other symptoms that'd point at flaky hardware (such as e.g. ZFS block checksumming errors) ? There have been two changes to HSFS in b78 as far as I remember (the readahead speed improvements and the hardlink support), I wouldn't associate either with e.g. screwed vfs linkage (as two of these stacktraces show), but then, stranger regressions have occurred. Can you put the bzip2-compressed crashdumps into some accessible location so that we can have a look ? Have cc:'ed ufs-discuss, as that's often used as discussion forum for legacy filesystems. Thanks, FrankH. On Wed, 11 Jun 2008, Kyle McDonald wrote: And Again. I don't know enough about the panic dumps to say if they're the same or not, but I've been doing (slightly) different things st the time of each panic. Here's the latest dump: # mount -o ro /dev/dsk/c2t0d0s1 /mnt1 Jun 11 17:02:26 Boot ufs: NOTICE: mount: not a UFS magic number (0x6c8) mount: /dev/dsk/c2t0d0s1 is not this fstype # mount -F hsfs /dev/dsk/c2t0d0s1 /mnt1 hsfs mount: /dev/dsk/c2t0d0s1 is not an hsfs file system. # mount -o ro /dev/dsk/c2t0d0s2 /mnt1 mount: /dev/dsk/c2t0d0s2 is not this fstype # bash bash-3.2# mount -F hsfs -o ro /dev/dsk/c2t0d0s2 /mnt1 hsfs mount: /dev/dsk/c2t0d0s2 is not an hsfs file system. bash-3.2# mount -F hsfs -o ro /dev/dsk/c2t0d0s3 /mnt1 mount: /dev/dsk/c2t0d0s3 no such device bash-3.2# mount -o ro /dev/dsk/c2t0d0s3 /mnt1 mount: I/O error mount: Cannot mount /dev/dsk/c2t0d0s3 bash-3.2# mount -o ro /dev/dsk/c2t0d0s4 /mnt1 mount: I/O error mount: Cannot mount /dev/dsk/c2t0d0s4 bash-3.2# mount -f hsfs -o ro /dev/dsk/c2t0d0s4 /mnt1 mount: /dev/dsk/c2t0d0s4 no such device bash-3.2# mount -f hsfs -o ro /dev/dsk/c2t0d0s5 /mnt1 panic[cpu2]/thread=ff02d573d760: BAD TRAP: type=e (#pf Page fault) rp=ff001047d9b0 addr=40 occurred in module genunix due to a NULL pointer dereference mount: #pf Page fault Bad kernel fault at addr=0x40 pid=1172, pc=0xfba81ac3, sp=0xff001047daa0, eflags=0x10207 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: 40cr3: 22cbb9000cr8: c rdi: fbca24e0 rsi:1 rdx:8 rcx:4 r8: fbca26b0 r9:0 rax:0 rbx:0 rbp: ff001047dac0 r10: 270005 r11: 2c r12: 270005 r13: 270005 r14: ff001047db08 r15:0 fsb:0 gsb: ff02d50aaac0 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: fba81ac3 cs: 30 rfl:10207 rsp: ff001047daa0 ss: 38 ff001047d890 unix:die+c8 () ff001047d9a0 unix:trap+13b1 () ff001047d9b0 unix:cmntrap+e9 () ff001047dac0 genunix:vfs_devismounted+23 () ff001047dbd0 hsfs:hs_getmdev+12b () ff001047dc70 hsfs:hsfs_mount+195 () ff001047dca0 genunix:fsop_mount+21 () ff001047de00 genunix:domount+8fa () ff001047de80 genunix:mount+d2 () ff001047dec0 genunix:syscall_ap+8f () ff001047df10 unix:brand_sys_sysenter+1e6 () syncing file systems... done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 260327 pages dumped, compression ratio 5.74, dump succeeded rebooting... -Kyle Kyle McDonald wrote: It happenned again. Only this time it happenned when I started 'bash' (after failing[no such device] to mount s7 of the same CD.) Here's the panic this time: # mount -F hsfs -o ro /dev/dsk/c2t0d0s7 /mnt mount: /dev/dsk/c2t0d0s7 no such device # bash panic[cpu0]/thread=ff02d58d46e0: BAD TRAP: type=e (#pf Page fault) rp=ff00104e7db0 addr=a occurred in module unknown due to a NULL pointer dereference sh: #pf Page fault Bad kernel fault at addr=0xa pid=1199, pc=0xa, sp=0xff00104e7ea0, eflags=0x10246 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: acr3: 22fd88000cr8: c rdi: ff02d46a9400 rsi: ff030240d040 rdx: ff02d58d46e0 rcx:3 r8: ff02faddc628 r9: ff02faa16708 rax:e rbx: fbc77b90 rbp: ff02d4f7f048 r10: ff02d560c008 r11:0 r12: 4af r13: 2eb r14: ff02d59171f0 r15: ff02d58d46e0 fsb:0 gsb: fbc26770 ds: 4b es: 4b fs:0 gs:
Re: [osol-discuss] PANIC! mounting cdrom slice on b78
[EMAIL PROTECTED] wrote: There have been two changes to HSFS in b78 as far as I remember (the readahead speed improvements and the hardlink support), I wouldn't associate either with e.g. screwed vfs linkage (as two of these stacktraces show), but then, stranger regressions have occurred. Can you put the bzip2-compressed crashdumps into some accessible location so that we can have a look ? Have cc:'ed ufs-discuss, as that's often used as discussion forum for legacy filesystems. I would like to see the output of isoinfo -i /dev/dsk/c2t0d0s2 -d Thanks, FrankH. On Wed, 11 Jun 2008, Kyle McDonald wrote: And Again. I don't know enough about the panic dumps to say if they're the same or not, but I've been doing (slightly) different things st the time of each panic. Here's the latest dump: # mount -o ro /dev/dsk/c2t0d0s1 /mnt1 Jun 11 17:02:26 Boot ufs: NOTICE: mount: not a UFS magic number (0x6c8) mount: /dev/dsk/c2t0d0s1 is not this fstype # mount -F hsfs /dev/dsk/c2t0d0s1 /mnt1 hsfs mount: /dev/dsk/c2t0d0s1 is not an hsfs file system. # mount -o ro /dev/dsk/c2t0d0s2 /mnt1 mount: /dev/dsk/c2t0d0s2 is not this fstype # bash bash-3.2# mount -F hsfs -o ro /dev/dsk/c2t0d0s2 /mnt1 hsfs mount: /dev/dsk/c2t0d0s2 is not an hsfs file system. bash-3.2# mount -F hsfs -o ro /dev/dsk/c2t0d0s3 /mnt1 mount: /dev/dsk/c2t0d0s3 no such device bash-3.2# mount -o ro /dev/dsk/c2t0d0s3 /mnt1 mount: I/O error mount: Cannot mount /dev/dsk/c2t0d0s3 bash-3.2# mount -o ro /dev/dsk/c2t0d0s4 /mnt1 mount: I/O error mount: Cannot mount /dev/dsk/c2t0d0s4 bash-3.2# mount -f hsfs -o ro /dev/dsk/c2t0d0s4 /mnt1 mount: /dev/dsk/c2t0d0s4 no such device bash-3.2# mount -f hsfs -o ro /dev/dsk/c2t0d0s5 /mnt1 panic[cpu2]/thread=ff02d573d760: BAD TRAP: type=e (#pf Page fault) rp=ff001047d9b0 addr=40 occurred in module genunix due to a NULL pointer dereference mount: #pf Page fault Bad kernel fault at addr=0x40 pid=1172, pc=0xfba81ac3, sp=0xff001047daa0, eflags=0x10207 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: 40cr3: 22cbb9000cr8: c rdi: fbca24e0 rsi:1 rdx:8 rcx:4 r8: fbca26b0 r9:0 rax:0 rbx:0 rbp: ff001047dac0 r10: 270005 r11: 2c r12: 270005 r13: 270005 r14: ff001047db08 r15:0 fsb:0 gsb: ff02d50aaac0 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: fba81ac3 cs: 30 rfl:10207 rsp: ff001047daa0 ss: 38 ff001047d890 unix:die+c8 () ff001047d9a0 unix:trap+13b1 () ff001047d9b0 unix:cmntrap+e9 () ff001047dac0 genunix:vfs_devismounted+23 () ff001047dbd0 hsfs:hs_getmdev+12b () ff001047dc70 hsfs:hsfs_mount+195 () ff001047dca0 genunix:fsop_mount+21 () ff001047de00 genunix:domount+8fa () ff001047de80 genunix:mount+d2 () ff001047dec0 genunix:syscall_ap+8f () ff001047df10 unix:brand_sys_sysenter+1e6 () syncing file systems... done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 260327 pages dumped, compression ratio 5.74, dump succeeded rebooting... The panic did not directly happen in hsfs ;-) We did add a lot of checks against into hsfs but not everything can be 100% secure. but hs_getmdev() does not access the medium, it just do some kernel consistency checks. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] PANIC! mounting cdrom slice on b78
I have sNV b78 installed (I know I'm working on upgrading to b90.) Is that an official snv_78 build, or did you compile that from onnv-gate mercurial sources (post snv_77)? I was attempting to mount /dev/dsk/c2t0d0s4, which is an ATAPI DVDROM drive containing S10 03/05 CD1, and the machine panic'd when I did 'mount -F hsfs -o ro /dev/dsk/c2t0d0s4' Hmm, there had been some kernel heap corruption problems with hsfs around snv_75 / snv_77. That was bug 6621609, and is supposed to be fixed in snv_78. Can you try to add the following line to /etc/system, reboot, and retry to reproduce the hsfs mount panic? set kmem_flags=0xf (This enables kernel heap checking) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] PANIC! mounting cdrom slice on b78
Hi All, I have sNV b78 installed (I know I'm working on upgrading to b90.) I was attempting to mount /dev/dsk/c2t0d0s4, which is an ATAPI DVDROM drive containing S10 03/05 CD1, and the machine panic'd when I did 'mount -F hsfs -o ro /dev/dsk/c2t0d0s4' Here's what came up on the console... I can try to get the core also if needed. panic[cpu0]/thread=ff02d5810140: BAD TRAP: type=e (#pf Page fault) rp=ff0010896a20 addr=20 occurred in module mntfs due to a NULL pointer dereference hald: #pf Page fault Bad kernel fault at addr=0x20 pid=700, pc=0xf78da280, sp=0xff0010896b10, eflags=0x10246 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: 20cr3: 22fd88000cr8: c rdi:0 rsi:a rdx:a rcx:0 r8: 60 r9: 3a rax: 60 rbx: 42 rbp: ff0010896b50 r10:b r11: ff001089691d r12: 18ba r13:0 r14:0 r15: ff04b36e3da8 fsb:0 gsb: fbc26770 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: f78da280 cs: 30 rfl:10246 rsp: ff0010896b10 ss: 38 ff0010896900 unix:die+c8 () ff0010896a10 unix:trap+13b1 () ff0010896a20 unix:cmntrap+e9 () ff0010896b50 mntfs:mntfs_global_len+30 () ff0010896be0 mntfs:mntfs_snapshot+111 () ff0010896d30 mntfs:mntioctl+31c () ff0010896db0 genunix:fop_ioctl+7b () ff0010896ec0 genunix:ioctl+174 () ff0010896f10 unix:brand_sys_sysenter+1e6 () syncing file systems... 2 done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 311409 pages dumped, compression ratio 4.14, dump succeeded rebooting... If there's a better email list to post this to, please let me know. Or if this is a known issue, is it fixed in b90? -Kyle ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] PANIC! mounting cdrom slice on b78
It happenned again. Only this time it happenned when I started 'bash' (after failing[no such device] to mount s7 of the same CD.) Here's the panic this time: # mount -F hsfs -o ro /dev/dsk/c2t0d0s7 /mnt mount: /dev/dsk/c2t0d0s7 no such device # bash panic[cpu0]/thread=ff02d58d46e0: BAD TRAP: type=e (#pf Page fault) rp=ff00104e7db0 addr=a occurred in module unknown due to a NULL pointer dereference sh: #pf Page fault Bad kernel fault at addr=0xa pid=1199, pc=0xa, sp=0xff00104e7ea0, eflags=0x10246 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: acr3: 22fd88000cr8: c rdi: ff02d46a9400 rsi: ff030240d040 rdx: ff02d58d46e0 rcx:3 r8: ff02faddc628 r9: ff02faa16708 rax:e rbx: fbc77b90 rbp: ff02d4f7f048 r10: ff02d560c008 r11:0 r12: 4af r13: 2eb r14: ff02d59171f0 r15: ff02d58d46e0 fsb:0 gsb: fbc26770 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip:a cs: 30 rfl:10246 rsp: ff00104e7ea0 ss: 38 ff00104e7c90 unix:die+c8 () ff00104e7da0 unix:trap+13b1 () ff00104e7db0 unix:cmntrap+e9 () warning! 8-byte aligned %fp = ff02d4f7f048 ff02d4f7f048 a () syncing file systems... done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 272320 pages dumped, compression ratio 5.20, dump succeeded rebooting... Is this machine suffering a Hardware failure? or is this a bug? (It could be a bad CD I suppose, but I'd think it was a bug if a bad CD can panic the system.) -Kyle Kyle McDonald wrote: Hi All, I have sNV b78 installed (I know I'm working on upgrading to b90.) I was attempting to mount /dev/dsk/c2t0d0s4, which is an ATAPI DVDROM drive containing S10 03/05 CD1, and the machine panic'd when I did 'mount -F hsfs -o ro /dev/dsk/c2t0d0s4' Here's what came up on the console... I can try to get the core also if needed. panic[cpu0]/thread=ff02d5810140: BAD TRAP: type=e (#pf Page fault) rp=ff0010896a20 addr=20 occurred in module mntfs due to a NULL pointer dereference hald: #pf Page fault Bad kernel fault at addr=0x20 pid=700, pc=0xf78da280, sp=0xff0010896b10, eflags=0x10246 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: 20cr3: 22fd88000cr8: c rdi:0 rsi:a rdx:a rcx:0 r8: 60 r9: 3a rax: 60 rbx: 42 rbp: ff0010896b50 r10:b r11: ff001089691d r12: 18ba r13:0 r14:0 r15: ff04b36e3da8 fsb:0 gsb: fbc26770 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: f78da280 cs: 30 rfl:10246 rsp: ff0010896b10 ss: 38 ff0010896900 unix:die+c8 () ff0010896a10 unix:trap+13b1 () ff0010896a20 unix:cmntrap+e9 () ff0010896b50 mntfs:mntfs_global_len+30 () ff0010896be0 mntfs:mntfs_snapshot+111 () ff0010896d30 mntfs:mntioctl+31c () ff0010896db0 genunix:fop_ioctl+7b () ff0010896ec0 genunix:ioctl+174 () ff0010896f10 unix:brand_sys_sysenter+1e6 () syncing file systems... 2 done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 311409 pages dumped, compression ratio 4.14, dump succeeded rebooting... If there's a better email list to post this to, please let me know. Or if this is a known issue, is it fixed in b90? -Kyle ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] PANIC! mounting cdrom slice on b78
And Again. I don't know enough about the panic dumps to say if they're the same or not, but I've been doing (slightly) different things st the time of each panic. Here's the latest dump: # mount -o ro /dev/dsk/c2t0d0s1 /mnt1 Jun 11 17:02:26 Boot ufs: NOTICE: mount: not a UFS magic number (0x6c8) mount: /dev/dsk/c2t0d0s1 is not this fstype # mount -F hsfs /dev/dsk/c2t0d0s1 /mnt1 hsfs mount: /dev/dsk/c2t0d0s1 is not an hsfs file system. # mount -o ro /dev/dsk/c2t0d0s2 /mnt1 mount: /dev/dsk/c2t0d0s2 is not this fstype # bash bash-3.2# mount -F hsfs -o ro /dev/dsk/c2t0d0s2 /mnt1 hsfs mount: /dev/dsk/c2t0d0s2 is not an hsfs file system. bash-3.2# mount -F hsfs -o ro /dev/dsk/c2t0d0s3 /mnt1 mount: /dev/dsk/c2t0d0s3 no such device bash-3.2# mount -o ro /dev/dsk/c2t0d0s3 /mnt1 mount: I/O error mount: Cannot mount /dev/dsk/c2t0d0s3 bash-3.2# mount -o ro /dev/dsk/c2t0d0s4 /mnt1 mount: I/O error mount: Cannot mount /dev/dsk/c2t0d0s4 bash-3.2# mount -f hsfs -o ro /dev/dsk/c2t0d0s4 /mnt1 mount: /dev/dsk/c2t0d0s4 no such device bash-3.2# mount -f hsfs -o ro /dev/dsk/c2t0d0s5 /mnt1 panic[cpu2]/thread=ff02d573d760: BAD TRAP: type=e (#pf Page fault) rp=ff001047d9b0 addr=40 occurred in module genunix due to a NULL pointer dereference mount: #pf Page fault Bad kernel fault at addr=0x40 pid=1172, pc=0xfba81ac3, sp=0xff001047daa0, eflags=0x10207 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: 40cr3: 22cbb9000cr8: c rdi: fbca24e0 rsi:1 rdx:8 rcx:4 r8: fbca26b0 r9:0 rax:0 rbx:0 rbp: ff001047dac0 r10: 270005 r11: 2c r12: 270005 r13: 270005 r14: ff001047db08 r15:0 fsb:0 gsb: ff02d50aaac0 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: fba81ac3 cs: 30 rfl:10207 rsp: ff001047daa0 ss: 38 ff001047d890 unix:die+c8 () ff001047d9a0 unix:trap+13b1 () ff001047d9b0 unix:cmntrap+e9 () ff001047dac0 genunix:vfs_devismounted+23 () ff001047dbd0 hsfs:hs_getmdev+12b () ff001047dc70 hsfs:hsfs_mount+195 () ff001047dca0 genunix:fsop_mount+21 () ff001047de00 genunix:domount+8fa () ff001047de80 genunix:mount+d2 () ff001047dec0 genunix:syscall_ap+8f () ff001047df10 unix:brand_sys_sysenter+1e6 () syncing file systems... done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 260327 pages dumped, compression ratio 5.74, dump succeeded rebooting... -Kyle Kyle McDonald wrote: It happenned again. Only this time it happenned when I started 'bash' (after failing[no such device] to mount s7 of the same CD.) Here's the panic this time: # mount -F hsfs -o ro /dev/dsk/c2t0d0s7 /mnt mount: /dev/dsk/c2t0d0s7 no such device # bash panic[cpu0]/thread=ff02d58d46e0: BAD TRAP: type=e (#pf Page fault) rp=ff00104e7db0 addr=a occurred in module unknown due to a NULL pointer dereference sh: #pf Page fault Bad kernel fault at addr=0xa pid=1199, pc=0xa, sp=0xff00104e7ea0, eflags=0x10246 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f8xmme,fxsr,pge,mce,pae,pse,de cr2: acr3: 22fd88000cr8: c rdi: ff02d46a9400 rsi: ff030240d040 rdx: ff02d58d46e0 rcx:3 r8: ff02faddc628 r9: ff02faa16708 rax:e rbx: fbc77b90 rbp: ff02d4f7f048 r10: ff02d560c008 r11:0 r12: 4af r13: 2eb r14: ff02d59171f0 r15: ff02d58d46e0 fsb:0 gsb: fbc26770 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip:a cs: 30 rfl:10246 rsp: ff00104e7ea0 ss: 38 ff00104e7c90 unix:die+c8 () ff00104e7da0 unix:trap+13b1 () ff00104e7db0 unix:cmntrap+e9 () warning! 8-byte aligned %fp = ff02d4f7f048 ff02d4f7f048 a () syncing file systems... done dumping to /dev/dsk/c1t0d0s3, offset 431030272, content: kernel 100% done: 272320 pages dumped, compression ratio 5.20, dump succeeded rebooting... Is this machine suffering a Hardware failure? or is this a bug? (It could be a bad CD I suppose, but I'd think it was a bug if a bad CD can panic the system.) -Kyle Kyle McDonald wrote: Hi All, I have sNV b78 installed (I know I'm working on upgrading to b90.) I was attempting to mount /dev/dsk/c2t0d0s4, which is an ATAPI DVDROM drive containing S10 03/05 CD1, and the machine panic'd when I did 'mount -F hsfs -o ro /dev/dsk/c2t0d0s4'
