Bug 215522 - xfs_reapir gets killed by OOM on FC6 recovery CD
Summary: xfs_reapir gets killed by OOM on FC6 recovery CD
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xfsprogs
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Garzik
QA Contact:
URL: http://oss.sgi.com/bugzilla/show_bug....
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-14 15:17 UTC by Konstantin Antselovich
Modified: 2013-07-03 02:30 UTC (History)
2 users (show)

Fixed In Version: 2.9.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-22 19:13:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
photo of kernel OOPS (1.28 MB, image/jpeg)
2006-11-21 20:01 UTC, Konstantin Antselovich
no flags Details

Description Konstantin Antselovich 2006-11-14 15:17:23 UTC
Description of problem: xfs_repair recovery program for XFS from xfsprogs
package gets killed by OOM-killer on FC6 recovery CD. 


Version-Release number of selected component (if applicable):
Name   : xfsprogs
Arch   : i386
Version: 2.8.11
Release: 3.fc6
Size   : 2.9 M
Repo   : installed
Summary: Utilities for managing the XFS filesystem.



How reproducible:  Always


Steps to Reproduce:
1. Boot from FC6 recovery CD
2. type `xfs_repair /dev/xfs_partition
3. watch top on the other console how xfs_repair eats memory and finally
   "... was killed by OOM"
  
Actual results:
program does not finish it s work, gets killed by kernel because it eats all
available memory

Expected results:
application should work as expected -- go through all blocks and inodes to
repair filesystem.


Additional info:
was able to recover with old version (about 2 years old) of xfs_repair

Comment 1 Eric Sandeen 2006-11-16 04:28:31 UTC
how big, and how populated (inode count) is the filesystem you are repairing?

Comment 2 Konstantin Antselovich 2006-11-16 05:12:51 UTC
it was a / directory on my working machine -- 15GB total, 8GB used.  Naturally
there are lots of small files in / but that's should handled.

If you look at the 'top' output on the other console while xfs_repair is working
-- it grows in size every second and it takes all available memory in less than
a minute.  So, I pretty sure its bug and not a feature.

 

Comment 3 Konstantin Antselovich 2006-11-16 05:18:21 UTC
PS: sorry, cannot look at the inode count right now, / is mounted.



Comment 4 Eric Sandeen 2006-11-16 15:24:41 UTC
df -i will give you inode counts... 

But, this doesn't sound like a particularly large filesystem, just wanted to
check.  I'll ping the sgi repair maintainer & see if they have any idea.  How
much memory was in your machine?  I wonder if swap is enabled in FC6 rescue mode...

Thanks,
-Eric

Comment 5 Konstantin Antselovich 2006-11-16 15:55:44 UTC
> df -i 
oops, did know that.

So for the record:
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/mapper/fedora3-system
                     1867776  288312 1579464   16% /

I dunno if swap is enabled by default, even I it will be, I guess it won't help
much if you need to repair any FS of a descent size (with the current FC6 repair CD)


Thanks for the reply,
Konstantin


Comment 6 Konstantin Antselovich 2006-11-16 15:57:22 UTC
PS: mem size is 768MB

Comment 7 Eric Sandeen 2006-11-16 15:58:48 UTC
Konstantin, thanks.  Let me ping the sgi guys on this one...

Comment 8 Konstantin Antselovich 2006-11-21 19:59:02 UTC
PS: I did some experiments with xfs_repair last night, running `xfs_reapir
/dev/fedora3/storage' (small xfs partition, about 10GB)  resulted in kernel OOPS

See attached photo.

Comment 9 Konstantin Antselovich 2006-11-21 20:01:01 UTC
Created attachment 141821 [details]
photo of kernel OOPS

Comment 10 Eric Sandeen 2006-11-22 01:37:12 UTC
well, that's not really an oops, it's detected a soft lockup.  And although it
is the xfs_repair process, I can't imagine what it would be doing to cause
this... strange.

Comment 11 Eric Sandeen 2007-08-22 19:13:02 UTC
Most recent xfs_repair should be much better for both memory consumption and
speed.  There's not a lot we can do to fix the FC6 recovery CD, as it's spun and
done.

If you still have xfs_repair OOM problems with more recent xfsprogs (or more
recent recovery CDs), please file another bug...

F8test now has the most recent xfsprogs, and F7 should get it in a bit (it's in
updates-testing now).

Thanks,

-Eric


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