Skip to contentSkip to conversation

Revised petition WAS: LVM in stock kernel!?

linux-lvm Andreas Dilger 6 participants 7 messages Aug 27, 1999 1 message not in the archive

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines · Shane

- Integration with IBM's ADSM backup allows Linux machines to be backed up "snapshot" style by simply syncing volumes and grabbing volume data.

I would like to learn specifically what this is before we post this list anywhere. I don't know of any "integration" with ADSM and Linux LVM. I don't think the current LVM supports mirrored LVs, so there is no possibility of a snapshot of a filesystem...

Quoted 2 lines

- The ability to add a sort of volume log allows almost instant volume resyncing while maintaining an active data volume.

I don't think this is currently possible either with Linux LVM... Let's stick with what works before we go talking about features that don't exist yet.

You can add me as a strong supporter of LVM for Linux. I think any OS that doesn't have LVM these days is a pain in the a**.

Cheers, Andreas

Signature · 4 lines
Andreas Dilger  University of Calgary \ "If a man ate a pound of pasta and
                Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \  cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/      hungry?" -- Dogbert
#1 lore raw

I completely agree with Andreas, snapshots and volume logs are a feature of veritas vxfs (journaled filesystem) not veritas LVM.

Quoted 26 lines · Andreas Dilger
Quoted 2 lines · Shane

- Integration with IBM's ADSM backup allows Linux machines to be backed up "snapshot" style by simply syncing volumes and grabbing volume data.

I would like to learn specifically what this is before we post this list anywhere. I don't know of any "integration" with ADSM and Linux LVM. I don't think the current LVM supports mirrored LVs, so there is no possibility of a snapshot of a filesystem...

Quoted 2 lines

- The ability to add a sort of volume log allows almost instant volume resyncing while maintaining an active data volume.

I don't think this is currently possible either with Linux LVM... Let's stick with what works before we go talking about features that don't exist yet.

You can add me as a strong supporter of LVM for Linux. I think any OS that doesn't have LVM these days is a pain in the a**.

Cheers, Andreas

Signature · 4 lines
Andreas Dilger  University of Calgary \ "If a man ate a pound of pasta and
                Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \  cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/      hungry?" -- Dogbert
Signature · 2 lines
Luca Berra -- [email protected]
    Communications Media & Services S.r.l.
#2 lore raw
Quoted 16 lines

I completely agree with Andreas, snapshots and volume logs are a feature of veritas vxfs (journaled filesystem) not veritas LVM.

Quoted 11 lines · Andreas Dilger
Quoted 2 lines · Shane

- Integration with IBM's ADSM backup allows Linux machines to be backed up "snapshot" style by simply syncing volumes and grabbing volume data.

I would like to learn specifically what this is before we post this list anywhere. I don't know of any "integration" with ADSM and Linux LVM. I don't think the current LVM supports mirrored LVs, so there is no possibility of a snapshot of a filesystem...

Quoted 2 lines

- The ability to add a sort of volume log allows almost instant volume resyncing while maintaining an active data volume.

Yep.

Quoted 2 lines
Quoted 2 lines

I don't think this is currently possible either with Linux LVM...

Yes, you are right as far as LVM 0.7 is concerned.

Quoted 3 lines
Quoted 3 lines

Let's
stick with what works before we go talking about features that don't exist yet.

I'm working on LV snapshot support right now.

I'ld like to have it in 0.8 because it would be a block device level feature, which can be used by each and every block device user (FSes/DBMSes/...).

IMO this conforms to the 'better do things generic' approach.

<SNIP>

Regards,
Heinz
--

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Systemmanagement CS-TS T-Nova
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41

                                                 64205 Darmstadt
[email protected]                      Germany
                                                 +49 6151 886-425
                                                          FAX-386

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw
In reply to Andreas Dilger

Since we're petitioning Linus to include 'current' LVM code, I believe that we should make it clear what Linux LVM 'currently' supports. Though a section including future growth would probably be a good idea, since it'd give Linus a good feeling about future support, and also let him know what direction this piece of code is going in.

Of course, include my name on the petition.

[email protected]

Steve Brueggeman

Quoted 20 lines
Quoted 2 lines · Shane

