From: "litaibaichina@gmail.com" <litaibaichina@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfsck out of memory for big fs
Date: Fri, 17 Aug 2018 10:44:19 +0800 [thread overview]
Message-ID: <201808171044160880896@gmail.com> (raw)
Hi Guys,
I had a big btrfs on a md device, it be mounted , but after a while it will become ready only:
# btrfs fi df /data/
Data, single: total=24.46TiB, used=24.46TiB
System, DUP: total=8.00MiB, used=2.59MiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=81.00GiB, used=79.71GiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=512.00MiB, used=264.28MiB
# dmesg -T
[Thu Aug 16 18:16:31 2018] BTRFS error (device md127): parent transid verify failed on 26603622694912 wanted 185320 found 207817
[Thu Aug 16 18:16:31 2018] BTRFS error (device md127): parent transid verify failed on 26603622694912 wanted 185320 found 207817
[Thu Aug 16 18:16:31 2018] BTRFS warning (device md127): Skipping commit of aborted transaction.
[Thu Aug 16 18:16:31 2018] BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure
[Thu Aug 16 18:16:31 2018] BTRFS info (device md127): forced readonly
[Thu Aug 16 18:16:31 2018] BTRFS info (device md127): delayed_refs has NO entry
I want to use btrfsck to check it, but it will OOM :
# btrfsck /dev/md127
Checking filesystem on /dev/md127
UUID: 6b87a52f-9a5f-4d03-b345-9d954c2ce259
checking extents
Killed
I am trying to use lowmem mode, but as I tried before, it may OOM too, any ideas ?
Thanks.
next reply other threads:[~2018-08-17 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 2:44 litaibaichina [this message]
2018-08-17 4:34 ` btrfsck out of memory for big fs Qu Wenruo
[not found] ` <2018081713260089574410@gmail.com>
2018-08-17 5:52 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201808171044160880896@gmail.com \
--to=litaibaichina@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).