Re: Help with debugging a trace
Re: Help with debugging a trace
On Sat, Dec 23, 2006 at 02:52:16PM +0800, Vince Loden wrote:
> Thanks for replying, Paul.
> It panics with or without the 200 GB attached. Yes I'd thought maybe
> a FireWire problem too.
>
> Thanks. I hope I've given you enough info.
I just had a quick look at the source - that panic looks like it
is there to protect against a condition that shouldn't happen...
I'm beat - but running fsck over both disks wouldn't hurt.
> On 23 Dec 2006, at 2:47 PM, Paul Ripke wrote:
>
> >On Sat, Dec 23, 2006 at 01:45:23PM +0800, Vince Loden wrote:
> >>
> >>panic(cpu 0 caller 0x000E3DDC): vnode_writedone: numoutput < 0
> >
> >Without studying the info provided too deeply:
> >
> >Does it only panic when the 200 GB drive is mounted? I'd guess
> >that the HFS+ (I assume) metadata structures are corrupted on your
> >200 GB drive - umount and run fsck (Darwin method) or Disk Utility
> >(Mac OS X) over the filesystem.
> >
> >Either that, or there's unrelocatable bad blocks in the HFS+ metadata
> >structures that's causing problems. I haven't checked the source -
> >what does Darwin do on metadata write failures? Panic?
> >
> >Second look at the panic string and backtrace, I'm guessing the
> >later.
Cheers,
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden