[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#488945: marked as done (kmauz@htwg-konstanz.de: SCSI "Recovered Error" - stop ext3 journal - remount read-only)



Your message dated Tue, 8 Sep 2009 22:03:39 +0200
with message-id <20090908200339.GM19152@inutil.org>
and subject line Re: kmauz@htwg-konstanz.de: SCSI "Recovered Error" - stop ext3 journal - remount read-only
has caused the Debian Bug report #488945,
regarding kmauz@htwg-konstanz.de: SCSI "Recovered Error" - stop ext3 journal - remount read-only
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
488945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488945
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12etch2

Dear debian-kernel-team,

During storage maintainance a scsi error occured and stopped the ext3
journal.

The setup:

Debian etch/i386:
Kernel: Linux homesrv 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007
i686 GNU/Linux

lsmod:
nfs                   202828  0 
nfsd                  197936  25 
exportfs                5600  1 nfsd
lockd                  54344  3 nfs,nfsd
nfs_acl                 3584  2 nfs,nfsd
sunrpc                138812  13 nfs,nfsd,lockd,nfs_acl
vmmemctl               10332  0 
ipv6                  226016  36 
quota_v2                8864  6 
dm_snapshot            15552  0 
dm_mirror              19152  0 
dm_mod                 50232  2 dm_snapshot,dm_mirror
loop                   15048  0 
tsdev                   7520  0 
i2c_piix4               8140  0 
parport_pc             32132  0 
parport                33256  1 parport_pc
intel_agp              21148  1 
floppy                 53156  0 
shpchp                 33024  0 
pci_hotplug            28704  1 shpchp
i2c_core               19680  1 i2c_piix4
vmxnet                 11712  0 
agpgart                29896  1 intel_agp
rtc                    12372  0 
psmouse                35016  0 
pcspkr                  3072  0 
serio_raw               6660  0 
evdev                   9088  0 
ext3                  119240  8 
jbd                    52456  1 ext3
mbcache                 8356  1 ext3
sd_mod                 19040  17 
ide_cd                 36064  0 
cdrom                  32544  1 ide_cd
mptspi                 16136  9 
mptscsih               21696  1 mptspi
mptbase                46176  2 mptspi,mptscsih
scsi_transport_spi     22336  1 mptspi
scsi_mod              124168  4
sd_mod,mptspi,mptscsih,scsi_transport_spi
piix                    9444  0 [permanent]
generic                 5476  0 [permanent]
ide_core              110504  3 ide_cd,piix,generic
thermal                13608  0 
processor              28840  1 thermal
fan                     4804  0 

cat /proc/scsi/scsi

Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: VMware   Model: Virtual disk     Rev: 1.0 
Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: VMware   Model: Virtual disk     Rev: 1.0 
Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: SUN      Model: CSM200_R         Rev: 0619
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: SUN      Model: CSM200_R         Rev: 0619
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: SUN      Model: CSM200_R         Rev: 0619
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: VMware   Model: Virtual disk     Rev: 1.0 
Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: VMware   Model: Virtual disk     Rev: 1.0 
Type:   Direct-Access 			 ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 08 Lun: 00
Vendor: VMware   Model: Virtual disk Rev: 1.0 
Type:   Direct-Access 			 ANSI SCSI revision: 02


it is running in a vmware esx 3.0.1 environment with a Sun STK 6140
storage array.

During a disk change the following error is logged by the kernel:

sdc: Current: sense key: Recovered Error
    <<vendor>> ASC=0xe0 ASCQ=0x6ASC=0xe0 ASCQ=0x6
    EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already
    cleared for block 75569857
    Remounting filesystem read-only

I have to reboot and fsck the partition.

Recovered Errors sounds like - there was an error, but the storage
recovered it, by itself - so wy the ext3 failure occured?

The same issue happend on a ubuntu 6.06 lts ( Kernel 2.6.16 ).

All debian sarge with kernel 2.4.27 survived the scsi error.

Is there a setting, to tell the kernel to retry the read or write
operation?

Regards,

Konrad

-- 
Konrad Mauz 
Rechenzentrum
Hochschule Technik, Wirtschaft und Gestaltung
Braunegger-Strasse 55, D 78462 Konstanz                                         
e-mail: kmauz@htwg-konstanz.de
Tel.:   +49 7531 206-472
Fax.:   +49 7531 206-153



--- End Message ---
--- Begin Message ---
Version: 2.6.24-1

On Tue, Sep 08, 2009 at 08:47:21AM +0200, Konrad Mauz wrote:
> On Sat, Aug 15, 2009 at 03:18:44AM +0200, Moritz Muehlenhoff wrote:
> > On Wed, Jul 02, 2008 at 11:52:08AM +0200, Konrad Mauz wrote:
> > > Package: linux-image-2.6.18-4-686
> > > Version: 2.6.18.dfsg.1-12etch2
> > > 
> > > Dear debian-kernel-team,
> > > 
> > > During storage maintainance a scsi error occured and stopped the ext3
> > > journal.
> > > 
> > > The setup:
> > > 
> > > Debian etch/i386:
> > > Kernel: Linux homesrv 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007
> > > i686 GNU/Linux
> > 
> > Was this a one time error or did it occur repeatedly? If the latter,
> > did you test more recent kernels? Can defective hardware be ruled
> > out?
> > 
> > Cheers,
> >         Moritz
> 
> Hello Moritz,
> 
> I think you can close the bug report. I've switched to 2.6.24-etchnhalf
> and never had the problem again.
> 
> Thanks for taking care of this problem.

Ok, closing the bug, then.

Cheers,
        Moritz


--- End Message ---

Reply to: