From: Petro <petro@auctionwatch.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] using 160GB IDE drives under linux with LVM.
Date: Thu Feb 7 18:46:01 2002 [thread overview]
Message-ID: <20020208004550.GC17474@auctionwatch.com> (raw)
In-Reply-To: <ZVUEAKI42A9VT05FDWVWVNI8D875GD.3c631c3a@kadzuki>
On Fri, Feb 08, 2002 at 01:30:50AM +0100, Anders Widman wrote:
> 2002-02-08 00:47:16, Petro <petro@auctionwatch.com> wrote:
>
> >On Thu, Feb 07, 2002 at 05:05:27PM -0600, Kirby C. Bohling wrote:
> >> Why is he brave, it is just a converted 2.4.15-pre5 with a change to the
> >> version number if I remember correctly that has a filesystem bug when
> >> you umount during a reboot. As long as he doesn't reboot and/or umount
> >> his data is save. :-)
> > I thought there were more changes than that.
> > 2.5.x is the development series, not the stable series.
> Not that the 2.4.x series is very stable anyway, with problems of different sorts (APIC for example)..
And problems with the high memory VM (DAMHIK), and...
But if the stable series isn't, how is the unstable going to be
better?
> //Anders
> >
> >> Kirby
> >>
> >> bzcat patch-2.4.15-to-2.5.0.bz2
> >>
> >> diff -urN linux-2.4.15/Makefile linux-2.5.0/Makefile
> >> --- linux-2.4.15/Makefile Thu Nov 22 11:22:58 2001
> >> +++ linux-2.5.0/Makefile Thu Nov 22 22:23:44 2001
> >> @@ -1,7 +1,7 @@
> >> VERSION = 2
> >> -PATCHLEVEL = 4
> >> -SUBLEVEL = 15
> >> -EXTRAVERSION =-greased-turkey
> >> +PATCHLEVEL = 5
> >> +SUBLEVEL = 0
> >> +EXTRAVERSION =
> >>
> >> KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
> >>
> >>
> >> Petro wrote:
> >> >On Thu, Feb 07, 2002 at 04:45:03PM -0600, John Moser wrote:
> >> >
> >> >>Is this specific to 2.4.X kernels? I'm running 2.5.0, and I just noticed
> >> >>that the 160 gig drives I was using are also partitioned at only 128Gigs.
> >> >>
> >> >
> >> > No, it's at the IDE driver level. There are patches to get around
> >> > this that are being considered for the mainstream kernel (Andrei H.
> >> > I believe).
> >> >
> >> > Brave man running 2.5.0, the dot-zero release of a development
> >> > kernel.
> >> >
> >> >
> >> >>-----Original Message-----
> >> >>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
> >> >>Behalf Of Andreas Dilger
> >> >>Sent: Thursday, February 07, 2002 4:18 PM
> >> >>To: linux-lvm@sistina.com
> >> >>Subject: Re: [linux-lvm] using 160GB IDE drives under linux with LVM.
> >> >>
> >> >>
> >> >>On Feb 07, 2002 22:33 +0100, Terje Kvernes wrote:
> >> >>
> >> >>> [ Re: IDE 128GB disk limits ]
> >> >>>
> >> >>> now, I've added SCSI-devices that where > 500GiB with ease into LVM,
> >> >>> but here I stumble. is there some easy solution out there that I've
> >> >>> missed?
> >> >>>
> >> >>> the box currently runs vanilla 2.4.16, only patched with LVM-1.0.1
> >> >>> from 26/11. patches or anything people want to toss at this will be
> >> >>> highly appreciated. we have two of these beasts from Maxtor, and
> >> >>> stand to loose about 60GiB of space, which isn't all that neat.
> >> >>>
> >> >>This is a kernel IDE driver limit. You need to patch with Andre Hedrik's
> >> >>IDE patches to support IDE devices over this size.
> >> >>
> >> >>Cheers, Andreas
> >> >>--
> >> >>Andreas Dilger
> >> >>http://sourceforge.net/projects/ext2resize/
> >> >>http://www-mddsp.enel.ucalgary.ca/People/adilger/
> >> >>
> >> >>
> >> >>_______________________________________________
> >> >>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
> >> >>
> >> >>
> >> >>_______________________________________________
> >> >>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
> >> >>
> >> >
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> >
> >--
> >Share and Enjoy.
> >
> >_______________________________________________
> >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
> >
> >
>
>
>
>
> _______________________________________________
> 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
--
Share and Enjoy.
next prev parent reply other threads:[~2002-02-07 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 15:34 [linux-lvm] using 160GB IDE drives under linux with LVM Terje Kvernes
2002-02-07 16:10 ` Chad C. Walstrom
2002-02-07 21:43 ` Terje Kvernes
2002-02-08 3:20 ` Heinz J . Mauelshagen
2002-02-07 16:14 ` James Hawtin
2002-02-07 21:48 ` Terje Kvernes
2002-02-07 16:18 ` Andreas Dilger
2002-02-07 16:42 ` John Moser
2002-02-07 16:50 ` Petro
2002-02-07 17:07 ` Kirby C. Bohling
2002-02-07 17:47 ` Petro
2002-02-07 18:31 ` Anders Widman
2002-02-07 18:46 ` Petro [this message]
2002-02-08 4:18 ` Anders Widman
2002-02-07 17:03 ` Andreas Dilger
2002-02-07 22:08 ` Terje Kvernes
2002-02-08 2:47 ` William Blunn
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=20020208004550.GC17474@auctionwatch.com \
--to=petro@auctionwatch.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.