LVM and I2O (fwd)

Forwarded message from Jan Strohbehn ...

-------- Original Message --------
Subject: Posting to the LVM Mailing List
Date: Thu, 07 Sep 2000 01:17:17 +0200
From: Jan Strohbehn <[email protected]>
Organization: ArtStor AG

Hello,

I'm trying to get the newest lvm working on I2O-devices, but it seems that the LVM-tools aren't able to recognize them. Has anyone a hint are
an idea why this problem appears ???
Are there any workarounds ???

Thank you very much,
Jan Strohbehn

------------------------------------------------------------------
Today's Fortune:

God rest ye CS students now,
Let nothing you dismay.
The VAX is down and won't be up, Until the first of May.
The program that was due this morn, Won't be postponed, they say.

Oh, tidings of comfort and joy, Comfort and joy,
Oh, tidings of comfort and joy.

The bearings on the drum are gone, The disk is wobbling, too.
We've found a bug in Lisp, and Algol Can't tell false from true.
And now we find that we can't get At Berkeley's 4.2.

(chorus)

Please look at tools/lib/lvm_dir_cache.c and extend the devdir array, tools/lib/lvm_check_dev + tools/lib/lvm_partition_count and extend the valid_majors array.

Regards,
Heinz      -- The LVM guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Bartningstr. 12
                                                  64289 Darmstadt
                                                  Germany
[email protected]                           +49 6151 7103 86
                                                       FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Jan, you write:

Is it possible that the I2O driver/disk itself is not working? Have you tried something like "dd if=/dev/zero of=/dev/{i2o_disk}" to test writes, and "dd if=/dev/{i2o_disk} of=/dev/null" to test reads? The block counts returned from the read and write tests should match... It may be that there is a bad block on the disk, and with LVM it changes the alignment of the FS so that the bad block is under some metadata (read/writted at mke2fs time), whereas the block is unused without LVM.

If that works OK, try sending the end of "strace mke2fs" on your disk to see what exactly is happening.

Cheers, Andreas

Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

Hi,

I have tried all this but the error still appears. Here's the exact error message:

root@bonita:~/ > mke2fs /dev/raid/vol1 mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
100352 inodes, 401408 blocks
20070 blocks (5.00%) reserved for the super user First data block=1
49 block groups
8192 blocks per group, 8192 fragments per group 2048 inodes per group
Superblock backups stored on blocks:

        8193, 24577, 40961, 57345, 73729, 204801, 221185

Writing inode tables: done
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
root@bonita:~/ >

Do you have any other idea why this happens ???

Thanks,
Jan

> >