linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is SATA ALPM safe with btrfs now (no more corruption)?
Date: Mon, 1 Jun 2020 19:39:25 +0200	[thread overview]
Message-ID: <20200601173925.GB18421@twin.jikos.cz> (raw)
In-Reply-To: <20200529042615.GA32752@merlins.org>

On Thu, May 28, 2020 at 09:26:15PM -0700, Marc MERLIN wrote:
> TLP allows SATA power management: SATA_LINKPWR_ON_BAT=max_performance
> 
> There are some old posts that talk about corruption if you enable this
> with btrfs:
> https://wiki.archlinux.org/index.php/TLP#Btrfs
> says not to enable it
> 
> https://forum.manjaro.org/t/btrfs-corruption-with-tlp/25158
> 
> https://github.com/linrunner/TLP/issues/128
> says it may not be safe
> 
> https://www.reddit.com/r/archlinux/comments/5tm5uh/btrfs_and_tlp/
> also talks about corruption
> 
> https://www.reddit.com/r/archlinux/comments/4f5xvh/saving_power_is_the_btrfs_dataloss_warning_still/
> say it's probably ok
> 
> My feeling is that it's probably ok nowadays with a 5.6+ kernel.
> 
> Would anyone disagree?

I don't and reading the posts, it's a hardware problem leading to
filesystem corruption. It's affecting all filesystem but the detection
capabilities differ, so it stuck with btrfs.

At least the Arch wiki note can be removed, I don't see any value
keeping it there, the fixes to ATA subsystem have been merged to 4.15.

  reply	other threads:[~2020-06-01 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  4:26 Is SATA ALPM safe with btrfs now (no more corruption)? Marc MERLIN
2020-06-01 17:39 ` David Sterba [this message]
2020-06-12 18:16   ` Marc MERLIN

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=20200601173925.GB18421@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.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).