From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 102731] I have a cough.
Date: Fri, 22 Jan 2016 10:27:24 +0000 [thread overview]
Message-ID: <bug-102731-13602-EqBrnOnyqM@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 #34 from John Hughes <john@calva.com> ---
I first started seeing the problem when I moved the guest kernel to 3.16
(i.e. started using the ext4 driver for my ext3 fileystems).
1. Host 3.16, Guest 3.16, 1G memory, filesystem goes readonly after
around 4 days
Then I upgraded the guest to 3.18.19
2. Host 3.16 Guest 3.18.19, 1G memory, filesystem goes readonly after
around 20 days
Then I upgraded the guest to 4.3.2
3. Host 3.16 Guest 4.3.2, 1G memory, filesystem goes readonly after 4 days
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.
4. Host 4.3.2, Guest 4.3.2, 2G memory, system ran for 90 days with no
problem.
So now I've set the guest to 3.16 with 1G of memory. We'll see what
happens next.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-01-22 10:27 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 [this message]
2016-01-22 15:20 ` bugzilla-daemon
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-EqBrnOnyqM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.