|
Bugzilla – Full Text Bug Listing |
| Summary: | fails to partition mounted drives ... | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Michael Meeks <mmeeks> |
| Component: | YaST2 | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aschnell, dmacvicar, gnome-bugs, kamikazow |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast logs
photo. second attempt logs (starting with no mounts) /var/log/messages to match ... proposed patch for tuning of automounter |
||
|
Description
Michael Meeks
2008-10-21 09:56:14 UTC
Created attachment 246789 [details]
yast logs
Hmm, it's worse than this in fact: I just unmounted all the drivers before running the live-installer. Right at the point that it started deleting & re-making the partitions I got a flurry of nautilus windows and new desktop mount-points showing the new mounts, in all their glory; and the live-installer bombed again - with it's lovable: "System error code was: -1014" ;-) that is some magic ! Screenshot attached for the benefit of un-believers ;-) [ along with a new set of yast2 logs ... ] Created attachment 246793 [details]
photo.
Created attachment 246794 [details]
second attempt logs (starting with no mounts)
Created attachment 246795 [details]
/var/log/messages to match ...
apparently several sets of "killall -9 nautilus" beforehand make life happier here; I finally got an install; do we need some "nautilus-dont-go-mount-crazy" thing we can run before hand to make life happier ? This type of thing has come up before, yast can umount -a the devices. See bug 382158 as well. Arvin, can I get from partitioner a list of partitions which will be either removed or resized according to the proposal? (I mean in a computer-readable form, not the proposal as generated by libstorage) Then they can be unmounted just before partitioner starts partitioning the disk. Jiri - I guess at some level we are fighting nautilus' impulse to mount new partitions as the system detects them [ presumably just after we make them ] - JP is it possible that nautilus is more aggressive than gnome-volume-manager here & thus causing the issue ? Perhaps the problem is that yast2 suggested to re-partition the disks to -exactly- the same geometry as is already there [doh] since it partitioned them last time it failed ;-) and as-such they have a valid file-system inside them post partition (I guess). yast2-storage (when run normal in the installed system) does stop hal to automount devices (see SwitchUiAutomounter in disk_worker.ycp). Calling the same code somewhere in the live-installation might be sufficient. @#9: Live instalaltion must work regardless whther the geometry is the same or changes @#10: Thanks for the hint, I think it makes sense to utilize this code. Anyway, does it unmount drives mounted before YaST was started? I think YaST should - call the code you refer above to avoid further mounting - check which partitions will be erased/resized (*) - unmount those of them which are mounted To achive (*), I need a way to get such partitoins, which interface can I use? Created attachment 251639 [details]
proposed patch for tuning of automounter
Jiri, does that patch look ok for you? Unmounting already mounted devices is more work. AFAIS libstorage would unmount devices if required but not if it thinks its running in the inst-sys. So I think I will need more sophisticated flags for that in libstorage. But no time for 11.1. This interface definitely will help. I think I can unmount the partitions myself for 11.1, but need to know which ones. Can libstorage tell me which partitions are going to be either deleted or resized according to the proposal? No, there isn't a function for that and the target-map does not contain the deleted devices. Hmm, I don't really see how it helps then. If I was doing an installation to a USB stick, I would probably first insert the USB stick and then start YaST (which means it's already mounted when YaST starts). Connecting it later may be a problem, if it is done after the disks detection. The patch makes sense, but solves only a very low part of the cases IMO. Maybe (as a hack for 11.1) I could disable automounter and grep /proc/mounts for /media/ (which is where automounter mounts the disks) and if something is found, tell user to unmount them. Do you think it makes sense? I cannot find any better solution ATM That should be ok for a hack. OK, will do it this way for 11.1. Done. Sorry that given current information live installer can gather there is no better solution possible for 11.1. *** Bug 445058 has been marked as a duplicate of this bug. *** |