Re: VOP_STRATEGY on VCHR
In message [EMAIL PROTECTED], Enache Adrian writes: I get this when I try to access for the first time a file on an ext2fs filesystem. VOP_STRATEGY on VCHR Please try this patch and let me know if it helps ? Index: ext2_vnops.c === RCS file: /home/ncvs/src/sys/gnu/ext2fs/ext2_vnops.c,v retrieving revision 1.75 diff -u -r1.75 ext2_vnops.c --- ext2_vnops.c4 Jan 2003 08:47:19 - 1.75 +++ ext2_vnops.c28 Jan 2003 08:37:50 - @@ -1528,7 +1528,7 @@ } vp = ip-i_devvp; bp-b_dev = vp-v_rdev; - VOP_STRATEGY(vp, bp); + VOP_SPECSTRATEGY(vp, bp); return (0); } -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_STRATEGY on VCHR
On Tue, Jan 28, 2003 at 09:38:19AM +0100, [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Enache Adrian writes: I get this when I try to access for the first time a file on an ext2fs filesystem. VOP_STRATEGY on VCHR Please try this patch and let me know if it helps ? Of course, it fixes it. Thanks Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VOP_STRATEGY on VCHR
I get this when I try to access for the first time a file on an ext2fs filesystem. VOP_STRATEGY on VCHR : 0xc1c23000: tag devfs, type VCHR, usecount 2, writecount 0, refcount 3, backtrace(c02fe7bd,c1c23000,0,c87eb938,c0166ed8) at backtrace+0x8 spec_strategy(c87eb960,c87eb97c,c1c4163b,c87eb960,0) at spec_strategy+0x2d spec_vnoperate(c87eb960,0,c87eb95c,0,0) at spec_vnoperate+0x18 ext2_strategy(c87eb9c8,0,0,1000,0) at ext2_strategy+0x8b breadn(c1c22e6c,0,0,1000,0) at breadn+0x126 bread(c1c22e6c,0,0,1000,0) at bread+0x4c ext2_read(c87ebaf0,c0328a20,0,0,0) at ext2_read+0x293 ext2_readdir(c87ebc98,20002,c0b9a1e0,0,c1c22e6c) at ext2_readdir+0x130 getdirentries(c0b9a1e0,c87ebd14,c03195a7,407,4) at getdirentries+0x128 syscall(2f,2f,2f,80d1000,80d1040) at syscall+0x271 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (196), eip = 0x808cf1f, esp = 0xbfbff1bc, ebp = 0xbfbff1d8 --- Is that anything serious or just noise ? (this is -CURRENT from yesterday) Regards Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_STRATEGY on VCHR?
On Sat, Jan 04, 2003 at 10:48:15PM -0800, walt wrote: After updating world and kernel this evening I saw this message fly by during the reboot: Mounting root from ufs:/dev/ad0s3a VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), Sorry, need DDB option to print backtrace That feels like an error message (sort of) but everything seems to be working normally. Is this a real problem or just noise? See phk's recent commit. Kris msg49688/pgp0.pgp Description: PGP signature
Re: VOP_STRATEGY on VCHR?
In message [EMAIL PROTECTED], walt writes: After updating world and kernel this evening I saw this message fly by during the reboot: Mounting root from ufs:/dev/ad0s3a VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), Sorry, need DDB option to print backtrace That feels like an error message (sort of) but everything seems to be working normally. Is this a real problem or just noise? Well, to you it's just noise, to me it's a real problem :-) It is probably the same problem as the one I just commited a fix for. If you get this again after upgrading, please put the DDB option in your kernel and see if you can reproduce it so I get a traceback. The vnode information alone seems not quite as useful as I had hoped. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_STRATEGY on VCHR?
On Sun, 5 Jan 2003 [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], walt writes: After updating world and kernel this evening I saw this message fly by during the reboot: Mounting root from ufs:/dev/ad0s3a VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), I get this too (except I fixed the misformatting of the message while reviewing the code, so that it is printed on 1 line with a non-bogus :). From /var/log/messages: % Jan 5 21:09:22 gamplex kernel: VOP_STRATEGY on VCHR: 0xc2697000: tag none, type VCHR, usecount 4, writecount 0, refcount 4, flags (VV_OBJBUF), % Jan 5 21:18:37 gamplex kernel: VOP_STRATEGY on VCHR: 0xc2697000: tag none, type VCHR, usecount 4, writecount 0, refcount 4, flags (VV_OBJBUF), (This shows a formatting bug in vprint() itself: the , at the end.) Sorry, need DDB option to print backtrace I have the DDB option, so I don't get this. It is probably the same problem as the one I just commited a fix for. I haven't cvsupped' the fix or debugged it yet. If you get this again after upgrading, please put the DDB option in your kernel and see if you can reproduce it so I get a traceback. The vnode information alone seems not quite as useful as I had hoped. Neither is the traceback. db_trace() prints using db_printf() so the message never reaches log files. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_STRATEGY on VCHR?
[EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], walt writes: VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), Sorry, need DDB option to print backtrace That feels like an error message (sort of) but everything seems to be working normally. Is this a real problem or just noise? Well, to you it's just noise, to me it's a real problem :-) It is probably the same problem as the one I just commited a fix for. Your patch eliminated my noise -- I hope it also fixed your problem ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_STRATEGY on VCHR?
Hi I received a similar problem during booting into single user mode upon startup. I hope the following helps: mounting root from ufs:/dev/ad2s1a start_init: trying /sbin/init VOP_STRATEGY on VCHR :0xc189a00: tag none, type VCHR, usecount 5, write count 0, refcount 6, flags (VV_OBJBUF) backtrace spec_strategy spec_getpages ffs_getpages vnode_pager_getpages exec_map_first_page kern_execve execve start_init fork_exit fork_trampoline --- trap 0x1, eip = 0, esp = 0xcbaaed7c, ebp = 0 --- [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], walt writes: After updating world and kernel this evening I saw this message fly by during the reboot: Mounting root from ufs:/dev/ad0s3a VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), Sorry, need DDB option to print backtrace That feels like an error message (sort of) but everything seems to be working normally. Is this a real problem or just noise? Well, to you it's just noise, to me it's a real problem :-) It is probably the same problem as the one I just commited a fix for. If you get this again after upgrading, please put the DDB option in your kernel and see if you can reproduce it so I get a traceback. The vnode information alone seems not quite as useful as I had hoped. -- Regards Peter As always the organisation disavows knowledge of this email To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_STRATEGY on VCHR?
That one should already be fixed. In message [EMAIL PROTECTED], Peter Kostouros writes: Hi I received a similar problem during booting into single user mode upon startup. I hope the following helps: mounting root from ufs:/dev/ad2s1a start_init: trying /sbin/init VOP_STRATEGY on VCHR :0xc189a00: tag none, type VCHR, usecount 5, write count 0, refcount 6, flags (VV_OBJBUF) backtrace spec_strategy spec_getpages ffs_getpages vnode_pager_getpages exec_map_first_page kern_execve execve start_init fork_exit fork_trampoline --- trap 0x1, eip = 0, esp = 0xcbaaed7c, ebp = 0 --- [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], walt writes: After updating world and kernel this evening I saw this message fly by during the reboot: Mounting root from ufs:/dev/ad0s3a VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), Sorry, need DDB option to print backtrace That feels like an error message (sort of) but everything seems to be working normally. Is this a real problem or just noise? Well, to you it's just noise, to me it's a real problem :-) It is probably the same problem as the one I just commited a fix for. If you get this again after upgrading, please put the DDB option in your kernel and see if you can reproduce it so I get a traceback. The vnode information alone seems not quite as useful as I had hoped. -- Regards Peter As always the organisation disavows knowledge of this email To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VOP_STRATEGY on VCHR?
After updating world and kernel this evening I saw this message fly by during the reboot: Mounting root from ufs:/dev/ad0s3a VOP_STRATEGY on VCHR : 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), Sorry, need DDB option to print backtrace That feels like an error message (sort of) but everything seems to be working normally. Is this a real problem or just noise? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