- Integration with IBM's ADSM backup allows Linux machines to be backed up "snapshot" style by simply syncing volumes and grabbing volume data.

I would like to learn specifically what this is before we post this list anywhere. I don't know of any "integration" with ADSM and Linux LVM. I don't think the current LVM supports mirrored LVs, so there is no possibility of a snapshot of a filesystem...

Quoted 2 lines

- The ability to add a sort of volume log allows almost instant volume resyncing while maintaining an active data volume.

I don't think this is currently possible either with Linux LVM... Let's stick with what works before we go talking about features that don't exist yet.

You can add me as a strong supporter of LVM for Linux. I think any OS that doesn't have LVM these days is a pain in the a**.

Cheers, Andreas

#4 lore raw
In reply to Andreas Dilger

-----BEGIN PGP SIGNED MESSAGE-----

Quoted 8 lines · Andreas Dilger
Quoted 2 lines · Shane

- Integration with IBM's ADSM backup allows Linux machines to be backed up "snapshot" style by simply syncing volumes and grabbing volume data.

I would like to learn specifically what this is before we post this list anywhere. I don't know of any "integration" with ADSM and Linux LVM. I don't think the current LVM supports mirrored LVs, so there is no possibility of a snapshot of a filesystem...

I've been able to succesully mirror lvs using the raid0 implmentation along with LVM since I started using it. As for the snapshot backup, in a nutshell, you simply mark a stale mirror (or break the mirror temporarily), and set ADSM to back up the logical volume directly (works fine, and quickly) Again, I've been using the Linux adsm client for almost 2 years now (pays to be an insider with IBM hehehe), and once LVM came out I immediately began testing LV backups. True, a data restore requires a complete rebuild of the mirror, but the client will get it. In some situations this is not optimal (e.g. if you have a filesystem using the LV), but in the case of raw LV access (e.g. Sybase/Oracle/DB2), it works well.

Quoted 7 lines
Quoted 3 lines

- The ability to add a sort of volume log allows almost instant volume resyncing while maintaining an active data volume.

I don't think this is currently possible either with Linux LVM... Let's stick with what works before we go talking about features that don't exist yet.

This is not yet, but I'm working on it ;-)

Quoted 3 lines

You can add me as a strong supporter of LVM for Linux. I think any OS that doesn't have LVM these days is a pain in the a**.

Ditto. Glad to see my name high up on the list.

Quoted 8 lines

Cheers, Andreas

Signature · 4 lines
Andreas Dilger  University of Calgary \ "If a man ate a pound of pasta and
                Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \  cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/      hungry?" -- Dogbert

% %%%%%%%%%%
%% S. Ryan Quick %%%%%%%%%
%%% UNIX Systems Engineer %%%%%%%%
%%%% Phaedo Consulting, Inc. -- Exec VP %%%%%%%
%%%%% %%%%%%
%%%%%% www.phaedo.com/ryan/ [email protected] %%%%%
%%%%%%% ------------ PGP FingerPrint ------------- %%%%
%%%%%%%% CF 19 6B BA 31 8E B8 8E 20 DF 4F 2B 2E 69 81 F5 %%%
%%%%%%%%% ------------------------------------------ %%
%%%%%%%%%% %

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv

iQCVAwUBN8awrvUYDAQiV+tNAQEl5QP/WUQ+eVnMvso5k2gX3sl1+w74W9frkJq5 Zif1KaRd49O+f3WSh/rBLX4wUdK0fk7p5Z4lSjFj45HdrgHPRFqTdhksCAQ+eV2O s02/XcfzWgyM3gnckR8JNvFV9lsNQ+ZZOK0bv6e+crpT+aZaufZRa5caiQXAzEVp rArNfC62Ceg=
=wK8R
-----END PGP SIGNATURE-----

A message that is not in the archive (sent off-list or not yet received): [email protected]. com

#6 lore raw
Quoted 9 lines

I've been able to succesully mirror lvs using the raid0 implmentation along with LVM since I started using it. As for the snapshot backup, in a nutshell, you simply mark a stale mirror (or break the mirror temporarily), and set ADSM to back up the logical volume directly (works fine, and quickly) Again, I've been using the Linux adsm client for almost 2 years now (pays to be an insider with IBM hehehe), and once LVM came out I immediately began testing LV backups. True, a data restore requires a complete rebuild of the mirror, but the client will get it. In some situations this is not optimal (e.g. if you have a filesystem using the LV), but in the case of raw LV access (e.g. Sybase/Oracle/DB2), it works well.

