linux-kernel - Resierfs random corruptions (probably related to cryptsetup or LVM)

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

Date:	Mon, 10 May 2010 17:08:49 +0300
From:	Dmitry Nezhevenko <dion@...ex.net>
To:	linux-kernel@...r.kernel.org
Subject: Resierfs random corruptions (probably related to cryptsetup or LVM)

Hi,

I'm experiencing some strange messages in kernel log:

[79096.365936] REISERFS warning: reiserfs-5090 is_tree_node: node level
32768 does not match to the expected one 1
[79096.365946] REISERFS error (device dm-3): vs-5150 search_by_key:
invalid format found in block 885035. Fsck?
[79096.365952] REISERFS (device dm-3): Remounting filesystem read-only
[79096.365961] REISERFS error (device dm-3): vs-13070
reiserfs_read_locked_inode: i/o failure occurred trying to find stat data
of [6413 109227 0x0 SD]

Hardware is an ASUS F6A laptop with one ST9250320AS HDD. It's configured
cryptsetup device with LUKS key and LVM on top of it. According to SMART
everything is okay with HDD, Reallocated_Sector_Ct is zero.

This happens very rarely (once per month)  so I don't know a way to reproduce 
it. Just reboot with fsck fixes it for a while. Also it looks that exact
volume is not important. This it happens with /usr but iirc same was with
/home (same LVM volume group).

I've googled and found some related threads here but related to ~2.6.19 kernel.
But currently I'm using debian's 2.6.32. 

Any ideas? 

-- 
WBR, Dmitry
--
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/