|
Bugzilla – Full Text Bug Listing |
| Summary: | Rebooting into Live-System after installation corrupts installed system | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Stephan Binner <binner> |
| Component: | Live Medium | Assignee: | Stephan Kulow <coolo> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P2 - High | CC: | coolo, jsrain, ms |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Screenshot | ||
|
Description
Stephan Binner
2009-09-08 22:06:07 UTC
Created attachment 317306 [details]
Screenshot
Addendum 2) One has to select a time zone which is East of UTC time zone (like Germany) and one has to keep "Hardware Clock Set to UTC" option unchecked. Failure to follow this addendum will result in a working system. :-) first measure I think is fixing the clock setup, e.g. fix /etc/sysconfig/clock to be UTC and a timezone depending on the language. Still, the live installer needs to set the correct timezone _before_ mounting the target. I'm sure this is done for DVD install, but not for live install. Stephan, I fail to follow you. IMO it is perfectly correct that the system last-mount time is far in the future - I personally don't care about the system (BIOS) time and use NTP, but at the point of time the filesystem gets mounted, NTP can hardly be running. Also, think of moving the system time into the past via firmware/BIOS. Another point: Stefan did one more run of the live CD after the installation (I guess it is also related). Since the live CD mounts the system (well, I'm not sure here how the automounter is configured), the last mount time may come from this run of the live system - when YaST is not involved and the system time may be any kind of strange. I don't think it's perfectly correct for the clock to jump backward unless the system time is wrong. The NTP time is written into the hardware clock and on boot reset. I don't say the file system should be discarded if the clock jumps, but we shouldn't enforce it either. So I think just as we set the keyboard layout once you go through the live installer, we should change the timezone of the live system _before_ we format and mount. What corrupts the filesystem is rebooting to the live system (according to the summary). Since changes in the live system are not persistent, how shall I enforce the timezone in the live system when it boots up? I don't see any way... oh my. I failed to notice that step. So it's indeed something automounting. Sorry for the noise. Anyway, I still think that filesystem needs to survive having been mounted in the future. it should survive it very fine if the journal was correctly synced - e.g. the file system was unmounted. there doesn't seem to be any desktop level automount, but kiwi mounting all file systems ;( Reported upstream, there is really nothing we can do: http://marc.info/?l=linux-ext4&m=125258734308549&w=2 rq20314 - sent the patch also upstream |