From: Georg Lukas <georg@op-co.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-replace OOM on 2GB machine
Date: Tue, 17 Nov 2015 14:18:13 +0100 [thread overview]
Message-ID: <20151117131657.GA3424@ovgu.de> (raw)
In-Reply-To: <564B23D8.2000202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
* Austin S Hemmelgarn <ahferroin7@gmail.com> [2015-11-17 13:56]:
> While it probably isn't related to the OOM issue, I would be particularly
> wary of using BTRFS on SMR disks, we've had multiple reports of serious
> issues with them (and IIRC, they were all the same model of 8TB Seagate SMR
> disks).
Yes, that's exactly the model I have here, but the problems are related
to the SMR support in the kernel, and hopefully not at all to btrfs.
With the latest patch by Martin K. Petersen [*], the disks seem to be
stable and reliable, finally.
[*] https://bugzilla.kernel.org/show_bug.cgi?id=93581
> Hmm, it looks like things weren't all RAID1, you've got a little over 1TiB
> of data that was RAID0, and that may be why you can't rebuild the FS. This
> shouldn't be causing an OOM condition, but it definitely means things are
> not fully recoverable.
I think this was caused by my attempt to rebalance the degraded RAID1
into RAID0, and there are indeed some files on the fs that I can't read
any more. As this is not a production system, I'm not very bothered - I
just wanted to find out if I can get it back to live, which currently
fails on the replace.
> This actually looks like it's a different issue potentially, for some reason
> BTRFS is trying to scrub the missing disk (which won't work of course).
Indeed, scrubbing the degraded disk set did not succeed either.
If you need me to perform any other actions on that disk set, let me
know on- or off-list.
Georg
--
|| http://op-co.de ++ GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N ++
|| gpg: 0x962FD2DE || o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+ ||
|| Ge0rG: euIRCnet || X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y? ||
++ IRCnet OFTC OPN ||_________________________________________________||
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-11-17 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 16:15 btrfs-replace OOM on 2GB machine Georg Lukas
2015-11-17 12:55 ` Austin S Hemmelgarn
2015-11-17 13:18 ` Georg Lukas [this message]
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=20151117131657.GA3424@ovgu.de \
--to=georg@op-co.de \
--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