|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 crashes with bus error during installation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Tobias Abt <tabt> |
| Component: | YaST2 | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | coolo |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | entire /var/log subtree | ||
|
Description
Tobias Abt
2007-09-26 22:14:22 UTC
I forgot one detail... The installation was done via network boot per PXE and installation source was NFS from a local server with RC1-DVD iso image loop mounted and exported. Just before YaST2 is started, the network is already initialized in the boot sequence and eth0 is therefore already up when YaST2 starts to look at the network cards. I am not sure whether this makes any difference, but maybe it helps... :-) Could you, please, attach YaST logs? Could you, please, attach the logs? Ideally the logs with all debugging information. See http://en.opensuse.org/Bugs/YaST#The_y2logs_don.27t_seem_to_show_my_problem._Can_that_logging_be_made_any_more_verbose.3F on how to enable verbose logging. The core dump could help as well. this sounds a lot like the xfs corruption bug we saw with RC1 As a matter of fact the root file system is XFS... Before that (10.3RC1), I did not have problems with various (open-)SuSE releases and XFS on that system. I also use XFS on: - private server (SuSE 10.0) - Notebook ThinkPad A30p (10.0, 10.1 and 10.2) - desktop PC at work: (was 10.1, now 10.2) - quite a few more, less frequently used setups Never a problem so far and good performance (especially cyrus-imapd much faster than with ext3)... If you have some idea how to reliably detect whether it is a XFS problem, please tell me. I will have a deeper look then. Yesterday evening I could not see a problem at first glance (dmesg, /var/log/messages), but maybe I overread something. (I will provide more info like the afore mentioned log files tonight...) Created attachment 175331 [details]
entire /var/log subtree
I included the entire /var/log to also have (the few) messages etc.
Well, I had some spare empty partitions, so I made some more tests: 10.3 RC1 on XFS without online repository: same failure in same line 10.3 Beta3 on XFS without online repository: successful installation 10.3 RC1 on ext3 without online repository: successful installation So I would concur with Stephan that it probably is the mentioned XFS bug and I would expect that it was introduced between Beta3 and RC1. Anything else I could provide you with? :-) Thank you! What's status of original xfs corruption bug? Can be this bug marked as duplicate? yes, as this is only RC1 I now did a fresh install of 10.3 GM with XFS root fs on the same system and I did not encounter that error again. It might seem as if the error is resolved IN GM. Therefore I propose to close the bug as "fixed". |