rustup failed (1.59.x) to 1.63.3): I had to remove ~/.rustup before the final success.

40 views
Skip to first unread message

ISHIKAWA,chiaki

unread,
Aug 17, 2022, 3:21:29 AMAug 17
to dev-platform
Hi,

During the local compilation of C-C TB, I got the following error after
I updated the local source tree and ran
mach configure.

--- begin quote
checking cargo version... 1.59.0
ERROR: Rust compiler 1.59.0 is too old.

To compile Rust language sources please install at least
version 1.61.0 of the 'rustc' toolchain (or, if using nightly,
at least one version newer than 1.61.0) and make sure it is
first in your path.

You can verify this by typing 'rustc --version'.

If you have the 'rustup' tool installed you can upgrade
to the latest release by typing 'rustup update'. The
installer is available from https://rustup.rs/

*** Fix above errors and then restart with "./mach build"

--- quote end

Well, I thought it is not a big deal, and ran
rustup as suggested. Such upgrades used to work like a charm.

Unfortunately, this time, i didn't.

Tthe rustup command spewed out mysterious errors about not being able to
rename files/directories.
Eventually, I gave up the local rusutp and went to the
https://rustup.rs/ site and ran the
command shown on the web page.

It also failed mysteriously. I noticed that there was OS error 28 (ENOSPC)?
Very strange because all the file systems had more than 800-900MB free
space.

Eventually, I removed ~/.rustup and ran the command at
https://rustup.rs/ and
now I could finally upgrade rustc.
(And I could run |mach configure|.
)
This did not happen before.

Just FYI.

Chiaki

PS:
This is the df output when the error occurred.
No filesystem is quite tight in terms of space. So OS error 28 (ENOSPC)
seems very strange.

df
Filesystem      1K-blocks       Used Available Use% Mounted on
udev              8161892          0   8161892   0% /dev
tmpfs             1638856       1304   1637552   1% /run
/dev/sda1         8153564     788828   6928976  11% /
/dev/sdn1        20464208   17645412   1753940  91% /usr
tmpfs             8194280          0   8194280   0% /dev/shm
tmpfs                5120          8      5112   1% /run/lock
/dev/sdp6       205314024  133292964  61518916  69% /NEW-SSD
/dev/sdo1       214470584  112975792  90527516  56% /NEW-SSD2
/dev/sdi1         8106460    4109160   3561540  54% /REF-COMM-CENTRAL
/dev/sdm1         8152540    2373796   5343032  31% /var
/dev/sdf1        13252248   11197848   1356496  90% /TEST-MAIL-DIR
/dev/sdd1         8106460    7439256    231444  97% /o-FF-NEW
/dev/sdh1         8106460    3808720   3861980  50% /TB-NEW
/dev/sde1         8106460    2556536   5114164  34% /COMM-CENTRAL
/dev/sdc6         3771000    2891336    668004  82% /OLD-VAR-DIR
/dev/sdl1        51289568   33051168  15600628  68% /KERNEL-SRC
/dev/sdj1        41309584     724772  38471396   2% /OLD-ROOT-DIR
/dev/sdc7        19047212   12657328   5397016  71% /OLD-USR-DIR
/dev/sdc10       32229344   29663264    903360  98% /home
/dev/sdc8          942940       3056    874708   1% /tmp
/dev/sdg1         8237532    4266432   3551724  55% /REF-OBJ-DIR
/dev/sdk1        24245468   14420960   8567548  63% /o-NREF-COMM-CENTRAL
download       2367313916 1713980864 653333052  73% /media/sf_download
tmpfs             1638856         60   1638796   1% /run/user/1000

The error spewed at the end of update failure:
error: failed to extract package (perhaps you ran out of disk space?):
No space left on device (os error 28)

Reply all
Reply to author
Forward
0 new messages