Summary: | sys-apps/portage-2.2.24 (?) - eats all inode in /usr/portage | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Juergen Rose <rose> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2015-11-13 11:03:11 UTC
(In reply to Juergen Rose from comment #0) > Is this large number of files to be expected? Yes, it's perfectly normal. > I do not have any selinux > package installed. Can I delete the files under > /usr/portage/metadata/md5-cache/sec-policy? Yes, but that some things (like emerge --searchdesc) will trigger metadata generation in /var/cache/edb/deb unless you also delete /usr/portage/sec-policy. > root@lynx:/usr/portage_lynx(60)# df -T /usr/portage > Filesystem Type 1K-blocks Used Available Use% Mounted on > /dev/mapper/vg-portage ext2 2046355 495326 1446172 26% /usr/portage_lynx > root@lynx:/usr/portage_lynx(61)# df -i /usr/portage > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/mapper/vg-portage 200704 200704 0 100% /usr/portage_lynx > > > Should I reformat my filesystem? Yes, and use a smaller bytes-per-inode setting. Note some filesystems such as xfs and btrfs do not have the "fixed number of inodes" limitation. Thanks Zac Medico, after reformating /usr/portage with ('mkfs.ext2 -b1024 -N400000 /dev/mapper/vg-portage' or 'mkfs.ext2 -b1024 -i2048'), 'tune2fs -O dir_index -c100 -i100 /dev/mapper/vg-portage' I have now 399360 or 2097152 inodes and /usr/portage is again writable. |