From: Andries Brouwer <aebr@win.tue.nl>
To: erik@hensema.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: LVM/Device mapper breaks with -mm (was: Re: 2.5.66-mm1)
Date: Wed, 26 Mar 2003 14:48:34 +0100 [thread overview]
Message-ID: <20030326134834.GA11173@win.tue.nl> (raw)
In-Reply-To: <slrnb8373s.19a.usenet@bender.home.hensema.net>
On Wed, Mar 26, 2003 at 12:26:37PM +0000, Erik Hensema wrote:
> Andrew Morton (akpm@digeo.com) wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.66/2.5.66-mm1/
> LVM or device mapper seems to be broken in -mm. I've only tried the
> following kernels so far:
> 2.5.64 - works
> 2.5.65-mm2 - doesn't work
> 2.5.66 - works
> 2.5.66-mm1 - doesn't work
Probably you are hit by
dev_t-32-bit.patch
[for playing only] change type of dev_t
This is hidden somewhat in the 100+ patches in -mm,
but the kernel is not quite ready yet - that is
why this is labeled "not to be applied, for
playing only". Mostly things work, but some stuff
related to lvm, md, dm, nfs, loop will break
because ioctls use structs with a dev_t field.
You can revert this single patch and probably all will be fine.
More interesting would be to apply
http://marc.theaimsgroup.com/?l=linux-kernel&m=103956089203199&w=3
if possible, and see whether that helps.
You can see some earlier discussion today under a subject
containing the word dm_ioctl.
Andries
next prev parent reply other threads:[~2003-03-26 13:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 9:38 2.5.66-mm1 Andrew Morton
2003-03-26 12:26 ` LVM/Device mapper breaks with -mm (was: Re: 2.5.66-mm1) Erik Hensema
2003-03-26 13:48 ` Andries Brouwer [this message]
2003-03-26 14:33 ` Erik Hensema
2003-03-26 16:03 ` Andries Brouwer
2003-03-26 17:43 ` Joe Thornber
2003-03-26 18:47 ` Joel Becker
2003-03-26 20:52 ` Andries Brouwer
2003-03-26 21:12 ` Joel Becker
2003-03-28 2:08 ` Dave Jones
2003-03-28 2:06 ` 2.5.66-mm1 Ed Tomlinson
2003-03-28 4:59 ` 2.5.66-mm1 Andrew Morton
2003-03-28 10:45 ` 2.5.66-mm1 Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303281139500.6678-100000@localhost.localdom ain>
2003-03-28 14:26 ` 2.5.66-mm1 Mike Galbraith
2003-03-28 14:56 ` 2.5.66-mm1 Zwane Mwaikambo
2003-03-28 15:25 ` 2.5.66-mm1 Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303281619530.9943-100000@localhost.localdom ain>
2003-03-28 16:05 ` 2.5.66-mm1 Mike Galbraith
[not found] ` <Pine.LNX.4.50.0303280942420.2884-100000@montezuma.mastecen de.com>
2003-03-28 16:01 ` 2.5.66-mm1 Mike Galbraith
2003-03-26 13:21 LVM/Device mapper breaks with -mm (was: Re: 2.5.66-mm1) Shane Shrybman
2003-03-28 8:30 Andries.Brouwer
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=20030326134834.GA11173@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=erik@hensema.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
all inboxes | Powered by JetHome®