I tried to yum update this computer and got the following error:
One of the configured repositories failed (Fedora 21 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: ............. Insufficient space in download directory /var/cache/yum/x86_64/21/fedora * free 0 * needed 100 k .............
It suggests such things as:
3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage:
yum-config-manager --disable fedora .............
[root@bobgASRockServer bobg]# du -h /var/cache/yum/x86_64/21/fedora 4.0K /var/cache/yum/x86_64/21/fedora/gen 4.0K /var/cache/yum/x86_64/21/fedora/packages 12K /var/cache/yum/x86_64/21/fedora
[root@bobgASRockServer bobg]# du -h /var/cache/yum/x86_64/21/ 4.0K /var/cache/yum/x86_64/21/fedora/gen 4.0K /var/cache/yum/x86_64/21/fedora/packages 12K /var/cache/yum/x86_64/21/fedora 4.0K /var/cache/yum/x86_64/21/updates/gen 40K /var/cache/yum/x86_64/21/updates/packages 48K /var/cache/yum/x86_64/21/updates 68K /var/cache/yum/x86_64/21/
It doesn't look like there are any large files? I don't understand what's going on here. two other F-21 computers updated normally.
Bob
On Fri, 13 Mar 2015 05:24:13 -0400, Bob Goodwin wrote:
I tried to yum update this computer and got the following error:
One of the configured repositories failed (Fedora 21 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: ............. Insufficient space in download directory /var/cache/yum/x86_64/21/fedora * free 0 * needed 100 k .............
It suggests such things as:
- Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable fedora.............
[root@bobgASRockServer bobg]# du -h /var/cache/yum/x86_64/21/fedora 4.0K /var/cache/yum/x86_64/21/fedora/gen 4.0K /var/cache/yum/x86_64/21/fedora/packages 12K /var/cache/yum/x86_64/21/fedora
[root@bobgASRockServer bobg]# du -h /var/cache/yum/x86_64/21/ 4.0K /var/cache/yum/x86_64/21/fedora/gen 4.0K /var/cache/yum/x86_64/21/fedora/packages 12K /var/cache/yum/x86_64/21/fedora 4.0K /var/cache/yum/x86_64/21/updates/gen 40K /var/cache/yum/x86_64/21/updates/packages 48K /var/cache/yum/x86_64/21/updates 68K /var/cache/yum/x86_64/21/
It doesn't look like there are any large files? I don't understand what's going on here. two other F-21 computers updated normally.
You forgot to show how much free space there _is_. Then, after you've done that, run "yum clean metadata" and retry. Also check the directory access permission bits -- just in case.
On 03/13/15 05:28, Michael Schwendt wrote:
You forgot to show how much free space there_is_.
I can't think of the command to show free space?
Then, after you've done that, run "yum clean metadata" and retry. Also check the directory access permission bits -- just in case.
-
I did that first thing, and here again:
[root@bobgASRockServer bobg]# yum clean metadata Loaded plugins: langpacks Cleaning repos: fedora updates 0 metadata files removed 0 sqlite files removed 0 metadata files removed
On 03/13/15 05:51, Frederic Muller wrote:
On 03/13/2015 04:44 PM, Bob Goodwin wrote:
I can't think of the command to show free space?
df -h
-
[root@bobgASRockServer bobg]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 50G 49G 0 100% / devtmpfs 1.7G 0 1.7G 0% /dev tmpfs 1.7G 68K 1.7G 1% /dev/shm tmpfs 1.7G 1016K 1.7G 1% /run tmpfs 1.7G 0 1.7G 0% /sys/fs/cgroup tmpfs 1.7G 20K 1.7G 1% /tmp /dev/sda1 477M 132M 316M 30% /boot /dev/sda5 864G 283G 538G 35% /home 192.168.1.8:/home 864G 283G 538G 35% /mnt/HOME1 //192.168.1.48/myshare 686G 121G 530G 19% /mnt/box48 tmpfs 339M 4.0K 339M 1% /run/user/989 tmpfs 339M 8.0K 339M 1% /run/user/1000
-
[root@bobgASRockServer bobg]# ll /var/cache/yum/x86_64/21/fedora total 8 drwxr-xr-x. 2 root root 4096 Mar 13 04:41 gen drwxr-xr-x. 2 root root 4096 Mar 12 14:15 packages
On 03/13/15 05:51, Frederic Muller wrote:
On 03/13/2015 04:44 PM, Bob Goodwin wrote:
I can't think of the command to show free space?
df -h
-
[root@bobgASRockServer bobg]# df -h /var/cache/yum/x86_64/21/fedora Filesystem Size Used Avail Use% Mounted on /dev/sda3 50G 49G 0 100% /
Ok, there is the problem. Not sure what's going on or what has filled that?
I need more coffee ...
Thank you,
Bob
On 03/13/2015 06:04 AM, Bob Goodwin wrote:
Filesystem Size Used Avail Use% Mounted on /dev/sda3 50G 49G 0 100% /
Ok, there is the problem. Not sure what's going on or what has filled that?
I need more coffee ...
Thank you,
mine looks like [root@pauls-server backups]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb6 48G 22G 23G 49% /
I just increased mine from 30-49 recently.. check /tmp, /var/tmp /var/log check for big files in "/"
to find large files in the current folder: du -cks *|sort -rn|head
find large files in a folder: du -a /FOLDER_NAME |sort -n -r|head -20
Hey Bob,
Try cleaning the yum cache for unused packages...
On Fri, Mar 13, 2015 at 7:24 AM, Paul Cartwright pbcartwright@gmail.com wrote:
On 03/13/2015 06:04 AM, Bob Goodwin wrote:
Filesystem Size Used Avail Use% Mounted on /dev/sda3 50G 49G 0 100% /
Ok, there is the problem. Not sure what's going on or what has filled that?
I need more coffee ...
Thank you,
mine looks like [root@pauls-server backups]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb6 48G 22G 23G 49% /
I just increased mine from 30-49 recently.. check /tmp, /var/tmp /var/log check for big files in "/"
to find large files in the current folder: du -cks *|sort -rn|head
find large files in a folder: du -a /FOLDER_NAME |sort -n -r|head -20
-- Paul Cartwright Registered Linux User #367800 and new counter #561587
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Fri, 13 Mar 2015 08:29:57 -0300, Martin Cigorraga wrote:
Hey Bob,
Try cleaning the yum cache for unused packages...
By default, Yum does not keep installed packages in the cache. It would be necessary to edit yum.conf to enable that feature as explained in the manual.
Plus, Bob has shown a rather empty Yum cache in the original post.
Oops, thank you Michael! On Mar 13, 2015 11:04 AM, "Michael Schwendt" mschwendt@gmail.com wrote:
On Fri, 13 Mar 2015 08:29:57 -0300, Martin Cigorraga wrote:
Hey Bob,
Try cleaning the yum cache for unused packages...
By default, Yum does not keep installed packages in the cache. It would be necessary to edit yum.conf to enable that feature as explained in the manual.
Plus, Bob has shown a rather empty Yum cache in the original post.
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 03/13/15 10:04, Michael Schwendt wrote:
Plus, Bob has shown a rather empty Yum cache in the original post.
I am still trying to fix this, just in over my head ...
I've never used gparted before but so far have managed to shrink the largest partition 20+ GB. However that is an extended partition and I need to add space to / [/var/cache/yum/x86_64/21/fedora is what wants more room] and I don't understand how to deal with that?
If I botch this I can still re-install and start from scratch again but would prefer not.
Bob
On Fri, Mar 13, 2015 at 10:21 AM, Bob Goodwin bobgoodwin@wildblue.net wrote:
I've never used gparted before but so far have managed to shrink the largest partition 20+ GB. However that is an extended partition and I need to add space to / [/var/cache/yum/x86_64/21/fedora is what wants more room] and I don't understand how to deal with that?
/ is on sda3, /home is on sda5, so they are likely discontinuous regions of the drive. The / needs to be either LVM or Btrfs based in order to use discontinuous regions of the drive.
If I botch this I can still re-install and start from scratch again but would prefer not.
This looks most likely, unless you can find out what's consuming so much space on /.
On 13.03.2015 17:21, Bob Goodwin wrote: ...
If I botch this I can still re-install and start from scratch again but would prefer not.
Consider these two applications:
Graphical disk usage statistics - Qt/KDE - https://userbase.kde.org/Filelight Filelight allows you to quickly understand exactly where your diskspace is being used by graphically representing your file system.
A graphical directory tree analyzer - Gtk/GNOME - https://wiki.gnome.org/Apps/Baobab Baobab is able to scan either specific directories or the whole filesystem, in order to give the user a graphical tree representation including each directory size or percentage in the branch. It also auto-detects in real-time any change made to your home folder as far as any mounted/unmounted device.
Prior to installation, find the largest packages: $ rpm -qa --qf '%{size}\t%{name}\n' | sort -n
and uninstall the largest until you resolve the overflow issue.
On Fri, 13 Mar 2015 12:21:15 -0400, Bob Goodwin wrote:
I am still trying to fix this, just in over my head ...
Run "du -h /" on your sda3 and skim over the output. Watch out for directory trees that contain many GB. Is that usage expected? Especially examine /var. Try to find any runtime files (e.g. in cache directories other than Yum's) where you may want to clean up manually.
I've never used gparted before but so far have managed to shrink the largest partition 20+ GB. However that is an extended partition and I need to add space to / [/var/cache/yum/x86_64/21/fedora is what wants more room] and I don't understand how to deal with that?
If I botch this I can still re-install and start from scratch again but would prefer not.
An old-school way is to use a so-called "bind mount", i.e. mount a _directory_ stored on another partition on /var/cache/yum. In /etc/fstab an entry for that could be added, too. Example:
/home/storage/yumcache /var/cache/yum auto bind 0 0
Since your /home dir has enough free space. ;) Don't forget to remove stuff in /var/cache/yum prior to mounting.
-
Bob Goodwin -
Chris Murphy -
Frederic Muller -
Martin Cigorraga -
Michael Schwendt -
Paul Cartwright -
poma