archive mirror
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <>
Subject: Re: decoded problem in 2.4.22-pre10
Date: Tue, 5 Aug 2003 14:57:43 +0200	[thread overview]
Message-ID: <> (raw)

> On  5 Aug 03 at 14:23, Stephan von Krawczynski wrote:
> > 
> > Hello Petr,
> > 
> > at this time I can't provide you with details or exact reporting as the box has
> > to be used for finding the 2.4.22-pre stability problem I see. And since the
> > crashes take quite some time to occur I cannot reboot and check out what's the
> > deal with the vmware modules.

One more thing. VMware creates file in /tmp, unlinks it, and then file 
gradually expands as VM is initialized, so it grews from 0 to your
guest memory size + videoram size + ~5MB, while at same time all portions
of that file are MAP_SHARED to several processes.

And at exit VMware does ftruncate(xxx,0) to throw away unneeded data,
preventing them from hitting disk on subsequent (f)sync(), and this 
ftruncate() happens while other processes which have mmapped file are
doing munmap or exit, finding dirty pages which have no
underlying storage anymore during cleanup...

Both these operations were observed to cause problems in the past -
- on startup long ago reiserfs had problems with grewing unlinked files,
on shutdown kernel's mm raced with ftruncate. Both these problems are
currently fixed, but maybe some other race appeared somewhere?
                                            Best regards,
                                                Petr Vandrovec

             reply	other threads:[~2003-08-05 12:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 12:57 Petr Vandrovec [this message]
2003-08-05 13:24 ` decoded problem in 2.4.22-pre10 Stephan von Krawczynski
  -- strict thread matches above, loose matches on Subject: below --
2003-08-05 12:46 Petr Vandrovec
2003-08-06 10:27 ` Stephan von Krawczynski
2003-08-05 12:02 Petr Vandrovec
2003-08-05 12:23 ` Stephan von Krawczynski
2003-08-05  8:00 Stephan von Krawczynski
2003-08-05 10:20 ` Stephan von Krawczynski
2003-08-05 12:40 ` Marcelo Tosatti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).