From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 32182] EXT4-fs error: bad header/extent
Date: Thu, 05 Mar 2015 14:32:44 +0000 [thread overview]
Message-ID: <bug-32182-13602-QPT1HpZrnp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-32182-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=32182
Adam Surak <adam.surak@algolia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adam.surak@algolia.com
--- Comment #16 from Adam Surak <adam.surak@algolia.com> ---
We experience this problem and the FS remounts to read-only. BuildServer is our
write heavy application, the server has RAID0 using MD. We have seen this
problem on servers with Ubuntu kernel (3.13.x) and MD raid (Samsung SSDs) and
also on servers with OVH custom built kernel (3.10) and LSI HW raid (Intel
S3500 SSDs) - although we see the issue on the servers with MD raid more often.
Syslog
======
Mar 5 13:30:01 c5-use-1 CRON[12504]: (root) CMD (/usr/bin/run-chef-client.sh)
Mar 5 13:30:35 c5-use-1 kernel: [10890197.121882] EXT4-fs error (device md3):
ext4_ext_remove_space:2935: inode #26869814: comm BuildServer: pblk 107512509
bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Mar 5 13:30:35 c5-use-1 kernel: [10890197.205494] Aborting journal on device
md3-8.
Mar 5 13:30:35 c5-use-1 kernel: [10890197.232881] EXT4-fs (md3): Remounting
filesystem read-only
Mar 5 13:30:35 c5-use-1 kernel: [10890197.244669] EXT4-fs error (device md3):
ext4_journal_check_start:56: Detected aborted journal
Mar 5 13:30:35 c5-use-1 kernel: [10890197.244673] EXT4-fs (md3): Remounting
filesystem read-only
Mar 5 13:30:35 c5-use-1 kernel: [10890197.342604] EXT4-fs error (device md3)
in ext4_ext_remove_space:3006: IO failure
Mar 5 13:30:35 c5-use-1 kernel: [10890197.398828] EXT4-fs error (device md3)
in ext4_ext_truncate:4544: IO failure
Mar 5 13:30:35 c5-use-1 kernel: [10890197.457592] EXT4-fs error (device md3)
in ext4_reserve_inode_write:4874: Journal has aborted
Mar 5 13:30:35 c5-use-1 kernel: [10890197.521148] EXT4-fs error (device md3)
in ext4_truncate:3797: Journal has aborted
Mar 5 13:30:35 c5-use-1 kernel: [10890197.588798] EXT4-fs error (device md3)
in ext4_reserve_inode_write:4874: Journal has aborted
Mar 5 13:30:35 c5-use-1 kernel: [10890197.659161] EXT4-fs error (device md3)
in ext4_orphan_del:2685: Journal has aborted
Mar 5 13:30:35 c5-use-1 kernel: [10890197.732682] EXT4-fs error (device md3)
in ext4_reserve_inode_write:4874: Journal has aborted
Mar 5 13:31:01 c5-use-1 CRON[13879]: (root) CMD ( /usr/bin/netstat.sh >
/tmp/netstat.json)
Debugfs
=======
debugfs -R 'stat <26869814>' /dev/md3
debugfs 1.42.9 (4-Feb-2014)
Inode: 26869814 Type: regular Mode: 0644 Flags: 0x80000
Generation: 2509781484 Version: 0x00000000:00000001
User: 1001 Group: 1001 Size: 0
File ACL: 0 Directory ACL: 0
Links: 0 Blockcount: 816256
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x54f85a7b:0fc8be80 -- Thu Mar 5 13:30:35 2015
atime: 0x54ee0aac:127f86a8 -- Wed Feb 25 17:47:24 2015
mtime: 0x54ee0ab5:693a9f7c -- Wed Feb 25 17:47:33 2015
crtime: 0x54ee0aac:127f86a8 -- Wed Feb 25 17:47:24 2015
dtime: 0x0194088b -- Tue Nov 3 11:12:11 1970
Size of extra inode fields: 28
EXTENTS:
(ETB0):107512509
uname -a
========
Linux c5-use-1 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
mount
=====
/dev/md3 on /home type ext4 (rw,noatime,nodiratime,errors=remount-ro)
I got also SMART output, dumpe2fs, lspci, mdadm, dpkg, dmesg and es2fsck
outputs but the files are quite extensive so I've put them to
http://www.surak.eu/fs-ro.tar.gz
Let me know if anything more is needed about the config of the server.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2015-03-05 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 16:47 [Bug 32182] New: EXT4-fs error: bad header/extent bugzilla-daemon
2011-04-01 14:07 ` Yongqiang Yang
2011-04-01 14:07 ` [Bug 32182] " bugzilla-daemon
2011-04-01 15:27 ` bugzilla-daemon
2011-04-01 15:29 ` bugzilla-daemon
2011-04-01 22:01 ` bugzilla-daemon
2011-04-01 23:21 ` bugzilla-daemon
2011-04-22 10:59 ` bugzilla-daemon
2011-06-06 19:59 ` bugzilla-daemon
2011-07-07 5:15 ` bugzilla-daemon
2011-07-07 14:45 ` bugzilla-daemon
2011-08-24 21:50 ` bugzilla-daemon
2012-08-20 15:23 ` bugzilla-daemon
2012-08-20 20:06 ` bugzilla-daemon
2012-08-21 0:44 ` bugzilla-daemon
2012-08-21 20:33 ` bugzilla-daemon
2012-08-21 21:34 ` bugzilla-daemon
2015-03-05 14:32 ` bugzilla-daemon [this message]
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-32182-13602-QPT1HpZrnp@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).