From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 187051] "orphan list check failed" error in ext4
Date: Mon, 30 Jan 2017 15:24:29 +0000 [thread overview]
Message-ID: <bug-187051-13602-3nEpnuYJid@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-187051-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=187051
--- Comment #18 from Hussam Al-Tayeb <me@hussam.eu.org> ---
No, it was only happening once a month or so.
I upgraded today to a corei5 with 8GB ram. I just plugged in my old hard disks
and rebuilt the initramfs image.
Perhaps the old hardware was too little for the load I was putting on the
computer.
I'll wait and see. Hopefully the issues will be gone.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-30 15:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 20:27 [Bug 187051] New: "orphan list check failed" error in ext4 bugzilla-daemon
2016-11-06 23:48 ` [Bug 187051] " bugzilla-daemon
2016-11-07 10:40 ` bugzilla-daemon
2016-11-07 17:02 ` bugzilla-daemon
2016-11-07 17:50 ` bugzilla-daemon
2016-11-07 19:39 ` bugzilla-daemon
2016-11-07 20:31 ` bugzilla-daemon
2016-11-08 15:15 ` bugzilla-daemon
2017-01-28 12:25 ` bugzilla-daemon
2017-01-28 12:52 ` bugzilla-daemon
2017-01-29 5:09 ` bugzilla-daemon
2017-01-29 9:02 ` bugzilla-daemon
2017-01-29 10:00 ` bugzilla-daemon
2017-01-29 11:53 ` bugzilla-daemon
2017-01-29 11:56 ` bugzilla-daemon
2017-01-29 11:56 ` bugzilla-daemon
2017-01-29 11:59 ` bugzilla-daemon
2017-01-30 2:21 ` bugzilla-daemon
2017-01-30 15:24 ` bugzilla-daemon [this message]
2017-08-28 11:57 ` bugzilla-daemon
2017-10-03 22:44 ` bugzilla-daemon
2017-10-04 12:35 ` bugzilla-daemon
2017-10-05 2:27 ` bugzilla-daemon
2017-10-05 11:00 ` 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-187051-13602-3nEpnuYJid@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.