All I did is to remove the /quota* files and then quotaoff -a
No more problems... so far
I have tryied what normally locks up systematicaly the sync command.
While heavy Disk IO doing a sync and no more problems.
So I really, so far, suspect problems in the quota code in the kernel.
Can somebody verify that and confirm my problem?
Thanks
Andre
On Tue, 20 April 1999, Andre . Couture wrote:
>
> Hi again,
>
> Could it actually be something related to QUOTAS???
>
> I will now try turning quotas off for a while and see.
>
> /Andre
>
> On Mon, 19 April 1999, Eric W. Biederman wrote:
>
> >
> > >>>>> "AC" == Andre Couture <coutuan@search-n-find.com> writes:
> >
> > AC> Hi all,
> >
> > AC> Since 2.2.? I have been having a lot of problem using the sync command.
> >
> > AC> It "hang" my system and sometimes just the window from which I'm running
> > AC> the command "sync".
> >
> > AC> It is very consistant (works fine 1 out of 4).
> >
> > AC> The major difference is that I rencently installed vmware which runs
> > AC> with nice -19
> > AC> But I don't see how could that affect the sync command except for the
> > AC> fac that it is very "io consuming".
> >
> > Besides the fact that the vmware module just creates a hole in
> > the kernel security that vmware can climb in, and do whatever it pleases?
> >
> > I have heard of other instances of vmware cause clock ticks to be missed.
> >
> > I admit vmware rubs me the the wrong way. But unless you can reproduce
> > this without vmware, running it's probably not a kernel bug.
> >
> > Eric
>
> Andre Couture
> PCDOCS/Fulcrum S.A. - Europe
>
> Office: +33(1)46.29.07.40
> GSM Europe: +33(6)07.04.35.65
> FAX/Voicemail Europe: +33(1) 53.01.29.63
> FAX/Voicemail Canada: +1(514) 221-2261
Andre Couture
PCDOCS/Fulcrum S.A. - Europe
Office: +33(1)46.29.07.40
GSM Europe: +33(6)07.04.35.65
FAX/Voicemail Europe: +33(1) 53.01.29.63
FAX/Voicemail Canada: +1(514) 221-2261
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/