Bug 437335
Summary: | yum cannot allocate memory when running yum clean all | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matěj Cepl <mcepl> |
Component: | yum | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | ffesti, james.antill, katzj, mcepl, pmatilai, tim.lauridsen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-20 05:52:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matěj Cepl
2008-03-13 16:21:57 UTC
What's the filesystem type in /var? [root@hubmaier ~]# mount |grep '/var ' /dev/mapper/vol0-logVar on /var type ext4dev (rw) [root@hubmaier ~]# tune2fs -l /dev/mapper/vol0-logVar tune2fs 1.40.7 (28-Feb-2008) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 8f478d1d-ca0e-47be-af7d-1493a04ef809 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extents sparse_super large_file Filesystem flags: signed_directory_hash test_filesystem Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1316336 Block count: 5259264 Reserved block count: 262963 Free blocks: 3997445 Free inodes: 1276327 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1022 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8176 Inode blocks per group: 511 Filesystem created: Tue Feb 12 17:37:03 2008 Last mount time: Mon Mar 17 23:49:59 2008 Last write time: Mon Mar 17 23:49:59 2008 Mount count: 56 Maximum mount count: 23 Last checked: Tue Feb 12 17:37:03 2008 Check interval: 15552000 (6 months) Next check after: Sun Aug 10 18:37:03 2008 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Journal inode: 8 Default directory hash: tea Directory Hash Seed: 7cb3738d-e59d-468d-99a8-32e3a407c577 Journal backup: inode blocks [root@hubmaier ~]# If you move /var/cache/yum to an ext3 partition does the problem vanish? If so, can we bring an ext4 hacker into this bug for help? Actually, I forgot to add the most important thing -- it happened once to me, and I wasn't able to reproduce it since the filing of this bug. umm, yah. I'm gonna close this worksforme, b/c it does - let me know if you can replicate it. |