2009-03-24 20:26:17

by Niel Lambrechts

[permalink] [raw]
Subject: 2.6.29: EXT4: __ext4_get_inode_loc errors after s2disk

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.

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
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >

sd 0:0:0:0: [sda] Attached SCSI disk

EXT4-fs: barriers enabled
kjournald2 starting: pid 649, dev sda6:8, commit interval 5 seconds
EXT4 FS on sda6, internal journal on sda6:8
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs: mounted filesystem sda6 with ordered data mode
EXT4 (no)acl options not supported
Adding 2099328k swap on /dev/sda5. Priority:-1 extents:1across:2099328k
EXT3 FS on sda7, internal journal
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Starting disk
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
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
EXT4-fs error (device sda6): __ext4_get_inode_loc: <6>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] unable to read inode block - inode=2346519,
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
EXT4-fs error (device sda6) in ext4_reserve_inode_write: IO failure

Any ideas?

Niel


2009-03-25 01:19:58

by Theodore Ts'o

[permalink] [raw]
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

2009-03-25 22:27:09

by Pavel Machek

[permalink] [raw]
Subject: Re: 2.6.29: EXT4: __ext4_get_inode_loc errors after s2disk

On Tue 2009-03-24 22:25:57, 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.

what kind of disk/what kind of controller is that?
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

2009-03-25 22:43:46

by Niel Lambrechts

[permalink] [raw]
Subject: Re: 2.6.29: EXT4: __ext4_get_inode_loc errors after s2disk

On 03/26/2009 12:30 AM, Pavel Machek wrote:
> On Tue 2009-03-24 22:25:57, Niel Lambrechts wrote:
>> 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.
>
> what kind of disk/what kind of controller is that?

Hi Pavel,

It is a Lenovo W500 Thinkpad.

lspci shows:

00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI
Controller (rev 03)

and for the disk, hdparm shows:
/dev/sda:

Model=HITACHI HTS722020K9SA00 FDE , FwRev=DC4LC75A,
SerialNo=080726DP0470DTGMUNPC
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=15203kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=390721968
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7

* signifies the current active mode


Niel