xfs
[Top] [All Lists]

Re: xfs_repair: "fatal error -- ran out of disk space!"

To: "Patrick J. LoPresti" <lopresti@xxxxxxxxx>
Subject: Re: xfs_repair: "fatal error -- ran out of disk space!"
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 22 Jun 2011 17:27:14 -0500
Cc: xfs@xxxxxxxxxxx
In-reply-to: <BANLkTi=gS5iO9R9pVk_df-4ofkkb0ZJgfw@xxxxxxxxxxxxxx>
References: <BANLkTi=gS5iO9R9pVk_df-4ofkkb0ZJgfw@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
On 6/22/11 4:32 PM, Patrick J. LoPresti wrote:
> I have a 5.1TB XFS file system that is 93% full (399G free according to "df").
> 
> I am trying to run "xfs_repair" on it.
> 
> The output is appended.
> 
> Question:  What am I supposed to do about this?  "xfs_repair -V" says
> "xfs_repair version 3.1.5".  (I downloaded and built the latest
> version hoping it would fix the issue, but no luck.)  Should I just
> start deleting files at random?

You could start by removing a few files you know you don't need, rather than
at random.  :)

TBH I've not seen this one before, and the error message is not all that
helpful.  It'd be nice to know how many blocks it was trying to reserve
when it ran out of space; I guess you'd need to use gdb, or instrument
all the calls to res_failed() in phase6.c to know for sure...

You could also capture an xfs_metadump of the fs and provide it for
analysis, it would let us reproduce the issue and know for sure what's
going on.  By default it obfuscates metadata.

-Eric

> Any ideas would be appreciated; I am trying to get this server back
> up, and restoring 5.1T is not going to be pleasant.
> 
> Thanks!
> 
>  - Pat
> 
> 
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - zero log...
>         - scan filesystem freespace and inode maps...
> sb_icount 42688, counted 59328
> sb_ifree 1, counted 36
> sb_fdblocks 104582610, counted 24
>         - found root inode chunk
> Phase 3 - for each AG...
>         - scan and clear agi unlinked lists...
>         - process known inodes and perform inode discovery...
>         - agno = 0
>         - agno = 1
>         - agno = 2
>         - agno = 3
>         - agno = 4
>         - agno = 5
>         - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
>         - setting up duplicate extent list...
>         - check for inodes claiming duplicate blocks...
>         - agno = 0
>         - agno = 2
>         - agno = 3
>         - agno = 5
>         - agno = 4
>         - agno = 1
> Phase 5 - rebuild AG headers and trees...
>         - reset superblock...
> Phase 6 - check inode connectivity...
>         - resetting contents of realtime bitmap and summary inodes
>         - traversing filesystem ...
> 
> fatal error -- ran out of disk space!
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
> 

<Prev in Thread] Current Thread [Next in Thread>