Panic: Initiate_write_inodeblock_ufs1: already started
Recompiled the kernel (GENERIC) and installed.
But now it panics on:
Initiate_write_inodeblock_ufs1: already started.
--WjW
PS: Once it trips into the debugger, how do I get it to dump?
panic just reboots.
- Original Message -
From: [EMAIL PROTECTED]
To: Willem Jan Withagen [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, January 04, 2003 9:57 AM
Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small...
In message 03a701c2b38c$8e3ad990$471b3dd4@dual, Willem Jan Withagen writes:
Which seems a problem sticking up it's head once so often.
I had it happen to me now 3 times over the last day. It just drops into the
debugger.
And I've foun little extra info in the archive.
What dows this actually mean? Is something leaking in the kernel.
IF so how do I help it go away.
I'm copy 100G from a W2K system to my vinum file server with a 170G raid5.
Current is as of 28 dec...
Please try to move up to current as of today. On Dec 29th I commited
code to make the desiredvnodes a limit rather than a vague suggestion
and that should solve your problem I hope.
--
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.
èR{.nÇ+·¬zwfj)m¢f£¢·hkyàRàÂ+aº{.nÇ+·ç±×.®·§¶)í
æèw* ¶¦zË
Re: Panic: Initiate_write_inodeblock_ufs1: already started
In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes: Recompiled the kernel (GENERIC) and installed. But now it panics on: Initiate_write_inodeblock_ufs1: already started. When does it panic ? in the boot sequence ? after ? Can you get me the first 4-5 lines of the output from trace ? -- 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: Panic: Initiate_write_inodeblock_ufs1: already started
On Sun, Jan 05, 2003 at 05:01:15PM +0100, [EMAIL PROTECTED] wrote: In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes: But now it panics on: Initiate_write_inodeblock_ufs1: already started. When does it panic ? in the boot sequence ? after ? After about 24 hrs for me. Can you get me the first 4-5 lines of the output from trace ? (kgdb) bt #0 0xc01ccb5b in doadump () #1 0xc01cd05e in boot () #2 0xc01cd309 in panic () #3 0xc028aaf2 in initiate_write_inodeblock_ufs1 () #4 0xc028a500 in softdep_disk_io_initiation () #5 0xc019bb79 in spec_strategy () #6 0xc019ae18 in spec_vnoperate () #7 0xc020cdd3 in bwrite () #8 0xc020e270 in vfs_bio_awrite () #9 0xc019b937 in spec_fsync () #10 0xc019ae18 in spec_vnoperate () #11 0xc021ca24 in sched_sync () #12 0xc01b9f25 in fork_exit () Sorry already built a new kernel, so I don't have kernel.debug any longer. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic: Initiate_write_inodeblock_ufs1: already started
In message [EMAIL PROTECTED], David O'Brien writes: On Sun, Jan 05, 2003 at 05:01:15PM +0100, [EMAIL PROTECTED] wrote: In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes: But now it panics on: Initiate_write_inodeblock_ufs1: already started. When does it panic ? in the boot sequence ? after ? After about 24 hrs for me. Ok, I just found another stupid bug and committed a fix. Can I get you (and others who see this) to upgrade your sources so you have rev 1.351 of kern/vfs_bio.c ? -- 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
