From: Jan Strohbehn <j.strohbehn@artstor.de>
To: Mauelshagen@Sistina.com, linux-lvm@msede.com
Subject: [linux-lvm] Re: \x7fLVM and I2O
Date: Tue, 12 Sep 2000 01:38:06 +0200 [thread overview]
Message-ID: <39BD6CDE.821BADCE@artstor.de> (raw)
In-Reply-To: 20000907160955.A21633@srv.t-online.de
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
"Heinz J. Mauelshagen" wrote:
>
> 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.
>
> On Wed, Sep 06, 2000 at 08:32:23PM +0200, Michael Marxmeier wrote:
\x7f> >
> > 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 ???
> >
\x7f
next prev parent reply other threads:[~2000-09-11 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-06 18:32 [linux-lvm] LVM and I2O (fwd) Michael Marxmeier
2000-09-07 16:09 ` Heinz J. Mauelshagen
2000-09-11 23:38 ` Jan Strohbehn [this message]
2000-09-11 19:08 ` [linux-lvm] Re: LVM and I2O Andreas Dilger
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=39BD6CDE.821BADCE@artstor.de \
--to=j.strohbehn@artstor.de \
--cc=Mauelshagen@Sistina.com \
--cc=linux-lvm@msede.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.