Debian Bug report logs - #404486
Subject: linux-image-2.6.18-3-686: strange problems with filesystem

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Hendrik Naumann <hn75@gmx.de>

To: submit@bugs.debian.org

Subject: Subject: linux-image-2.6.18-3-686: strange problems with filesystem

Date: Mon, 25 Dec 2006 17:12:02 +0100

[Message part 1 (text/plain, inline)]

Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: critical
Justification: causes serious data loss

*** Please type your report below this line ***

After booting the system the root filesystem (ext3 located on a 
logical volume) contained several files that gave I/O errors. The 
system made a normal shutdown before. 

$ls -la /lib/modules/2.6.18-3-686/nvidia/
insgesamt 0
?--------- ? ? ? ?                ? /lib/modules/2.6.18-3-686/nvidia/nvidia.ko

This file was the first I detected because X was not starting anymore. A

$ du / | grep Fehler
du: Zugriff auf »/usr/share/themes/Qt« nicht möglich: Eingabe-/Ausgabefehler
du: Zugriff auf »/lib/modules/2.6.18-3-686/nvidia/nvidia.ko« nicht möglich: Eingabe-/Ausgabefehler
du: Zugriff auf »/lib/modules/2.6.18-3-686/kernel/drivers/block/floppy.ko« nicht möglich: Eingabe-/Ausgabefehler
du: Zugriff auf »/lib/modules/2.6.18-3-686/kernel/drivers/block/cryptoloop.ko« nicht möglich: Eingabe-/Ausgabefehler
du: Zugriff auf »/var/lib/dpkg/info/auctex.postrm« nicht möglich: Eingabe-/Ausgabefehler

 revealed several other files.

After an fsck of the filesystem (which ended without errors) 
everything at the next boot.

I would not report this if this were the first issue with the 2.6.18 linux
 image. But this is the best documented case. One week ago the filesystem 
was checked on bootup and found corrupt (which very rarely happens to me).
After manually starting fsck and rebooting similar symptoms (I/O
errors) occurred. I had to do second fsck run (always from an other
root partition) which again correct errors. After that run the files that
had I/O errors were gone. I reinstall the packages that contained them.
 



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (20, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to de_DE@euro)

Versions of packages linux-image-2.6.18-3-686 depends on:
ii  coreutils                     5.97-5     The GNU core utilities
ii  debconf [debconf-2.0]         1.5.8      Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85c      tools for generating an initramfs
ii  module-init-tools             3.3-pre3-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-3-686 recommends:
ii  libc6-i686                   2.3.6.ds1-8 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686:
* linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/kimage-is-a-directory:
  linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686:
  linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686:
  linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false
  linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true
  linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686:
  linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686:
  linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk:
* linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686:
  linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false
  linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686:

-- 
PGP ID 65C92061

[Message part 2 (application/pgp-signature, inline)]

Message #12 received at 404486@bugs.debian.org (full text, mbox, reply):

From: Hendrik Naumann <hn75@gmx.de>

To: maks@sternwelten.at

Cc: 404486@bugs.debian.org

Subject: Severity setting for bug 404486

Date: Tue, 2 Jan 2007 15:40:44 +0100

[Message part 1 (text/plain, inline)]

Hi

I would like to know, how the downgrade of this bug is justified. At 
least from my point of view it broke the whole desktop system (makes 
unrelated software on the system (or the whole system) break) twice 
and corrupted the root file system (causes serious data loss) once.

The problem of this bug is reproduceability. This does not make the 
bug less severe, but even more ugly.

I really like to help finding the problem, but I really need some 
guidance.

Hendrik
-- 
PGP ID 65C92061

[Message part 2 (application/pgp-signature, inline)]

Message #17 received at 404486@bugs.debian.org (full text, mbox, reply):

From: Robin Farine <robin.farine@terminus.org>

To: 404486@bugs.debian.org

Subject: intermittent boot failures

Date: Wed, 21 Feb 2007 01:36:35 +0100

Hi,

I am observing similar symptoms when booting etch 
(linux-image-2.6.18-3-686_2.6.18-7) on an Asus P4B533 motherboard. 
With an ext2 root filesystem on an PATA disk, the boot process 
fails sometimes due to errors while loading kernel modules just 
after the initramfs has switched the root filesystem to the PATA 
disk partition.

