From: Stone <stone@heisl.org>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Brocken Raid & LUKS
Date: Sun, 24 Feb 2013 19:22:18 +0100 [thread overview]
Message-ID: <512A5A5A.5020904@heisl.org> (raw)
In-Reply-To: <512A2094.3020008@turmel.org>
Am 24.02.2013 15:15, schrieb Phil Turmel:
> On 02/24/2013 02:10 AM, Stone wrote:
>
>> e2fsck: aborted
>>
>> the output have 711mb..
>> do you ned more examples?
>> what do you say to case1?
> I think you need to see case2. Case #1 isn't very good.
>
> Phil
>
roger.
print
Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdc: 3907029168s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 34s 3907029118s 3907029085s primary
fsck:
One or more block group descriptor checksums are invalid. Fix? no
Group descriptor 0 checksum is invalid. IGNORED.
Group descriptor 1 checksum is invalid. IGNORED.
Group descriptor 2 checksum is invalid. IGNORED.
Group descriptor 3 checksum is invalid. IGNORED. -> up to 44712
...
....
HTREE directory inode 6140 has an invalid root node.
Clear HTree index? no
Inode 6140 should not have EOFBLOCKS_FL set (size 11864516288231708776,
lblk -1)
Clear? no
Inode 6140, i_size is 11864516288231708776, should be 0. Fix? no
Inode 6140, i_blocks is 146149627678319, should be 0. Fix? no
Inode 6141 is in use, but has dtime set. Fix? no
Inode 6141 has imagic flag set. Clear? no
Inode 6141 has a extra size (39571) which is invalid
Fix? no
Inode 6141 has compression flag set on filesystem without compression
support. Clear? no
Inode 6141, i_size is 9532800016578411510, should be 0. Fix? no
Inode 6141, i_blocks is 44690332653787, should be 0. Fix? no
.....
....
....
Suppress messages? no
Illegal block #2039 (1737394854) in inode 5693. IGNORED.
Illegal block #2040 (2008213591) in inode 5693. IGNORED.
Illegal block #2041 (2130466482) in inode 5693. IGNORED.
Illegal block #2042 (1739888040) in inode 5693. IGNORED.
Illegal block #2043 (1807109420) in inode 5693. IGNORED.
Illegal block #2044 (3445204660) in inode 5693. IGNORED.
Illegal block #2045 (1712689420) in inode 5693. IGNORED.
Illegal block #2046 (1938106967) in inode 5693. IGNORED.
Illegal block #2047 (3704437218) in inode 5693. IGNORED.
Illegal block #2048 (2131383249) in inode 5693. IGNORED.
Illegal block #2049 (2676662235) in inode 5693. IGNORED.
Illegal block #2050 (2662461689) in inode 5693. IGNORED.
Too many illegal blocks in inode 5693.
Clear inode? no
Suppress messages? no
Illegal block #2051 (4286896066) in inode 5693. IGNORED.
Illegal block #2055 (3899334065) in inode 5693. IGNORED.
Illegal block #2056 (3410742419) in inode 5693. IGNORED.
Illegal block #2057 (3944198843) in inode 5693. IGNORED.
Illegal block #2058 (3374907392) in inode 5693. IGNORED.
Illegal indirect block (2165853531) in inode 5693. IGNORED.
Error while iterating over blocks in inode 5693: Illegal indirect block
found
e2fsck: aborted
same shit different partion.
the logfile have 708mb
:(
next prev parent reply other threads:[~2013-02-24 18:22 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 16:01 Brocken Raid & LUKS stone
2013-02-19 17:57 ` Phil Turmel
[not found] ` <5123E4E9.3020609@heisl.org>
2013-02-19 21:16 ` Phil Turmel
[not found] ` <5123EF45.6080405@heisl.org>
[not found] ` <5123F7C7.7000406@turmel.org>
[not found] ` <5123FB71.3060509@heisl.org>
2013-02-20 0:31 ` Phil Turmel
2013-02-20 18:32 ` Stone
2013-02-20 18:39 ` Phil Turmel
2013-02-21 7:04 ` Stone
2013-02-21 9:42 ` stone
2013-02-21 13:29 ` Phil Turmel
2013-02-21 14:19 ` stone
2013-02-21 15:04 ` Phil Turmel
2013-02-21 15:30 ` stone
2013-02-21 15:38 ` Phil Turmel
2013-02-21 15:49 ` Phil Turmel
2013-02-21 16:32 ` Stone
2013-02-21 16:41 ` Phil Turmel
2013-02-21 16:43 ` Stone
2013-02-21 16:46 ` Phil Turmel
2013-02-21 16:51 ` Stone
2013-02-21 16:54 ` Phil Turmel
2013-02-21 17:17 ` Stone
2013-02-21 17:23 ` Stone
2013-02-21 17:36 ` Phil Turmel
2013-02-21 17:47 ` Stone
2013-02-21 18:00 ` Phil Turmel
2013-02-21 18:08 ` Stone
2013-02-21 18:11 ` Phil Turmel
2013-02-21 18:29 ` Stone
2013-02-21 18:54 ` Phil Turmel
2013-02-21 19:12 ` Stone
2013-02-21 19:17 ` Stone
2013-02-21 19:24 ` Phil Turmel
2013-02-21 19:29 ` Stone
2013-02-21 19:45 ` Phil Turmel
2013-02-21 19:46 ` Stone
[not found] ` <51269DE0.5070905@heisl.org>
2013-02-22 10:31 ` stone
2013-02-22 13:53 ` Phil Turmel
2013-02-22 14:58 ` Stone
2013-02-22 15:37 ` Phil Turmel
2013-02-22 18:17 ` Stone
2013-02-22 18:23 ` Phil Turmel
2013-02-22 20:43 ` Stone
2013-02-22 22:35 ` Phil Turmel
2013-02-22 22:42 ` Stone
2013-02-23 2:22 ` Phil Turmel
2013-02-23 3:11 ` Stone
2013-02-23 4:36 ` Phil Turmel
2013-02-23 10:19 ` Stone
2013-02-23 16:10 ` Phil Turmel
2013-02-23 22:26 ` Stone
2013-02-23 23:49 ` Phil Turmel
2013-02-24 0:13 ` Stone
2013-02-24 4:04 ` Phil Turmel
2013-02-24 7:10 ` Stone
2013-02-24 14:15 ` Phil Turmel
2013-02-24 18:22 ` Stone [this message]
2013-02-24 18:33 ` Phil Turmel
2013-02-24 19:23 ` Stone
2013-02-24 19:51 ` Phil Turmel
2013-02-24 20:15 ` Stone
2013-02-24 20:25 ` Phil Turmel
2013-02-24 20:38 ` Stone
2013-02-24 20:44 ` Phil Turmel
2013-02-24 20:47 ` Stone
2013-02-25 9:06 ` stone
2013-02-25 18:31 ` Stone
2013-02-25 20:11 ` Stone
2013-02-26 0:19 ` Phil Turmel
2013-02-27 7:26 ` Stone
2013-02-27 19:04 ` Stone
2013-02-27 19:33 ` Hans-Peter Jansen
2013-02-27 19:51 ` Stone
2013-03-02 17:13 ` Phil Turmel
[not found] ` <5127B0AB.5040108@heisl.org>
2013-02-22 18:30 ` Phil Turmel
2013-02-21 22:29 ` Chris Murphy
2013-02-21 22:34 ` Phil Turmel
2013-02-21 22:20 ` Chris Murphy
2013-02-21 22:26 ` Phil Turmel
2013-02-21 13:15 ` Phil Turmel
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=512A5A5A.5020904@heisl.org \
--to=stone@heisl.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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.