I was able to copy the full 100+Gb.
Next I'm going to try and fill the disk to the max as user, but i guess it'll not
trigger this bug.
And to that fact I have a question:
At the moment 8% of the disk is reserved.
It being a 170Gb raid, that wastes a good 13,6Gb, which I find at lot.
tunefs lets me bring that down to 5% = 8,5Gb without speed penalty.
But is for this size of spare space such a large threshold really required??
And IF i would like to experiment, where do I look for the knop to turn??
Thanx for the support,
--WjW
> 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.
>
> I칻 &ޱݙݢjH:+칻 &~n\ޞاܨ~^,j