With a ReiserFS root filesystem, the boot process fails sometimes 
because the filesystem check detects errors before the fs is 
actually mounted.

In both cases, the machine reboots without any problem after a power 
cycle, hence the filesytem is not really corrupted.

This problem never happened when the machine was running an earlier 
version of the kernel in etch (one of 2.6.16 or 2.6.17, I can't say 
for sure).

Robin

Message #24 received at 404486@bugs.debian.org (full text, mbox, reply):

From: Gyuris Szabolcs <szimszon@oregpreshaz.eu>

To: 404486@bugs.debian.org

Subject: The same bug with 2.6.18.dfsg.1-12

Date: Wed, 18 Apr 2007 10:22:54 +0200

[Message part 1 (text/plain, inline)]

I wonder if somebody could help me...

I had the same serious error recently:

Apr 18 05:44:53 int-backup kernel: EXT3-fs error (device md1):
ext3_free_blocks: Freeing blocks not in datazone - block = 340051947,
count = 1
Apr 18 05:44:53 int-backup kernel: Aborting journal on device md1.
Apr 18 05:44:53 int-backup kernel: __journal_remove_journal_head:
freeing b_committed_data
Apr 18 05:44:53 int-backup kernel: __journal_remove_journal_head:
freeing b_committed_data
Apr 18 05:44:53 int-backup kernel: __journal_remove_journal_head:
freeing b_committed_data
Apr 18 05:44:53 int-backup kernel: __journal_remove_journal_head:
freeing b_committed_data
Apr 18 05:44:53 int-backup kernel: __journal_remove_journal_head:
freeing b_committed_data
Apr 18 05:44:53 int-backup kernel: __journal_remove_journal_head:
freeing b_committed_data

...

Apr 18 05:44:53 int-backup kernel: EXT3-fs error (device md1):
ext3_free_blocks: Freeing blocks not in datazone - block = 371627902,
count = 1
Apr 18 05:44:53 int-backup kernel: EXT3-fs error (device md1):
ext3_free_blocks: Freeing blocks not in datazone - block = 1671519576,
count = 1
Apr 18 05:44:53 int-backup kernel: EXT3-fs error (device md1):
ext3_free_blocks: Freeing blocks not in datazone - block = 1191557896,
count = 1
Apr 18 05:44:53 int-backup kernel: EXT3-fs error (device md1):
ext3_free_blocks: Freeing blocks not in datazone - block = 1800208356,
count = 1
Apr 18 05:44:53 int-backup kernel: EXT3-fs error (device md1):
ext3_free_blocks: Freeing blocks not in datazone - block = 2990452676,
count = 1

...

