https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Severity|Normal |Major -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c2 --- Comment #2 from Joschi Brauchle 2013-01-20 17:51:03 UTC --- Exit code 5 means: "can't remove volume group containing logical volumes" It looks like YaST does not remove logical volumes contained inside the vgroup first. Hence, either remove them prior to removing a volume group or use the "--force" parameter with the call of 'vgremove'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c4 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|joschibrauchle@gmx.de | --- Comment #4 from Joschi Brauchle 2013-01-21 11:18:45 UTC --- Created an attachment (id=521102) --> (http://bugzilla.novell.com/attachment.cgi?id=521102) YaST2 logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c6 --- Comment #6 from Joschi Brauchle 2013-01-23 21:07:11 UTC --- Yes, you are right. I apologize for pointing the finger at YaST too quickly! I actually assumed YaST was not removing LVs simply due to the explanation of exit code 5, without looking at the logs. I see that lvm2.02.98 is the latest version out there. Hence I sent an email to the linux-lvm list. Should this report be reassigned? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c8 --- Comment #8 from Joschi Brauchle 2013-01-24 11:18:39 UTC --- After some IRC discussions, the problem seems to be that in openSUSE 12.3 installation, /etc/lvm to /mounts/mp_0000/etc/lvm/, which is mounted read-only. In openSUSE 12.2 installation, /etc/lvm was writable! See IRC log below: ---------------- [12:04] jbrauchle: hi - do you have writeble /etc/lvm ? [12:07] <jbrauchle> No, /etc/lvm symlinks to /mounts/mp_0000/etc/lvm/, which is mounted read-only [12:07] yep - that's the problem [12:08] there is missing error message [12:08] disable -A n [12:08] with your vgremove [12:08] <mcsontos> jbrauchle, you need to edit lvm.conf so backup_dir and archive_dir points to R/W location [12:08] <mcsontos> jbrauchle, that should do the trick [12:09] <mcsontos> More than that, I am surprised lvremoves succeeded [12:09] mcsontos: he uses -A n for lvremove [12:09] <mcsontos> OIC [12:10] <jbrauchle> ok... so then, if I understand correctly: If openSUSE 12.2 installation works OK with exactly the same setup (root FS also read-only), there must be something wrong lvm.conf? [12:11] <mcsontos> jbrauchle, or in installer [12:11] <mcsontos> jbrauchle, e.g. FS mounted RO while it used to be R/W [12:12] jbrauchle: there could be backup{archive=0} in lvm.conf [12:12] <mcsontos> or so [12:12] <jbrauchle> ok thanks! I will double check the difference from 12.2 to 12.3 [12:12] jbrauchle: any backup{backup=0} as well [12:12] (and) [12:14] <jbrauchle> ok, you're right. On 12.2 /etc/lvm is writeable! ---------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

From my limited knowledge of whats happening, I understand that LVM a) needs a writable path to store archives and backups of metadata. Usually

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c11 --- Comment #11 from Joschi Brauchle 2013-02-20 14:54:05 UTC --- Well, as I can't view bnc#781402 I can't judge if its similar... this defaults to /etc/lvm/{archive,backup}, but this is mounted read-only in the inst-sys of 12.3 (was read-write in 12.2) OR b) must be told to not create archives or backups of metadata in /etc/lvm.conf like so: ------------ backup { # Should we maintain a backup of the current metadata configuration ? # Use 1 for Yes; 0 for No. # Think very hard before turning this off! backup = 0 # Should we maintain an archive of old metadata configurations. # Use 1 for Yes; 0 for No. # On by default. Think very hard before turning this off. archive = 0 } ------------ So I guess option a) would be more sane... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c13 --- Comment #13 from Joschi Brauchle 2013-02-21 16:49:30 UTC --- As /etc/lvm/lvm.conf is also read only, I was unable to change it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c18 --- Comment #18 from Joschi Brauchle 2013-02-28 14:27:23 UTC --- In RC2 is looks like vgremove is called with the '-f' parameter, thus working around this problem. I'm not really convinced this is a real fix, as LVM cannot archive/backup any metadata in the current configuration... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c20 --- Comment #20 from Arvin Schnell 2013-03-22 09:03:27 UTC --- (In reply to comment #18)

In RC2 is looks like vgremove is called with the '-f' parameter, thus working around this problem.

I'm not really convinced this is a real fix, as LVM cannot archive/backup any metadata in the current configuration...

The option -f was added for another issue, see bug #781402. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c22 --- Comment #22 from Joschi Brauchle 2013-03-22 09:17:47 UTC --- I think all the other lvm commands (like lvremove) used by yast use "-A n -f"... hence, there is no archiving of metadata anyway, right? If so, the newly added "-f" option for vgremove solves this problem. If not, possibly make "/etc/lvm" writable again as it was in 12.2 and before...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c24 --- Comment #24 from Joschi Brauchle 2013-03-22 10:06:14 UTC --- No, the "-f" option for vgremove itself does not change archiving options, *but* as archiving is currently not possible due to read-only /etc/lvm/ directory, the "-f" option forces the operation to still proceed. Hence, it indirectly contributes to not archiving metadata in the current setup. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=799501 https://bugzilla.novell.com/show_bug.cgi?id=799501#c Alberto Planas Dominguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.