From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203943] ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails
Date: Fri, 21 Jun 2019 20:47:31 +0000 [thread overview]
Message-ID: <bug-203943-13602-okw2w42dCu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203943-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203943
--- Comment #6 from Theodore Tso (tytso@mit.edu) ---
That's because the German translation is busted. I've complained to the
German maintainer of the e2fsprogs messages file at the Translation Project,
but it hasn't been fixed yet. See [1] for more details.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892173#10
It *should* have actually printed the inode number, and it does if you just use
the built-in English text. In general, I *really* wish people would disable
the use of the translation when reporting bugs, because very often the use of
the translations add noise that make life harder for developers, and in this
case, it was losing information for you, the system administrator.
See the debugfs man page for more details, but to specify inode numbers to
debugfs, you need to surround the inode number with angle brackets. Here are
some examples:
% debugfs /tmp/test.img
debugfs 1.45.2 (27-May-2019)
debugfs: ls a
12 (12) . 2 (12) .. 13 (988) motd
debugfs: stat /a/motd
Inode: 13 Type: regular Mode: 0644 Flags: 0x80000
Generation: 0 Version: 0x00000000
User: 0 Group: 0 Size: 286
File ACL: 0
Links: 1 Blockcount: 2
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x5d0d416e -- Fri Jun 21 16:43:26 2019
atime: 0x5d0d416e -- Fri Jun 21 16:43:26 2019
mtime: 0x5d0d416e -- Fri Jun 21 16:43:26 2019
Inode checksum: 0x0000857d
EXTENTS:
(0):20
debugfs: stat <13>
Inode: 13 Type: regular Mode: 0644 Flags: 0x80000
Generation: 0 Version: 0x00000000
User: 0 Group: 0 Size: 286
File ACL: 0
Links: 1 Blockcount: 2
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x5d0d416e -- Fri Jun 21 16:43:26 2019
atime: 0x5d0d416e -- Fri Jun 21 16:43:26 2019
mtime: 0x5d0d416e -- Fri Jun 21 16:43:26 2019
Inode checksum: 0x0000857d
EXTENTS:
(0):20
debugfs: ncheck 13
Inode Pathname
13 /a/motd
debugfs: stat a
Inode: 12 Type: directory Mode: 0755 Flags: 0x80000
Generation: 0 Version: 0x00000000
User: 0 Group: 0 Size: 1024
File ACL: 0
Links: 2 Blockcount: 2
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x5d0d416b -- Fri Jun 21 16:43:23 2019
atime: 0x5d0d416b -- Fri Jun 21 16:43:23 2019
mtime: 0x5d0d416b -- Fri Jun 21 16:43:23 2019
Inode checksum: 0x000042d4
EXTENTS:
(0):18
debugfs: block_dump 18
0000 0c00 0000 0c00 0102 2e00 0000 0200 0000 ................
0020 0c00 0202 2e2e 0000 0d00 0000 dc03 0401 ................
0040 6d6f 7464 0000 0000 0000 0000 0000 0000 motd............
0060 0000 0000 0000 0000 0000 0000 0000 0000 ................
*
1760 0000 0000 0000 0000 0c00 00de be4e 16e9 .............N..
debugfs:
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-06-21 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 6:51 [Bug 203943] New: ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails bugzilla-daemon
2019-06-21 7:15 ` [Bug 203943] " bugzilla-daemon
2019-06-21 12:40 ` bugzilla-daemon
2019-06-21 14:52 ` bugzilla-daemon
2019-06-21 18:29 ` bugzilla-daemon
2019-06-21 19:34 ` bugzilla-daemon
2019-06-21 20:47 ` bugzilla-daemon [this message]
2019-06-22 7:48 ` bugzilla-daemon
2019-06-22 8:06 ` 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-203943-13602-okw2w42dCu@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).