Skip to contentSkip to conversation

buffer i/o error

DISCUSSION Andrej Hocevar 2 participants 2 messages Dec 3, 2008

lore
Share & tools
lore
#0 lore raw

Hello, I suddenly realized that one of my external disks (a Western Digital MyBook usb disk) wasn't accessible anymore. Then I found the following message. There seems to have been no apparent damage or loss, but I'm reporting it anyway.

Regards,

Andrej Hocevar

------------[ cut here ]------------
WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x20/0x69()
Modules linked in: nls_cp437 isofs loop xt_state xt_tcpudp iptable_filter
ip_tables x_tables nf_nat_ftp nf_nat nf_conntrack_ipv4 nfDec  3 16:24:58 stoa
kernel: Pid: 12202, comm: umount Not tainted 2.6.27.7home #1
 [<c0118eae>] warn_on_slowpath+0x40/0x63
 [<c0151c22>] check_object+0x10d/0x197
 [<c0152e76>] __slab_alloc+0x366/0x3de
 [<c011394b>] place_entity+0x9c/0xde
 [<c011388f>] update_curr+0x3d/0x5d
 [<c01149a0>] __dequeue_entity+0x1f/0x71
 [<c01158f0>] pick_next_task_fair+0xdf/0xe9
 [<c016fe20>] mark_buffer_dirty+0x20/0x69
 [<c0198b88>] journal_update_superblock+0x4a/0x7c
 [<c0198e00>] journal_destroy+0x101/0x146
 [<c0126742>] autoremove_wake_function+0x0/0x2d
 [<c018fcfd>] ext3_put_super+0x1f/0x147
 [<c01578a6>] generic_shutdown_super+0x4a/0xad
 [<c0157915>] kill_block_super+0xc/0x1b
 [<c0157983>] deactivate_super+0x2c/0x3f
 [<c0167772>] sys_umount+0x253/0x279
 [<c01677a3>] sys_oldumount+0xb/0xe
 [<c0102b36>] syscall_call+0x7/0xb
 [<c0310000>] via_ircc_open+0xfa/0x59b
 =======================
---[ end trace af37a7a2247422ea ]---

Linux stoa 2.6.27.7home #1 Sun Nov 23 14:37:46 CET 2008 i686 GNU/Linux

Gnu C                  4.3.2
Gnu make               3.81
binutils               2.18.0.20080103
util-linux             2.13.1.1
mount                  2.13.1
module-init-tools      found
PPP                    2.4.4
Linux C Library        2.7
Dynamic linker (ldd)   2.7
Procps                 3.2.7
Console-tools          0.2.3
Sh-utils               6.10
udev                   125
Modules Loaded         nls_cp437 isofs loop xt_state xt_tcpudp iptable_filter

ip_tables x_tables nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_conntrack_ftp nf_conntrack snd_mixer_oss ppdev lp cpufreq_stats fuse sr_mod sbp2 snd_intel8x0 snd_ac97_codec ac97_bus 8250_pci 8250 snd_pcm snd_timer rng_core serial_core snd_page_alloc video output parport_pc parport sd_mod evdev ide_cd_mod cdrom ide_disk usb_storage usbhid scsi_mod piix ohci1394 ide_core ieee1394 ehci_hcd uhci_hcd usbcore unix

--
www.ljudmila.org/ludliteratura

#1 lore raw
Quoted 12 lines · Andrej Hocevar

Hello, I suddenly realized that one of my external disks (a Western Digital MyBook usb disk) wasn't accessible anymore. Then I found the following message. There seems to have been no apparent damage or loss, but I'm reporting it anyway.

Regards,

Andrej Hocevar

------------[ cut here ]------------
WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x20/0x69()

[...]

Quoted 7 lines
 [<c016fe20>] mark_buffer_dirty+0x20/0x69
 [<c0198b88>] journal_update_superblock+0x4a/0x7c
 [<c0198e00>] journal_destroy+0x101/0x146
 [<c0126742>] autoremove_wake_function+0x0/0x2d
 [<c018fcfd>] ext3_put_super+0x1f/0x147
 [<c01578a6>] generic_shutdown_super+0x4a/0xad
 [<c0157915>] kill_block_super+0xc/0x1b

[...]

This warning typically happens when the connection to a disk was lost. Alas it doesn't tell /why/ the connection was lost.

http://kerneloops.org/guilty.php?guilty=journal_update_superblock has more of this sort.

Signature · 3 lines
Stefan Richter
-=====-==--- ==-- ---==
http://arcgraph.de/sr/