I give up



Greetings Guys & Dolls;

I give up, I'm whupped.

When I installed FC6, I let it use LVM2 to handle the disks because I was
tired of fighting with the most broken, nasty, evil disk partitioner ever
dreamed up, disk druid. I personally think that abomination was written
by an M$ plant, specifically to poison users against linux.

Now the 64k$ question: While running with LVM2 managed disks, is it
possible to run without dm_mod, the device-mapper? If so, please tell me
how to achieve this.

I rebooted last night, from 2.6.21-rc6 to 2.6.21-rc6 and for some reason
device-mapper went from #252 (cat /proc/devices) to #254, and has also
been seen at #253 in addition to the temporary address of #238 where it
was before that patch was reverted for 2.6.21-rc6

Anytime this changes, the device numbers in a stat report change, and tar
thinks its all new & restarts everything on a 45GB system from a level 0.
My vtape setup only has room for 8.5GB per vtape, so the catchup time is
many days. I can speed that up by temporarily making the vtape bigger in
my amanda.conf, but now the disk itself that the vtapes are on is at 96%
and will not tolerate another such catchup run.

So I'm pleading for either a stable, known address for device-mapper, or a
workaround that will immunize tar against its apparently uncontrolled
wanderings.

Please, pretty please, with sugar and cream in it even, please, give some
stability to this situation....

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
George Washington was first in war, first in peace -- and the first to
have his birthday juggled to make a long weekend.
-- Ashley Cooper
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • LVM cant find devices after adding new disks
    ... the disk the system boots normally. ... with an alternate superblock: ... # This is an example configuration file for the LVM2 system. ... # Configuration of metadata backups and archiving. ...
    (Debian-User)
  • Re: Cannot mount old drive with LVM partition - help!
    ... Basically rename the volgroup00 to volgroup01 or whatever so hdb ... Some LVM prints might help etc. ... Recovering and Renaming the LVM2 Volume ... backup file by examining the LVM2 header on the disk and editing out the ...
    (alt.os.linux)
  • RE: Raid or LVM
    ... I can see is for LVM1, which is not used in the 2.6 Kernel/ Fedora Core ... LVM2 metadata format, then you are limited only by disk space and the ...
    (Fedora)
  • Re: Moving /var/spool/mail
    ... My typical partioning with linux now is a small boot partition, a root partion, and the rest of the disk as a lvm2 physical volume. ...
    (comp.os.linux.networking)
  • Re: Moving /var/spool/mail
    ... and the rest of the disk as a lvm2 physical volume. ... > size - it runs in seconds, while the partition is mounted and in use. ...
    (comp.os.linux.networking)