This is not quite the same concept as snapshot filesystems, although you can certainly use it for reliable backups (quiescent filesystems!). With a spare disk you can even use lv and a floating mirror disk to help back up several mirrored devices - attach it to one mirror, sync up, detach and backup, attach to another mirror, sync, etc.

Snapshots (at least the concept that Veritas has described to the world) let you freeze the state of a filesystem as a read-only image while the filesystem itself remains live, but without breaking any mirrors and leaving yourself temporarily in an unmirrored state. All you really need is to be able to freeze a pointer to the metadata, and set the FS into a state such that no disk block can be modified, instead it's always copied on write. Requires suitable filesystem support, of course. Those extra blocks are released only when you're done with the snapshot. Snapshots can live for as long as you want, and there can be several of them active, as long as you have disk space that is.

#7 lore raw

-----BEGIN PGP SIGNED MESSAGE-----

Quoted 8 lines · Mats Wichmann

This is not quite the same concept as snapshot filesystems, although you can certainly use it for reliable backups (quiescent filesystems!). With a spare
disk you can even use lv and a floating mirror disk to help back up several mirrored
devices - attach it to one mirror, sync up, detach and backup, attach to another
mirror, sync, etc.

Now you're with me . . .

Quoted 15 lines

Snapshots (at least the concept that Veritas has described to the world) let you
freeze the state of a filesystem as a read-only image while the filesystem itself
remains live, but without breaking any mirrors and leaving yourself temporarily in
an unmirrored state. All you really need is to be able to freeze a pointer to the
metadata, and set the FS into a state such that no disk block can be modified, instead it's always copied on write. Requires suitable filesystem support, of course. Those extra blocks are released only when you're done with the snapshot.
Snapshots can live for as long as you want, and there can be several of them active, as long as you have disk space that is.

Yeah, ever since Iposted that first message I feared a vxfs backlash when it wasn't what I intended. There are some problems with Veritas concept of snapshots anyway, one of which is that on a vxfs filesystem on a volume with dirty region logging, then snapping a mirror does not really leave the new snap fs as "clean" as you might want it to. This has to dowith the write ordering to the dirty region log on the inital fs... you'l find on large filesystems (>100GB or so that I've noticed anyway), that active data on the primary
volume will cause so much writing to the volume log that the snap extent information hardly gets consulted and the end result can be a snapshot backup of the active filesystem (since vxfs snapshot consults a changelog as it performs the backup), not the snapped filesystem. I hope
to avoid this problem in the Linux LVM by having some sort of volume log write ordering, or maybe including the (for lack of a better term) dirty-region log as a mirror on the snap volume. This is different from the vxfs model mainly because my intention is to be able to essentially create snap mirrors of LVs as most of the data I work with doesn't exist on filesystems anyway.

Quoted 2 lines

% %%%%%%%%%%
%% S. Ryan Quick %%%%%%%%%
%%% UNIX Systems Engineer %%%%%%%%
%%%% Phaedo Consulting, Inc. -- Exec VP %%%%%%%
%%%%% %%%%%%
%%%%%% www.phaedo.com/ryan/ [email protected] %%%%%
%%%%%%% ------------ PGP FingerPrint ------------- %%%%
%%%%%%%% CF 19 6B BA 31 8E B8 8E 20 DF 4F 2B 2E 69 81 F5 %%%
%%%%%%%%% ------------------------------------------ %%
%%%%%%%%%% %

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv

iQCVAwUBN8bkoPUYDAQiV+tNAQE7xAP/VNGd6GEIdMMFdx5FxxwxRe0Lm6QOnGOV lj5/wnbx+zCf0XaVfavmZhWDAhmzXmYHCBcWx53PEMRI1sa3Pn/VONhQQtjW5h8+ ZkY7Qf2IZc/b+C9Z7abFa9OvI3Ub28HJkK67lCzfzG4Tsyuk2FS2dHX1ojdttEeb mgC1DpeOByk=
=AMPT
-----END PGP SIGNATURE-----