From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 102731] I have a cough.
Date: Fri, 22 Jan 2016 15:20:01 +0000 [thread overview]
Message-ID: <bug-102731-13602-EzcKX9W3L5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-102731-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=102731
--- Comment #35 from cwseys@physics.wisc.edu ---
Thanks!
I think you mistyped 4.2.3 -> 4.3.2 .
Here's the table (helps me see any pattern b/c it is closer together. Less
memory required. :) )
Hversion Gversion Gmem time before read-only
3.16 3.16 1 GB ~4 days
3.16 3.18.19 1 GB ~20 days
3.16 4.2.3 1 GB 4 days
4.2.3 4.2.3 2 GB not after ~90 days
4.2.3 3.16 1 GB inprogress
> Then I upgraded the host to 4.3.2, noticed the guest had only 1G of
> memory (and the guest kernel was bitching about not having enough memory
> during some TCP operations) so I increased the guest memory to 2G, Bad
> debugging style, but I was desperate.
Debugging and production don't get along well together. :)
> So now I've set the guest to 3.16 with 1G of memory. We'll see what
> happens next.
I haven't tried changing the host's kernel version yet. Will be interested to
know how it turns out! Thanks for debugging and hopefully you'll help us
(Debian/Ubuntu users) find a workaround at least.
Thanks again,
Chad.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-01-22 15:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 8:47 [Bug 102731] New: I have a cough bugzilla-daemon
2015-08-12 8:56 ` [Bug 102731] " bugzilla-daemon
2015-08-12 9:02 ` bugzilla-daemon
2015-08-12 9:11 ` bugzilla-daemon
2015-08-12 9:12 ` bugzilla-daemon
2015-08-12 18:53 ` bugzilla-daemon
2015-08-12 19:25 ` bugzilla-daemon
2015-08-31 15:46 ` bugzilla-daemon
2015-08-31 15:47 ` bugzilla-daemon
2015-08-31 18:03 ` bugzilla-daemon
2015-09-01 10:28 ` bugzilla-daemon
2015-09-01 14:43 ` bugzilla-daemon
2015-09-01 16:08 ` bugzilla-daemon
2015-09-16 14:09 ` bugzilla-daemon
2015-09-28 17:06 ` bugzilla-daemon
2015-09-30 9:49 ` bugzilla-daemon
2015-10-07 16:17 ` bugzilla-daemon
2015-10-08 9:16 ` bugzilla-daemon
2015-10-11 4:05 ` bugzilla-daemon
2015-10-12 10:36 ` bugzilla-daemon
2015-10-12 14:01 ` bugzilla-daemon
2015-10-15 15:32 ` bugzilla-daemon
2015-10-15 15:38 ` bugzilla-daemon
2015-10-15 15:41 ` bugzilla-daemon
2015-10-16 13:04 ` bugzilla-daemon
2015-10-16 15:53 ` bugzilla-daemon
2015-10-16 16:14 ` bugzilla-daemon
2015-10-20 13:40 ` bugzilla-daemon
2015-10-20 15:44 ` bugzilla-daemon
2015-10-20 15:55 ` bugzilla-daemon
2015-10-20 16:28 ` bugzilla-daemon
2015-10-20 16:30 ` bugzilla-daemon
2015-11-25 10:09 ` bugzilla-daemon
2016-01-19 12:00 ` bugzilla-daemon
2016-01-21 23:57 ` bugzilla-daemon
2016-01-22 10:27 ` bugzilla-daemon
2016-01-22 15:20 ` bugzilla-daemon [this message]
2016-01-22 16:36 ` bugzilla-daemon
2016-02-08 9:52 ` bugzilla-daemon
2016-02-08 10:56 ` bugzilla-daemon
2016-03-18 22:20 ` bugzilla-daemon
2016-03-19 17:49 ` bugzilla-daemon
2016-03-20 1:27 ` bugzilla-daemon
2016-03-20 23:26 ` bugzilla-daemon
2016-03-21 13:04 ` bugzilla-daemon
2016-03-25 16:55 ` bugzilla-daemon
2016-04-08 15:49 ` bugzilla-daemon
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-102731-13602-EzcKX9W3L5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).