Guten Abend, Auf meinem - nicht sooo - alten PC mit neuem openSuse 11.2 erhalte ich beim booten mehrfach die Meldung "Buffer I/O error on device dm-2" (siehe Auszug unten). Trotz dieser Meldung läuft nachher alles normal weiter. Aber ich würde gerne wissen, woher sie kommen und was sie zu bedeuten haben, denn auf den anderen drei ebenfalls neu installierten Maschinen (neuere Modelle mit nur 1 oder 2 HDs) kommen keine solchen Meldungen. Ich hab drei physische HDs, alles (ausser /boot) ist verschlüsselt. Die fstab hänge ich zur Info ganz unten auch noch an. Kann mir jemand sagen, woher die Meldungen kommen, was sie bedeuten, wie ich sie los werde? Vielen Dank. Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com Auszug aus /var/log/boot.msg: ----------------------------- <6>[ 39.175190] loop: module loaded <5>[ 39.303861] REISERFS (device sda1): found reiserfs format "3.6" with standard journal <5>[ 39.303910] REISERFS (device sda1): using ordered data mode <4>[ 39.303914] reiserfs: using flush barriers <5>[ 39.313609] REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>[ 39.314889] REISERFS (device sda1): checking transaction log (sda1) <5>[ 39.470970] REISERFS (device sda1): Using r5 hash to sort names <6>[ 41.117828] BIOS EDD facility v0.16 2004-Jun-25, 3 devices found <4>[ 46.480111] device-mapper: ioctl: unable to remove open device temporary-cryptsetup-784 <4>[ 46.491506] __ratelimit: 2 callbacks suppressed <3>[ 46.491513] Buffer I/O error on device dm-2, logical block 0 <3>[ 46.507662] Buffer I/O error on device dm-2, logical block 1 <3>[ 46.523299] Buffer I/O error on device dm-2, logical block 2 <3>[ 46.538472] Buffer I/O error on device dm-2, logical block 3 <3>[ 46.553656] Buffer I/O error on device dm-2, logical block 4 <3>[ 46.568404] Buffer I/O error on device dm-2, logical block 5 <3>[ 46.582608] Buffer I/O error on device dm-2, logical block 6 <3>[ 46.596331] Buffer I/O error on device dm-2, logical block 7 <3>[ 46.609600] Buffer I/O error on device dm-2, logical block 8 <3>[ 46.622478] Buffer I/O error on device dm-2, logical block 9 <5>[ 48.632092] REISERFS (device dm-2): found reiserfs format "3.6" with standard journal <5>[ 48.632138] REISERFS (device dm-2): using ordered data mode <4>[ 48.632141] reiserfs: using flush barriers <5>[ 48.663997] REISERFS (device dm-2): journal params: device dm-2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>[ 48.665292] REISERFS (device dm-2): checking transaction log (dm-2) <5>[ 48.903215] REISERFS (device dm-2): Using r5 hash to sort names <5>[ 52.503555] REISERFS (device dm-3): found reiserfs format "3.6" with standard journal <5>[ 52.503598] REISERFS (device dm-3): using ordered data mode <4>[ 52.503601] reiserfs: using flush barriers <5>[ 52.521939] REISERFS (device dm-3): journal params: device dm-3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>[ 52.523566] REISERFS (device dm-3): checking transaction log (dm-3) <5>[ 52.589214] REISERFS (device dm-3): Using r5 hash to sort names <5>[ 59.188325] REISERFS (device dm-4): found reiserfs format "3.6" with standard journal <5>[ 59.188374] REISERFS (device dm-4): using ordered data mode <4>[ 59.188377] reiserfs: using flush barriers <5>[ 59.208185] REISERFS (device dm-4): journal params: device dm-4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>[ 59.209834] REISERFS (device dm-4): checking transaction log (dm-4) <5>[ 59.282029] REISERFS (device dm-4): Using r5 hash to sort names fstab: ------ /dev/disk/by-id/ata-WDC_[und-hier-die-weitere-ID]-part1 /boot reiserfs acl,user_xattr 1 2 /dev/mapper/cr_hda1 swap swap defaults 0 0 /dev/mapper/root / reiserfs acl,user_xattr 1 1 /dev/mapper/cr_hda2 /home reiserfs acl,user_xattr,noauto 0 0 /dev/mapper/cr_sda3 /digikam_alben reiserfs acl,user_xattr,noauto 0 0 /dev/mapper/cr_hdc1 /diverses reiserfs acl,user_xattr,noauto 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um eine Liste aller verfuegbaren Kommandos zu bekommen, schicken Sie eine Mail an: opensuse-de+help@opensuse.org
On 27.11.2009, Daniel Bauer wrote:
<3>[ 46.491513] Buffer I/O error on device dm-2, logical block 0
Das ist schon eine Weile bekannt, ich kopiere die Mail vom cryptsetup maintainer einfach mal hier rein: --------- cut here ---------------------------- * Subject: Re: Question on LUKS master key digest and its effect on security * From: Milan Broz <mbroz@xxxxxxxxxx> * Date: Sat, 19 Sep 2009 21:00:32 +0200 * In-reply-to: <20090919165148.GA5619@xxxxxxxxxxxxxxxxx> * References: <200909182039.44953.dmcrypt-list@xxxxxxxxxxxx> * Sender: dm-crypt-bounces@xxxxxxxx * User-agent: Thunderbird 2.0.0.23 (X11/20090812) Heinz Diehl wrote:
On 18.09.2009, Milan Broz wrote:
As reported some weeks ago, the buffer i/o errors are still present with the latest svn code (from today):
[....] Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 32
This is not cryptsetup bug but interference with badly written udev rules or programs reacting to uevents (like DeviceKit etc) which tries to open/scan temporary/keyslot cryptstetup devices (I see this messages too with dracut in Fedora). (In 1.0.7 was 1 sec timeout which was removed, that caused these messages to appear more often. But this timeout slowed down keyslot scan unnecessarily.) You can easily verify that - run command which produces this messages like cryptsetup luksOpen with --debug, and if you see WARNING: other process locked internal device ... it is this problem. These messages are ugly, but there is actually no problem - if cryptsetup detects that someone locks internal keyslot device by opening it (usually it is blkid), it remaps it to error target, so that program receives io errors on read and quickly closes it. (unfortunately kernel log this read error to syslog.) (I hope that udev problems will be solved soon by switching device-mapper to use udev directly and maintain its own, correctly written, rules.) Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt ------------- cut here -------------------------------------- Mach' mal ein Update von udev und device-mapper. -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um eine Liste aller verfuegbaren Kommandos zu bekommen, schicken Sie eine Mail an: opensuse-de+help@opensuse.org
participants (2)
-
Daniel Bauer
-
Heinz Diehl