Bug 25135 - It would be nice if the Release notes would suggest to make sure a user has enough free space, before using "--download-all"
Summary: It would be nice if the Release notes would suggest to make sure a user has e...
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: wiki.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Documentation Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-15 19:51 CEST by peter lawford
Modified: 2019-10-13 13:10 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
return of the command LC_ALL=C urpmi --replacefiles --auto-update --auto --download-all --test > migration-en_627.txt (293.15 KB, text/plain)
2019-07-15 19:54 CEST, peter lawford
Details

Description peter lawford 2019-07-15 19:51:35 CEST
Description of problem:
after restoring my mageia 6 to its original state after an hazardous trial of migration to version 7 (see bug 25124), I have performed the following test: 
first, I have replaced the medias of version 6 by the medias of version 7, as indicated in your migration guide:
[root@mga6-64 alain4]# urpmi.removemedia -a
[root@mga6-64 alain4]# urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.7.$ARCH.list'
theses commands successfully worked
and then:

[root@mga6-64 alain4]# LC_ALL=C urpmi --replacefiles --auto-update --auto --download-all --test > migration-en_627.txt

you'll find here attached the file migration-en_627.txt, open it and you'll see that each package (there are more than 1500) needs a space between 5000MB and 8500MB, say a total space more than 10TB, which doesn't make sense

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 peter lawford 2019-07-15 19:54:06 CEST
Created attachment 11188 [details]
return of the command LC_ALL=C urpmi --replacefiles --auto-update --auto --download-all --test > migration-en_627.txt
Comment 2 Thomas Backlund 2019-07-15 20:09:11 CEST
Thats because you use "--download-all" wich makes it download every rpm locally before install...

But I see the confusion... the size number is incremental, so it's the last line:

compiler-rt-8.0.0-1.mga7.x86_64 needs 8852MB on the / filesystem

that tells you how much space it needs in the end...

It could maybe be improved...

CC: (none) => tmb

Comment 3 peter lawford 2019-07-15 23:47:29 CEST
(In reply to Thomas Backlund from comment #2)
> Thats because you use "--download-all" wich makes it download every rpm
> locally before install...
> 
> But I see the confusion... the size number is incremental, so it's the last
> line:
> 
> compiler-rt-8.0.0-1.mga7.x86_64 needs 8852MB on the / filesystem
> 
> that tells you how much space it needs in the end...
> 
> It could maybe be improved...

yes, but the option --download-all is indicated in the upgrade guide of the mageia site: see 
https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_from_Mageia_6

furthermore, in the file migration-en_627.txt, line 142 says:
"installation fails"  why?

(cat -n migration-en_627.txt displays the lines number)
Comment 4 Thomas Backlund 2019-07-16 00:00:08 CEST
(In reply to peter lawford from comment #3)
> (In reply to Thomas Backlund from comment #2)
> > Thats because you use "--download-all" wich makes it download every rpm
> > locally before install...
> > 
> > But I see the confusion... the size number is incremental, so it's the last
> > line:
> > 
> > compiler-rt-8.0.0-1.mga7.x86_64 needs 8852MB on the / filesystem
> > 
> > that tells you how much space it needs in the end...
> > 
> > It could maybe be improved...
> 
> yes, but the option --download-all is indicated in the upgrade guide of the
> mageia site: see 
> https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_from_Mageia_6

It states "It is *sometimes* a good idea to ...", basically meaning especially with unstable internet connection, you might be better of downloading all first...

> 
> furthermore, in the file migration-en_627.txt, line 142 says:
> "installation fails"  why?
> 

Because with all stuff downloaded, you dont have enough free space on / anymore.
It tries to protect you from not trying to install something that will fail due to running out of disk space
Comment 5 Marja Van Waes 2019-08-01 09:57:21 CEST
(In reply to Thomas Backlund from comment #4)
> (In reply to peter lawford from comment #3)

> > 
> > yes, but the option --download-all is indicated in the upgrade guide of the
> > mageia site: see 
> > https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_from_Mageia_6
> 
> It states "It is *sometimes* a good idea to ...", basically meaning
> especially with unstable internet connection, you might be better of
> downloading all first...
> 
> > 
> > furthermore, in the file migration-en_627.txt, line 142 says:
> > "installation fails"  why?
> > 
> 
> Because with all stuff downloaded, you dont have enough free space on /
> anymore.
> It tries to protect you from not trying to install something that will fail
> due to running out of disk space

Reassigning to Docteam. The "It is sometimes a good idea to test the upgrade before carrying it on." message could maybe be changed into:

"It is sometimes a good idea, when you have more than enough free disk space, to test the upgrade before carrying it on."

Or in anything better that Docteam thinks of :-)

Assignee: bugsquad => doc-bugs
CC: (none) => marja11
Summary: nonsense huge free space needed for migration mageia6 to mageia7 => It would be nice if the Release notes would suggest to make sure a user has enough free space, before using "--download-all"
Severity: normal => enhancement

Marja Van Waes 2019-10-13 13:06:04 CEST

Component: New RPM package request => wiki.mageia.org
Version: 6 => trunk
Product: Mageia => Websites

Comment 6 Marja Van Waes 2019-10-13 13:10:33 CEST
Fixed https://wiki.mageia.org/mw-en/index.php?title=Mageia_7_Release_Notes&type=revision&diff=45522&oldid=45499

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.