| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug. |
| From: | Arkadiusz Miśkiewicz <arekm@xxxxxxxx> |
| Date: | Thu, 3 Nov 2011 21:02:12 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20111103115429.GA15726@xxxxxxxxxxxxx> |
| References: | <201110311156.20421.arekm@xxxxxxxx> <20111103110306.GA8382@xxxxxxxxxxxxx> <20111103115429.GA15726@xxxxxxxxxxxxx> |
| User-agent: | KMail/1.13.7 (Linux/3.1.0-05616-gf362f98; KDE/4.7.3; x86_64; ; ) |
On Thursday 03 of November 2011, Christoph Hellwig wrote: > Can you give this patch a quick try on the image in that constrained > setup? Ate up all 8GB of ram and then was killed: [217802.127030] Out of memory: Kill process 22898:#0 (xfs_repair) score 784 or sacrifice child [217802.127033] Killed process 22898:#0 (xfs_repair) total-vm:7156064kB, anon- rss:6652784kB, file-rss:620kB Now the question is if 8GB should be enough for repairing 7TB filesystem? -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ |
| Previous by Date: | Re: [PATCH 7/9] xfstests: add a new quota test that runs fsstress under ENOSPC conditions, Christoph Hellwig |
|---|---|
| Next by Date: | Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug., Arkadiusz MiÅkiewicz |
| Previous by Thread: | Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug., Christoph Hellwig |
| Next by Thread: | Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug., Arkadiusz MiÅkiewicz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |