From: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Evms-devel@lists.sourceforge.net
Subject: RFH: ext3 on EVMS on SW-RAID1 problem
Date: Wed, 27 Apr 2005 13:46:48 +0200 [thread overview]
Message-ID: <20050427114648.GA17153@titan.lahn.de> (raw)
Hello and help!
One of our university fileservers shows strange problems since last
friday. Syslog show the following messages:
attempt to access beyond end of device
dm-8: rw=0, want=8589934592, limit=262142
The strange thing: If I mount a disk-image of that volume via loop,
everything works fine!
The server was running Debian sarge with an unpatched 2.6.11.6 than, but
is running an 2.6.11.7 now and still shows the same problem.
EVMS is version 2.5.2-1 and DevMapper is version 1.01.00-4.
moradin:/var/tmp# dd if=/dev/evms/bsp2005 of=/var/tmp/bsp2005.e3
262142+0 records in
262142+0 records out
134216704 bytes transferred in 5.012082 seconds (26778633 bytes/sec)
moradin:/var/tmp# mount -o loop /var/tmp/bsp2005.e3 /mnt
moradin:/var/tmp# stat /mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h
File: `/mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h'
Size: 12695 Blocks: 28 IO Block: 4096 regular file
Device: 700h/1792d Inode: 24840 Links: 1
Access: (0640/-rw-r-----) Uid: ( 1000/ pmhahn) Gid: (19992/ bsp2005)
Access: 2005-04-27 13:06:16.000000000 +0200
Modify: 2005-04-13 15:21:57.000000000 +0200
Change: 2005-04-22 08:35:09.000000000 +0200
moradin:/var/tmp# md5sum /mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h
3a5f8185367677ce39f9f8d2a72a2705 /mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h
moradin:~# umount /mnt
moradin:~# mount /dev/evms/bsp2005 /mnt
moradin:~# stat /mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h
File: `/mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h'
Size: 12695 Blocks: 28 IO Block: 4096 regular file
Device: fd08h/64776d Inode: 24840 Links: 1
Access: (0640/-rw-r-----) Uid: ( 1000/ pmhahn) Gid: (19992/ bsp2005)
Access: 2005-04-27 13:06:16.000000000 +0200
Modify: 2005-04-13 15:21:57.000000000 +0200
Change: 2005-04-22 08:35:09.000000000 +0200
moradin:~# md5sum /mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h
error processing /mnt/i386-gnu-linux/tools/lib/gcc-lib/mips-linux/3.3.2/include/stddef.h: failed in buffer_read(fd): mdfile: Input/output error
moradin:~# umount /mnt
bsp2005 is an ext3-filesystem, from which a snapshot bsp2005_snap is
created. They both live in a lvm-region, which is based on a
Software-RAID1 using two partitions of two SCSI discs:
lvm/svs/bsp2005#origin#
lvm/svs/bsp2005
md/md0
sda4
sda
sdb4
sdb
Is something wrong with this setup or is it a known problem? Since the
same solution was working last year without problems, I'm very confused
about this strange error behaviour.
BYtE
Philipp
--
/ / (_)__ __ ____ __ Philipp Hahn
/ /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de
next reply other threads:[~2005-04-27 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 11:46 Philipp Matthias Hahn [this message]
2005-04-28 3:08 ` RFH: ext3 on EVMS on SW-RAID1 problem Chris Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050427114648.GA17153@titan.lahn.de \
--to=pmhahn@titan.lahn.de \
--cc=Evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox