Bug 167240 - Update broken, target partition not mounted, warning about low disk space
Summary: Update broken, target partition not mounted, warning about low disk space
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: libzypp (show other bugs)
Version: RC 1
Hardware: Other Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on: 158785
Blocks:
  Show dependency tree / graph
 
Reported: 2006-04-18 08:03 UTC by Mihnea Istinie
Modified: 2006-04-18 16:02 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast logs (321.65 KB, application/x-gtar)
2006-04-18 08:04 UTC, Mihnea Istinie 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mihnea Istinie 2006-04-18 08:03:18 UTC 
I tried to update to RC1 (build 1001)

What I got was a warning that the disk space is low (what I can't imagine, the old system to be updated still had ~10GB free).

Looking in the console at the mounted systems I've seen that only the install system was mounted!
Filesystem            Size  Used Avail Use% Mounted on
/dev/loop0            197M  197M     0 100% /mounts/instsys

At the warning "Disk Space is nearly exhausted, continue with installation" I pressed the "NO" button... but the warning came up again and again, I suppose for each single package.

maybe the bug is also related to 158785 (beside the mount problem)
Comment 1 Mihnea Istinie 2006-04-18 08:04:03 UTC 
Created attachment 78752 [details]
yast logs
Comment 2 Stanislav Visnovsky 2006-04-18 08:09:44 UTC 
Downloading the package description failed.
Comment 5 Christoph Thiel 2006-04-18 11:46:30 UTC 
I'v just tried to update via NFS and ran into the same problem. Logs can be made available on demand.
Comment 6 Jiri Srain 2006-04-18 14:49:42 UTC 
This is caused by removing the root partition from the update proposal (due to problems that are caused by the change of the root partition).

I will update the root partition selection step so that it mounts the target system instead of the proposal.
Comment 7 Jiri Srain 2006-04-18 16:02:47 UTC 
Fixed in SVN, submitting to STABLE...