Apr 18 05:44:54 int-backup kernel: Assertion failure in journal_forget()
at fs/jbd/transaction.c:1228: "!jh->b_frozen_data"
Apr 18 05:44:54 int-backup kernel: ------------[ cut here ]------------
Apr 18 05:44:54 int-backup kernel: kernel BUG at fs/jbd/transaction.c:1228!
Apr 18 05:44:54 int-backup kernel: invalid opcode: 0000 [#1]
Apr 18 05:44:54 int-backup kernel: SMP
Apr 18 05:44:54 int-backup kernel: Modules linked in: nfs nfsd exportfs
lockd nfs_acl sunrpc button ac battery ipv6 dm_snapshot dm_mirror dm_mod
loop evdev snd_via82xx gameport snd_ac97_codec snd_ac97_bus snd_pcm
snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd
via82cxxx_audio uart401 floppy sound rtc pcspkr via686a psmouse
serio_raw via_agp agpgart soundcore i2c_isa i2c_viapro parport_pc
i2c_core ac97_codec shpchp pci_hotplug parport ext3 jbd mbcache raid1
md_mod ide_generic ide_cd cdrom sd_mod via82cxxx generic ide_core sata_sil
e100 mii libata scsi_mod uhci_hcd usbcore thermal processor fan
Apr 18 05:44:54 int-backup kernel: CPU:    0
Apr 18 05:44:54 int-backup kernel: EIP:    0060:[<d091dad4>]    Not
tainted VLI
Apr 18 05:44:54 int-backup kernel: EFLAGS: 00010292   (2.6.18-4-686 #1)
Apr 18 05:44:54 int-backup kernel: EIP is at journal_forget+0xa9/0x1d9 [jbd]
Apr 18 05:44:54 int-backup kernel: eax: 0000005c   ebx: c15547bc   ecx:
00000096   edx: 00000000
Apr 18 05:44:54 int-backup kernel: esi: cbb22f40   edi: cf918600   ebp:
c3850600   esp: cfdc7cf8
Apr 18 05:44:54 int-backup kernel: ds: 007b   es: 007b   ss: 0068
Apr 18 05:44:54 int-backup kernel: Process nfsd (pid: 3040, ti=cfdc6000
task=c13e0aa0 task.ti=cfdc6000)
Apr 18 05:44:54 int-backup kernel: Stack: d09225bd d0922248 d09225a8
000004cc d092267b cdd933ec c15547bc c15547bc
Apr 18 05:44:54 int-backup kernel: cf918600 cdd933ec d092011d 00e2c343
c15547bc
cd7480d4 cdd933ec c15547bc
Apr 18 05:44:54 int-backup kernel: d0952644 c15547bc cdd933ec cd7480d4
00e2c343
d095295e c15547bc 00e2c343
Apr 18 05:44:54 int-backup kernel: Call Trace:
Apr 18 05:44:54 int-backup kernel: [<d092011d>] journal_revoke+0xd1/0xf5
[jbd]
Apr 18 05:44:54 int-backup kernel: [<d0952644>] ext3_forget+0x7a/0xb3 [ext3]
Apr 18 05:44:54 int-backup kernel: [<d095295e>]
ext3_free_branches+0xd4/0x1a9 [ext3]
Apr 18 05:44:54 int-backup kernel: [<d095294c>]
ext3_free_branches+0xc2/0x1a9 [ext3]
Apr 18 05:44:54 int-backup kernel: [<d095294c>]
ext3_free_branches+0xc2/0x1a9 [ext3]
Apr 18 05:44:54 int-backup kernel: [<d0953117>]
ext3_truncate+0x6e4/0x79a [ext3]Apr 18 05:44:54 int-backup kernel:
[<c015be29>] __getblk+0x27/0x266
Apr 18 05:44:54 int-backup kernel: [<d091cabb>]
do_get_write_access+0x435/0x462
[jbd]
Apr 18 05:44:54 int-backup kernel: [<c0147e1e>] truncate_inode_pages+0x9/0xf
Apr 18 05:44:54 int-backup kernel: [<c014d1e2>] vmtruncate+0xc4/0xe2
Apr 18 05:44:54 int-backup kernel: [<c016fd9f>] inode_setattr+0x59/0x165
Apr 18 05:44:54 int-backup kernel: [<d0953fbd>] ext3_setattr+0x17e/0x1d8
[ext3]
Apr 18 05:44:54 int-backup kernel: [<c016ffd8>] notify_change+0x12d/0x2c1
Apr 18 05:44:54 int-backup kernel: [<d0bafb28>] nfsd_setattr+0x329/0x49d
[nfsd]
Apr 18 05:44:54 int-backup kernel: [<d0bb5524>]
nfsd3_proc_setattr+0x7c/0x85 [nfsd]
Apr 18 05:44:54 int-backup kernel: [<d0bac0cb>] nfsd_dispatch+0xbb/0x170
[nfsd]
Apr 18 05:44:54 int-backup kernel: [<d0b5d4c9>] svc_process+0x3b9/0x614
[sunrpc]Apr 18 05:44:54 int-backup kernel: [<d0bac5c5>] nfsd+0x1ab/0x30a
[nfsd]
Apr 18 05:44:54 int-backup kernel: [<d0bac41a>] nfsd+0x0/0x30a [nfsd]
Apr 18 05:44:54 int-backup kernel: [<c0101005>] kernel_thread_helper+0x5/0xb
Apr 18 05:44:54 int-backup kernel: Code: 02 0f 85 a5 00 00 00 83 7e 10
00 74 29
68 7b 26 92 d0 68 cc 04 00 00 68 a8 25 92 d0 68 48 22 92 d0 68 bd 25 92
d0 e8 96 fe 7f ef <0f> 0b cc 04 a8 25 92 d0 83 c4 14 90 0f ba 33 01 90
0f ba 33 13
Apr 18 05:44:54 int-backup kernel: EIP: [<d091dad4>]
journal_forget+0xa9/0x1d9 [jbd] SS:ESP 0068:cfdc7cf8

cpu:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 10
cpu MHz         : 1000.091
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 mmx fxsr sse up
bogomips        : 2002.11

I'm using this PC as nfs backup server with SIL3112 sata+sw raid0+2x
500GB ST3500630NS

[smime.p7s (application/x-pkcs7-signature, attachment)]

Message #29 received at 404486@bugs.debian.org (full text, mbox, reply):

From: Frank Isemann <f.isemann@xenbyte.com>

To: 404486@bugs.debian.org

Subject: Subject: linux-image-2.6.18-3-686: strange problems with filesystem

Date: Fri, 06 Jul 2007 18:14:35 +0200

Hi,

same Problem here, but im using the linux-image-2.6.18-4-xen-amd64 
(2.6.18.dfsg.1-12etch2)

Got strange Filesystem Errors ( EXT3 and EXT2 ) like
-------

Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 5865475 was part of the orphaned inode list.  IGNORED.
Inode 5865476 was part of the orphaned inode list.  IGNORED.
Inode 5865477 was part of the orphaned inode list.  IGNORED.
Inode 5865478 was part of the orphaned inode list.  IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity

Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (17557118, counted=17557086).
Fix? no

Inode bitmap differences:  -(5865474--5865478)
Fix? no

Free inodes count wrong (9525073, counted=9525063).
Fix? no
---

and many more... ;-)


This Errors occurs when i create Files for example. But they hide if i 
delete them again. Just looks like a problem with the Meta Data or 
something else.

Im using PATA and SATA Disks ( Two of the SATA Discs are combined to a 
Raid1 via MDADM and are using LVM for our vServers ) and the Filesystem 
Errors are on both types.


lspci:

00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller 
(rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller 
(rev a1)

Is it a Controller/Hardware Problem?


Does someone have a Workaround or somthing to solve this Error?



Greetings,
Frank

Message #34 received at 404486@bugs.debian.org (full text, mbox, reply):

From: Moritz Muehlenhoff <jmm@inutil.org>

To: Hendrik Naumann <hn75@gmx.de>

Cc: 404486@bugs.debian.org, jmm@debian.org

Subject: Re: Subject: linux-image-2.6.18-3-686: strange problems with filesystem

Date: Thu, 4 Dec 2008 23:18:52 +0100

On Mon, Dec 25, 2006 at 05:12:02PM +0100, Hendrik Naumann wrote:

> I would not report this if this were the first issue with the 2.6.18 linux
>  image. But this is the best documented case. One week ago the filesystem 
> was checked on bootup and found corrupt (which very rarely happens to me).
> After manually starting fsck and rebooting similar symptoms (I/O
> errors) occurred. I had to do second fsck run (always from an other
> root partition) which again correct errors. After that run the files that
> had I/O errors were gone. I reinstall the packages that contained them.

Does this error still occur with more recent kernel versions?

Cheers,
        Moritz

Message #39 received at 404486@bugs.debian.org (full text, mbox, reply):

From: Hendrik Naumann <hn75@gmx.de>

To: Moritz Muehlenhoff <jmm@inutil.org>

Cc: 404486@bugs.debian.org, jmm@debian.org

Subject: Re: Subject: linux-image-2.6.18-3-686: strange problems with filesystem

Date: Wed, 10 Dec 2008 13:44:42 +0100

[Message part 1 (text/plain, inline)]

Hi

> Does this error still occur with more recent kernel versions?

On my systems those errors did not occur since then.

Cheers

Hendrik
-- 
PGP ID 65C92061

[Message part 2 (application/pgp-signature, inline)]

Message #44 received at 404486-done@bugs.debian.org (full text, mbox, reply):

From: Moritz Muehlenhoff <jmm@inutil.org>

To: Hendrik Naumann <hn75@gmx.de>

Cc: 404486-done@bugs.debian.org

Subject: Re: Subject: linux-image-2.6.18-3-686: strange problems with filesystem

Date: Sat, 13 Dec 2008 10:52:58 +0100

On Wed, Dec 10, 2008 at 01:44:42PM +0100, Hendrik Naumann wrote:
> Hi
> 
> > Does this error still occur with more recent kernel versions?
> 
> On my systems those errors did not occur since then.

Ok, closing.

Cheers,
        Moritz

> 
> Cheers
> 
> Hendrik
> -- 
> PGP ID 65C92061

Send a report that this bug log contains spam.