linux-kernel - Re: 2.6.29: EXT4: __ext4_get_inode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090325011942.GH32307@mit.edu>
Date:	Tue, 24 Mar 2009 21:19:42 -0400
From:	Theodore Tso <tytso@....edu>
To:	Niel Lambrechts <niel.lambrechts@...il.com>
Cc:	"linux.kernel" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.29: EXT4: __ext4_get_inode_loc errors after s2disk

On Tue, Mar 24, 2009 at 10:25:57PM +0200, Niel Lambrechts wrote:
> Hi,
> 
> After upgrading to 2.6.29 I get the below errors after resuming from
> hibernating with s2disk. I ran fsck and tried doing the same thing again
> in 2.6.28.9-pae, but do not get any errors there.

The ext4 errors are interleaved with hardware errors, and the ext4
errors are about I/O errors.

EXT4-fs error (device sda6): __ext4_get_inode_loc: unable to read inode block - inode=2346519
EXT4-fs error (device sda6) in ext4_reserve_inode_write: IO failure

This looks more like a hibernation problem than an ext4 problem.
Looks like the hard drive is being left in some inconsistent state
after resuming from hibernation.

     	   	       		   	   - Ted

> sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
> sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
> sd 0:0:0:0: [sda] Add. Sense: No additional sense information
> end_request: I/O error, dev sda, sector 242190447
> sd 0:0:0:0: [sda]
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
> sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
> sd 0:0:0:0: [sda] block=9404418Add. Sense: No additional sense information end_request:
> I/O error, dev sda, sector 242190703
> sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors: (200 GB/186 GiB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors: (200 GB/186 GiB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/