From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [reiserfs-list] lvm-list pointed to reiserfs: fs/lvm-problems?
Date: Wed, 30 May 2001 11:22:44 +0200 [thread overview]
Message-ID: <20010530112244.A30938@sistina.com> (raw)
In-Reply-To: <20010529222304.A4888@mind.bartosch.net>; from peter@bartosch.net on Tue, May 29, 2001 at 10:23:04PM +0200
On Tue, May 29, 2001 at 10:23:04PM +0200, Peter Bartosch wrote:
> Hi!
>
>
> > PB> extend an existing (0.8i) LV)
> >
> > PB> so i created a new kernel (2.4.2) with lvm 0.9.1_beta7
> >
> > Linux-2.4.4 has serious reiserfs bugs fixed.
>
> hmm, i tried to make a LVM patch for it but this fails - yesterday i saw a
> message, that there's somewhere a patch for the 2.4.4 that LVM-sources
> will make a patch
You didn't tell what the failure cause was.
It could likely be the renaming of get_hardblocksize to get_hardsect_size
in the 2.4.4 kernel which hits lvm.c.
The recent CVS software at www.sistina.com has that fix already or
you change it in lvm.c end recompile/reinstall.
Hope this helps.
Regards,
Heinz -- The LVM Guy --
>
> > PB> i created the reiserfs on it, but when i tried to mount it, the mount
> > PB> failed
> > PB> an reiserfsck --rebuild-sb and after that reiserfsck --rebuild-tree
> > PB> clears it and i could mount my LV -- UNTIL the next reboot
> >
> > What kernel messages were ?
> >
> > Sorry, but it looks for me like a lvm problem. Can you test you LV by
> > coping some random data (~ 64 MB) to a file in reliable location and
> > to LV, and compare them (or md5 hashes) after reboot ?
>
> hmm, i haven't really tried another filesystem, maybe i should try ext2?
>
> > Reiserfs error handling not an ideal one. Kernel oops below is a
> > normal :( reaction on damaged data coming from disk.
> >
> > Same reason (damaged data), I think, prevented reiserfs volume from
> > mounting.
>
> yes you're right - but why does it oops when i _only_ want to do an "ls
> -l"?
>
> :wq - until next mail B-), l8r
>
> Peter
> --
> :~~~~~~~~~~~~~~~~~~ peter@bartosch.net ~~~~~~~~~~~~~~~~~~:
> : student of technical computer science :
> : university of applied sciences krefeld (germany) :
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> FD314F21 C7 AE 2F 28 C1 33 71 77 0D 77 CD 6E 58 E9 06 6B
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-30 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010528183105.C924@mind.bartosch.net>
2001-05-29 17:10 ` [linux-lvm] Re: [reiserfs-list] lvm-list pointed to reiserfs: fs/lvm-problems? Alexander Zarochentcev
2001-05-29 20:23 ` Peter Bartosch
2001-05-30 9:22 ` Heinz J. Mauelshagen [this message]
2001-05-30 11:36 ` Alexander Zarochentcev
2001-05-31 18:40 ` Peter Bartosch
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=20010530112244.A30938@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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.