* [Bug 12533] New: with extents, ext4 block count wrong
@ 2009-01-24 9:18 bugme-daemon
2009-01-25 3:48 ` [Bug 12533] " bugme-daemon
2009-01-25 5:38 ` bugme-daemon
0 siblings, 2 replies; 3+ messages in thread
From: bugme-daemon @ 2009-01-24 9:18 UTC (permalink / raw)
To: linux-ext4
http://bugzilla.kernel.org/show_bug.cgi?id=12533
Summary: with extents, ext4 block count wrong
Product: File System
Version: 2.5
KernelVersion: 2.6.28
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: markus@cs.wisc.edu
Latest working kernel version: 2.6.28
Earliest failing kernel version: 2.6.28
Distribution: Gentoo
Hardware Environment: i686
Block size: 4096
I'm trying to recover from a massive data loss with ext4 (root directory
erased), so I'm looking at lots of hexedit output. Here's one thing that looks
quite wrong:
ED 41 E8 03 00 10 00 00 16 81 73 49 16 81 73 49
16 81 73 49 00 00 00 00 E8 03 03 00 08 00 00 00
00 00 08 00 02 00 00 00 0A F3 01 00 04 00 00 00
00 00 00 00 00 00 00 00 01 00 00 00 3E 17 13 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 61 27 09 0B 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The 4 in the second byte indicates this is a directory. The second word says
the file size is 4096 bytes, the same as the block size. The eight word says
there are eight blocks. Last, the extent header has one extent (second half of
the 11th word), and this one extent has a block count of 1 (first half of 15th
word).
The directory contains a single directory.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 12533] with extents, ext4 block count wrong
2009-01-24 9:18 [Bug 12533] New: with extents, ext4 block count wrong bugme-daemon
@ 2009-01-25 3:48 ` bugme-daemon
2009-01-25 5:38 ` bugme-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugme-daemon @ 2009-01-25 3:48 UTC (permalink / raw)
To: linux-ext4
http://bugzilla.kernel.org/show_bug.cgi?id=12533
markus@cs.wisc.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |REJECTED
Resolution| |INVALID
------- Comment #1 from markus@cs.wisc.edu 2009-01-24 19:48 -------
never mind. This is probably the way it's supposed to be.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 12533] with extents, ext4 block count wrong
2009-01-24 9:18 [Bug 12533] New: with extents, ext4 block count wrong bugme-daemon
2009-01-25 3:48 ` [Bug 12533] " bugme-daemon
@ 2009-01-25 5:38 ` bugme-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugme-daemon @ 2009-01-25 5:38 UTC (permalink / raw)
To: linux-ext4
http://bugzilla.kernel.org/show_bug.cgi?id=12533
------- Comment #2 from tytso@mit.edu 2009-01-24 21:38 -------
Yup. I suggest that you use debugfs, and that you look at some valid
filesystems before you start filing more bugs in the future....
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-01-25 5:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-24 9:18 [Bug 12533] New: with extents, ext4 block count wrong bugme-daemon
2009-01-25 3:48 ` [Bug 12533] " bugme-daemon
2009-01-25 5:38 ` bugme-daemon
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).