From: Kevin Shanahan <kmshanah@ucwb.org.au>
To: linux-ext4@vger.kernel.org
Subject: Re: More ext4 acl/xattr corruption - 4th occurence now
Date: Thu, 14 May 2009 09:26:18 +0930 [thread overview]
Message-ID: <20090513235618.GC4914@kulgan> (raw)
In-Reply-To: <20090513062634.GE4972@kulgan>
On Wed, May 13, 2009 at 03:56:34PM +0930, Kevin Shanahan wrote:
> And following the same formula as last time(s):
>
> hermes:~# debugfs /dev/dm-0
> debugfs: stat "local/apps/OLD-APPS/APPS/NWAPPS/OAIII/OATEMP/F_CLPROF.IF"
> invalid inode->i_extra_isize (8224)
> Inode: 2542 Type: bad type Mode: 0043 Flags: 0x5849462f
> Generation: 538970637 Version: 0x66663030:535f4445
> User: 538980401 Group: 538993001 Size: 996566576
> File ACL: 538976288 Directory ACL: 0
> Links: 8812 Blockcount: 35322822674750
> Fragment: Address: 538976288 Number: 0 Size: 0
> ctime: 0x41462d54:65636166 -- Tue Sep 14 08:59:24 2004
> atime: 0x4e4f4620:63206c61 -- Sat Aug 20 14:59:04 2011
> mtime: 0x594c494d:6972413d -- Fri Jun 23 08:18:45 2017
> crtime: 0x726f6c6f:3138233d -- Sun Nov 3 13:24:39 2030
> dtime: 0x7241203a -- Sun Sep 29 09:35:14 2030
> Size of extra inode fields: 8224
> BLOCKS:
>
> debugfs: imap "local/apps/OLD-APPS/APPS/NWAPPS/OAIII/OATEMP/F_CLPROF.IF"
> Inode 2542 is part of block group 0
> located at block 447, offset 0x0d00
>
> hermes:~# dd if=/dev/dm-0 of=block-447.dump bs=4k skip=447 count=1
> 1+0 records in
> 1+0 records out
> 4096 bytes (4.1 kB) copied, 0.0121164 s, 338 kB/s
>
> Now, this is (possibly) interesting - that block contains a bunch of
> file data. Looks like a html email (I can tell it's email because of
> the FIXED_ prefix added to the tags by the mail sanitizer).
>
> If I can locate the source of that data, perhaps it will point to
> where the corruption is coming from? Any tips on scanning for the
> data? I'll start with simple find and grep and see how far I get.
I didn't find this in any file in the current directory structure. I
guess it could be old data that hadn't been zeroed out.
However, the only binary data I can see seems to be at offset 0x0155
(341), nowhere near offset 0x0d00 (unless I misunderstand the imap
output above. Does that little blob of binary data make any sense as
an inode?
Cheers,
Kevin.
next prev parent reply other threads:[~2009-05-13 23:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 6:26 More ext4 acl/xattr corruption - 4th occurence now Kevin Shanahan
2009-05-13 23:56 ` Kevin Shanahan [this message]
2009-05-14 4:40 ` Theodore Tso
2009-05-14 11:07 ` Kevin Shanahan
2009-05-14 11:17 ` Manish Katiyar
2009-05-14 12:30 ` Theodore Tso
2009-05-14 13:25 ` Kevin Shanahan
2009-05-14 14:07 ` Theodore Tso
2009-05-14 14:30 ` Kevin Shanahan
2009-05-14 15:44 ` Eric Sandeen
2009-05-14 21:07 ` Kevin Shanahan
2009-05-14 21:08 ` Eric Sandeen
2009-05-14 16:12 ` Theodore Tso
2009-05-14 21:02 ` Kevin Shanahan
2009-05-14 21:23 ` Theodore Tso
2009-05-14 21:33 ` Kevin Shanahan
2009-05-15 23:18 ` Kevin Shanahan
2009-05-15 1:21 ` Eric Sandeen
2009-05-15 12:50 ` Theodore Tso
2009-05-15 12:58 ` Eric Sandeen
2009-05-15 15:24 ` Eric Sandeen
2009-05-15 16:27 ` Eric Sandeen
2009-05-15 4:55 ` Aneesh Kumar K.V
2009-05-15 10:11 ` Theodore Tso
2009-05-15 13:07 ` Theodore Tso
2009-05-19 10:00 ` Thierry Vignaud
2009-05-19 11:36 ` Theodore Tso
2009-05-19 12:01 ` Alex Tomas
2009-05-19 15:04 ` Theodore Tso
2009-05-19 15:16 ` Alex Tomas
2009-05-19 15:18 ` Thierry Vignaud
2009-05-15 3:57 ` Alex Tomas
2009-05-15 4:58 ` Aneesh Kumar K.V
2009-05-15 10:27 ` Theodore Tso
2009-05-18 2:14 ` [PATCH] ext4: Add a comprehensive block validity check to ext4_get_blocks() (Was: More ext4 acl/xattr corruption - 4th occurence now) Theodore Tso
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=20090513235618.GC4914@kulgan \
--to=kmshanah@ucwb.org.au \
--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).