All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16081] Data loss after crash during heavy I/O
Date: Sat, 5 Jun 2010 14:32:54 GMT	[thread overview]
Message-ID: <201006051432.o55EWsfX028759@demeter.kernel.org> (raw)
In-Reply-To: <bug-16081-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16081





--- Comment #18 from lkolbe@techfak.uni-bielefeld.de  2010-06-05 14:32:46 ---
Thanks, though. After working flawlessly for more than 13TiB, we hit another
crash today - a colleague called 'lsscsi', after that all commands quit with
'Bus error' for a while and the machine stuck with no messages on the serial
line. Befor that, cat /proc/interrupts worked and showed massive ERR:

shepherd:/etc# cat /proc/interrupts 
             CPU0       CPU1       CPU2       CPU3       
[...]
 THR:          0          0          0          0   Threshold APIC interrupts
 MCE:          0          0          0          0   Machine check exceptions
 MCP:         28         28         28         28   Machine check polls
 ERR:   37567046
 MIS:          0

I suppose this means it's not Linux fault?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-06-05 14:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 15:19 [Bug 16081] New: Data loss after crash during heavy I/O bugzilla-daemon
2010-05-31 15:21 ` [Bug 16081] " bugzilla-daemon
2010-05-31 15:22 ` bugzilla-daemon
2010-05-31 15:24 ` bugzilla-daemon
2010-05-31 15:28 ` bugzilla-daemon
2010-06-01 16:38 ` bugzilla-daemon
2010-06-02 12:02 ` bugzilla-daemon
2010-06-02 12:10 ` bugzilla-daemon
2010-06-02 15:57 ` bugzilla-daemon
2010-06-02 16:44 ` bugzilla-daemon
2010-06-02 16:44 ` bugzilla-daemon
2010-06-02 17:53 ` bugzilla-daemon
2010-06-02 18:06 ` bugzilla-daemon
2010-06-02 18:24 ` bugzilla-daemon
2010-06-02 18:28 ` bugzilla-daemon
2010-06-02 21:57 ` bugzilla-daemon
2010-06-02 22:07 ` bugzilla-daemon
2010-06-02 22:09 ` bugzilla-daemon
2010-06-03  6:02 ` bugzilla-daemon
2010-06-03 14:19 ` bugzilla-daemon
2010-06-05 14:32 ` bugzilla-daemon [this message]
2011-02-28  1:23 ` bugzilla-daemon
2011-02-28  1:24 ` 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=201006051432.o55EWsfX028759@demeter.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.