ran xfs_repair -vv -L -P -m1750 and segfault at expected point.
I got the core-dump with dbg symbols, along with repair output and strace output.
What should I do with it? Provide as it is?
Archive is about 70M: for now I can make a public share:
https://apps.memopal.com/e/S656XDVV
Hope this can help.
On Thu, May 9, 2013 at 5:11 PM, Filippo Stenico <filippo.stenico@xxxxxxxxx> wrote:
On Thu, May 9, 2013 at 1:39 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
On Wed, May 08, 2013 at 07:30:05PM +0200, Filippo Stenico wrote:That's exactly what the oom killer is supposed to do.
> Hello,
> -m option seems not to handle the excessive memory consumption I ran into.
> I actually ran xfs_repair -vv -m1750 and looking into kern.log it seems
> that xfs_repair invoked oom killer, but was killed itself ( !! )
Yeah, some sacrifice needed.
> This is last try to reproduce segfault:I know your filesystem is around 7TB in size, but how much RAM do
> xfs_repair -vv -P -m1750
you have? It's not unusual for xfs_repair to require many GB of
memory to run succesfully on filesystems of this size...
it is around 11 TB, 7.2 used.
I have 4 G ram, but xfs_repair -vv -m1 says I need 1558
root@ws1000:~# xfs_repair -vv -P -m 1 /dev/mapper/vg0-lv0
Phase 1 - find and verify superblock...
- max_mem = 1024, icount = 29711040, imem = 116058, dblock = 2927886336, dmem = 1429632
Required memory for repair is greater that the maximum specified
with the -m option. Please increase it to at least 1558.
so I figured 1750 megs would be enoughCheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
--
F
--
F
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
