From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: GRUB + LVM + XFS?
Date: Tue Jan 15 08:21:01 2002 [thread overview]
Message-ID: <20020115151829.F11005@sistina.com> (raw)
In-Reply-To: <200201080927.g089QVJ00669@hammer.brocade.com>; from ahead@bigpond.net.au on Tue, Jan 08, 2002 at 10:48:11AM +1000
On Tue, Jan 08, 2002 at 10:48:11AM +1000, Adrian Head wrote:
> On Tue, 8 Jan 2002 05:54, Rupa Schomaker wrote:
> > I'm having toubles with the current CVS version of the XFS kernel. I
> > haven't had time to look at it completely, but... it could be:
> >
> > 1) mismatch between userspace and kernel (what LVM is in the XFS
> > kernel? I'm using the debian lvm10 userspace).
> >
> > 2) bad config
> >
> > 3) ???
> >
> > A quick "bt" at boot in kdb shows that devfs is in the call path. No,
> > I haven't had time to write everything down. :( Man, I wish there was
> > an easy to dump the kdb info or an OOPs to disk...
>
> Well all I do is for getting kdb output is to use a serial console and
> another computer - then cut and past then send ;-).
>
> It is very interesting that devfs is referenced - there was a LVM memory
> corruption problem and a patch for LVM/devfs - it can be found here:
> http://marc.theaimsgroup.com/?l=linux-xfs&m=101031443221058&w=2
>
> From my experience it seems that LVM 1.0.1rc4(ish) is way more robust than
> the updated LVM 1.0.1 or even CVS LVM 1.0.1 yesterday.
Do you have some input which particular changes cause it?
Thanks.
> However, not
> everything works as expected with either. You can find a results table for a
> few tests I have conducted here: (of course YMMV)
> http://marc.theaimsgroup.com/?l=linux-lvm&m=100994364215110&w=2
>
> I think you would be very interested in the discussions and activity that has
> been occuring on the linux-xfs & linux-lvm lists at the moment regarding XFS
> and LVM. If you are seeing problems I would be very interested in finding
> out how your problems differ from mine.
>
> --
> Adrian Head
>
> (Public Key available on request.)
>
> _______________________________________________
> 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
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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:[~2002-01-15 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1010427293.29260.3.camel@UberGeek>
[not found] ` <m3666ej5t2.fsf@shakti.rupa.com>
2002-01-07 18:46 ` [linux-lvm] Re: GRUB + LVM + XFS? Adrian Head
2002-01-08 3:26 ` Adrian Head
2002-01-08 5:43 ` Eric M. Hopper
2002-01-15 8:21 ` Heinz J . Mauelshagen [this message]
2002-01-15 9:17 ` Adrian Head
2002-01-15 9:36 ` Patrick Caulfield
2002-01-15 9:58 ` Adrian Head
2002-01-15 10:01 ` Adrian Head
2002-01-08 7:33 Adrian Head
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=20020115151829.F11005@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.