still problems with removing "non existant" dead snapshots :/
I take a snapshot every hour, every 8 hour, eveyr day, and every week. I've got 4 "equal" scripts to do the work, the only difference is the snapshot name and the mountpoint.
However, when i try to remove the old and unmounted snapshot, i sometimes
get an error message. Like one in every 10 times.
I get messages like:
--------------------
lvremove -- can't remove open snapshot logical volume "/dev/optVG/1hour_snapshot_opt_1035237601"
And:
----
lvremove -- ERROR "lv_release(): LV number" releasing logical volume "/dev/optVG/1hour_snapshot_opt_1035324001"
If i use lvdisplay on them, i get a message like
------------------------------------------------
ve:/dev/optVG# lvdisplay /dev/optVG/1hour_snapshot_opt_1035* lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035324001" doesn't exist
lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035345601" doesn't exist
lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035352801" doesn't exist
lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035381601" doesn't exist
lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035410401" doesn't exist
lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035432001" doesn't exist
lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035439201" doesn't exist
The problem is that these snapshots take up space. Most take 1GB, since thats what they
are created with, but some take more, since i run some scripts to ensure that they dont
reach 100% so they are always readable.
I can remove the "files" from /dev/optVG/, but the space is not released until i
restart the VG. Even restarting the VG doesnt remove the "dead" snapshots (the files
in /dev/optVG/)
JonB
Jon,
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.
Regards,
Heinz -- The LVM Guy --
Quoted 58 lines · Jon Bendtsen
I take a snapshot every hour, every 8 hour, eveyr day, and every week. I've got 4 "equal" scripts to do the work, the only difference is the snapshot name and the mountpoint.
However, when i try to remove the old and unmounted snapshot, i sometimes
get an error message. Like one in every 10 times.I get messages like:
--------------------
lvremove -- can't remove open snapshot logical volume "/dev/optVG/1hour_snapshot_opt_1035237601"And:
----
lvremove -- ERROR "lv_release(): LV number" releasing logical volume "/dev/optVG/1hour_snapshot_opt_1035324001"If i use lvdisplay on them, i get a message like
------------------------------------------------ve:/dev/optVG# lvdisplay /dev/optVG/1hour_snapshot_opt_1035* lvdisplay -- logical volume "/dev/optVG/1hour_snapshot_opt_1035324001" doesn't existlvdisplay -- logical volume "
/dev/optVG/1hour_snapshot_opt_1035345601" doesn't existlvdisplay -- logical volume "
/dev/optVG/1hour_snapshot_opt_1035352801" doesn't existlvdisplay -- logical volume "
/dev/optVG/1hour_snapshot_opt_1035381601" doesn't existlvdisplay -- logical volume "
/dev/optVG/1hour_snapshot_opt_1035410401" doesn't existlvdisplay -- logical volume "
/dev/optVG/1hour_snapshot_opt_1035432001" doesn't existlvdisplay -- logical volume "
/dev/optVG/1hour_snapshot_opt_1035439201" doesn't existThe problem is that these snapshots take up space. Most take 1GB, since thats what they
are created with, but some take more, since i run some scripts to ensure that they dont
reach 100% so they are always readable.
I can remove the "files" from/dev/optVG/, but the space is not released until i
restart the VG. Even restarting the VG doesnt remove the "dead" snapshots (the files
in/dev/optVG/)
Quoted 7 lines
JonB
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Quoted 6 lines · Heinz J . Mauelshagen
Jon,
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.
lvm_1.1-rc2.tar.gz on default 2.4.18
JonB
Quoted 9 lines · Jon Bendtsen
Quoted 6 lines · Heinz J . Mauelshagen
Jon,
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.lvm_1.1-rc2.tar.gz on default 2.4.18
This is a discontinued (and buggy) development version.
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
Quoted 10 lines
JonB
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Signature · 15 lines
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Quoted 6 lines · Heinz J . Mauelshagen
Quoted 4 lines · Jon Bendtsen
Quoted 3 lines · Heinz J . Mauelshagen
Jon,
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.lvm_1.1-rc2.tar.gz on default 2.4.18
This is a discontinued (and buggy) development version.
Oh ?? i didnt get that impression from the website, and definately not from ftp://linux.msede.com/lvm/1.1/README
Quoted 1 line
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
it's a production server, so i'll downgrade.
JonB
Quoted 11 lines · Jon Bendtsen
Quoted 10 lines · Heinz J . Mauelshagen
Quoted 8 lines · Jon Bendtsen
Quoted 6 lines · Heinz J . Mauelshagen
Jon,
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
lvm_1.1-rc2.tar.gz on default 2.4.18
This is a discontinued (and buggy) development version.
Oh ?? i didnt get that impression from the website, and definately not from ftp://linux.msede.com/lvm/1.1/README
Sorry, we'll change that.
Quoted 5 lines
Quoted 3 lines
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
it's a production server, so i'll downgrade.
Ok.
Quoted 10 lines
JonB
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Signature · 15 lines
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Quoted 1 line · Heinz J . Mauelshagen
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
Hmmm what are the problems with 1.1-rc2? thats the version I am currently running, 1.0.5 I beleive has a problem with pvmove > 2 gig? or am I rembering the wrong version.
James
Quoted 9 lines · James Hawtin
Quoted 1 line · Heinz J . Mauelshagen
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
Hmmm what are the problems with 1.1-rc2? thats the version I am currently running, 1.0.5 I beleive has a problem with pvmove > 2 gig? or am I rembering the wrong version.
No, there's no such problem in 1.1.
It is just an intermediate development version which got replaced by LVM2/device-mapper.
Use that combination if you want stable, cutting-edge Linux LVM :)
Quoted 10 lines
James
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Signature · 15 lines
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Quoted 5 lines · Heinz J . Mauelshagen
Quoted 4 lines · James Hawtin
On Fri, 25 Oct 2002, Heinz J . Mauelshagen wrote:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
Hmmm what are the problems with 1.1-rc2? thats the version I am currently running, 1.0.5 I beleive has a problem with pvmove > 2 gig? or am I rembering the wrong version.
No, there's no such problem in 1.1.
no no I ment is there a pvmove greater than 2 gig problem with 1.0.5? I seem to rember that was why i upgraded to 1.1-rc2
Quoted 6 lines
It is just an intermediate development version which got replaced by LVM2/device-mapper.
Use that combination if you want stable, cutting-edge Linux LVM :)
Cutting or Bleeding edge?
How painful is the upgrade from 1.1-rc2 to the 2 series (which I have not tried yet). Does it require a complete lvm system rebuild or can it use my old pvs, vgs? Which version is the best to go for? Ie any "known problems" why I should not use the latest....
James
Quoted 11 lines · Heinz J . Mauelshagen
Quoted 9 lines · Jon Bendtsen
Quoted 6 lines · Heinz J . Mauelshagen
Jon,
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.lvm_1.1-rc2.tar.gz on default 2.4.18
What is the version on 2.4.19 (stock)?
Quoted 3 lines
This is a discontinued (and buggy) development version.
You should give LVM2 + device-mapper a try or downgrade to 1.0.5.
Signature · 1 line
Luben
Quoted 7 lines · Luben Tuikov
Quoted 6 lines · Heinz J . Mauelshagen
Quoted 4 lines · Jon Bendtsen
Quoted 3 lines · Heinz J . Mauelshagen
Jon,
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.lvm_1.1-rc2.tar.gz on default 2.4.18
What is the version on 2.4.19 (stock)?
1.0.5ish
- Joe
Quoted 6 lines · Heinz J . Mauelshagen
Jon,
which LVM version are you using?
If the driver it is older than 1.0.5 it can be a lockking bug fixed in the recent LVM1 version.
I still get the error, i've got 3 this morning.
umount: /dev/optVG/1hour_snapshot_opt_1035518401: not mounted lvremove -- ERROR "lv_release(): LV number" releasing logical volume "/dev/optVG/1hour_snapshot_opt_1035518401"
I'll use the -debug option and save the output.
JonB