https://bugzilla.novell.com/show_bug.cgi?id=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |fehr@novell.com |ovo.novell.com | -- 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=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c2 melchiaros melchiaros <melchiaros@aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|melchiaros@aol.com | --- Comment #2 from melchiaros melchiaros <melchiaros@aol.com> 2011-06-06 10:15:19 UTC --- Created an attachment (id=433025) --> (http://bugzilla.novell.com/attachment.cgi?id=433025) it is a bundle of logs from yast2 - May be it is the y2log-1 file in there I´ve added all what locks like a log to the archive. Can´t remember if I went back in the installation or start direct a new. When there should be no helpful info in there, I can make the setup again and catch the necessary files. -- 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=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c3 Thomas Fehr <fehr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@novell.com AssignedTo|fehr@novell.com |mmarek@novell.com --- Comment #3 from Thomas Fehr <fehr@novell.com> 2011-06-06 11:02:24 UTC --- The attached y2log file contains an installation using ext4 on /dev/sda3 that did not show the problem. But I was able to reproduce the problem here, so no need to attach further yl2og file. The problem seems that the code in mkfs.btrfs that checks if the device to format is in use is confused by the loop mounts in /proc/mounts where the file the loop is based on does not exist any more in the filesystem. Error message by mkfs.btrfs is: error checking /dev/sda3 mount status Problem is reproducible also on SLES11 SP2. To reproduce it one needs to use an installation method where loop mounts are used by linuxrc (e.g. installation by iso image as a medium). Reassigning to maintainer of btrfs-utils. -- 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=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c4 --- Comment #4 from Thomas Fehr <fehr@novell.com> 2011-06-06 13:34:50 UTC --- JFI: As a workaround one can type "squash=0 loadimage=0" at the kernel command line (labeled "Boot Options:" at install screen) this will prevent linuxrc from using loop devices unless if they are absolutely needed. -- 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=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c7 Bernhard Wiedemann <bwiedemann@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@novell.com --- Comment #7 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-07-01 10:55:38 CEST --- in http://openqa.opensuse.org/opensuse/video/openSUSE-NET-x86_64-Build0093-xfce... I added squash=0 loadimage=0 on the isolinux kernel params and verified in /proc/cmdline that they came in, but while it booted, it still failed with error code -3008. my strace mkfs.btrfs /dev/vda3 supports the analysis in comment #3 -- 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=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c13 --- Comment #13 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-07-01 17:00:56 CEST --- This is an autogenerated message for OBS integration: This bug (697671) was mentioned in https://build.opensuse.org/request/show/75017 Factory / btrfsprogs -- 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=697671 https://bugzilla.novell.com/show_bug.cgi?id=697671#c16 Bernhard Wiedemann <bwiedemann@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #16 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-07-14 08:52:57 CEST --- seen working with Build0120. installation-images had probably not been built before. http://openqa.opensuse.org/results/openSUSE-DVD-i586-Build0120-btrfs now shows a later btrfs bug :) -- 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.