2003-February Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
- re: [linux-lvm] High level architecture (Long),
Greg Freemyer
- [linux-lvm] vgimport problem,
Dieter Stueken
- Re: [linux-lvm] HELP: vgscan segfaults,
Terje Kvernes
- [linux-lvm] LVM and linux kernel 2.4.19,
Sharad Tiwari
- [linux-lvm] RAID5 + LVM stillborn,
Jason Smith
- [linux-lvm] pv_move failed,
Dieter Stueken
- [linux-lvm] Problems with LVM 1.0.6,
Bas
- [linux-lvm] Cannot create any more LV's: "No such device or address",
Bas
- [linux-lvm] Recovering from a hard crash,
Rechenberg, Andrew
- [linux-lvm] "umount" LVM stuff,
David Corbin
- [linux-lvm] lvm mirroring,
Roman Gavrilov
- [linux-lvm] AS 2.1 Latest Kernel and LVM,
Loren Flath
- [linux-lvm] RE: Sharing LVM's via NFS on Redhat 8.0 (nice clarification),
DJ TweeQ
- [linux-lvm] Sharing LVM's via NFS on Redhat 8.0,
DJ TweeQ
- [linux-lvm] Re: How to handle Bad Block relocation with LVM? I actually quite agree. Here are a few points: o A PE is typically less than 0.01% of my total disk space. o Corruption on a drive tends to spread, especially if sectors near the corruption are accessed frequently, so it's best to avoid a whole section of a drive around a bad spot. o In general, I would want to throw away a drive that had so many bad sectors that it's firmware relocation software could no longer handle them. So, my main purpose in relocating the PE is to recover as much data from it as I can before junking the drive.,
Dieter Stueken
- [linux-lvm] Re: LVM 1.0.3 to LVM 1.0.6 upgrade path on a Redhat 8.0 Production System,
DJ TweeQ
- [linux-lvm] Frederic BODART/INT/CHEM/Corp est absent(e).,
Frederic BODART
- [linux-lvm] LVM 1.0.3 to LVM 1.0.6 upgrade path on a Redhat 8.0 Production System,
DJ TweeQ
- [linux-lvm] Re: Sharing Logical Volumes via NFS on Redhat 8.0 & Updating LVM to 1.0.6 on Red,
DJ TweeQ
- [linux-lvm] striping efficiency,
Alexy Khrabrov
- [linux-lvm] dm chunk size is 512?,
Jason Smith
- [linux-lvm] Sharing Logical Volumes via NFS on Redhat 8.0,
DJ TweeQ
- [linux-lvm] Re: Re: Sharing LVM's via NFS on Redhat 8.0 Part2 - SAMBA?,
DJ TweeQ
- [linux-lvm] Sharing LVM's via NFS on Redhat 8.0 Part2 - SAMBA?,
DJ TweeQ
- [linux-lvm] Re: Sharing LVM's via NFS on Redhat 8.0 Part2 - SAMBA?,
DJ TweeQ
- [linux-lvm] Howto Upgrade/Install LVM 1.0.6 patch on Redhat 8.0,
DJ TweeQ
- [linux-lvm] encryption in LVM2,
Jon Bendtsen
- [linux-lvm] list for GFS?,
Jesse Keating
- [linux-lvm] Anonymous CVS updated,
AJ Lewis
- [linux-lvm] Available snapshot chunks known in LVM2,
Jason Smith
- [linux-lvm] Re: How to handle Bad Block relocation with LVM?,
Eric Hopper
- [linux-lvm] enclosure separation/turnoff,
Alexy Khrabrov
- [linux-lvm] How to handle Bad Block relocation with LVM?,
Rocky Lee
- [linux-lvm] vgchange -ay failed with "Bad address",
Axel Reinhold
- [linux-lvm] PV Status NOT available,
Rupert Hair
- [linux-lvm] almost-full snapshots,
Jason Smith
- [linux-lvm] Erroneously formatted PV; 'vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group'...,
Tim-Patrick Märk
- [linux-lvm] Linux Redhat with VA7100,
aicha okirim
- [linux-lvm] erroneously formatted pv; vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group...,
Tim-Patrick Märk
- [linux-lvm] cvs anonymous update problem SOLVED,
Joel Soete
- [linux-lvm] LVM2 lvextend lockup,
Jason Smith
- [linux-lvm] Compliment,
Barr. Williams Sani
- [linux-lvm] LVM 1.0.1 to LVM2 upgrade path,
Dossy
- [linux-lvm] pvmove problem,
B. Dobalina
- [linux-lvm] cannot create a volume group named the same as one already removed,
Tom Georgoulias
- [linux-lvm] CVS changes...,
Heinz J . Mauelshagen
- [linux-lvm] RAID5 bug? [was: Re: raid and lvm],
Jason Smith
- [linux-lvm] ATTENTION NEEDED,
NZANGA JOSEPH MOBUTU.
- [linux-lvm] Snapshot resizing bug (LVM1),
Dale J. Stephenson
- Re: [linux-lvm] resize an ext3 on an LV,
YongChul Kim
- [linux-lvm] New lv cannot span pv's,
Stefan Nilsen
- [linux-lvm] lvm and fai,
Sébastien GALLET
- [linux-lvm] cvs anonymous update problem,
Joel Soete
- [linux-lvm] Help configuring LVM,
Jon Lacey
- [linux-lvm] Re:cramfs ramdisk and rootfs on LVM,
Jan H. van Gils
- [linux-lvm] Ulf Bartelt,
Hartwig zur Nieden
- Re: [linux-lvm] LVM2 for kernels 2.4.20,
Joe Thornber
- [linux-lvm] Severe problem: data lost while adding a partition,
Sander Alberink
- RE: [linux-lvm] LVM rootfs and cramfs as ramdisk,
Jan H. van Gils
- Re: [linux-lvm] Does LVM2 support RAID?,
Heinz J . Mauelshagen