linux-kernel - Re: buffer i/o error

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] [day] [month] [year] [list]

Date:	Wed, 03 Dec 2008 17:52:55 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Andrej Hocevar <and.hocevar@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: buffer i/o error

Andrej Hocevar wrote:
> 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()
[...]
>  [<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.
-- 
Stefan Richter
-=====-==--- ==-- ---==
http://arcgraph.de/sr/
--
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/