From: Marc MERLIN <marc@merlins.org>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: Is SATA ALPM safe with btrfs now (no more corruption)?
Date: Fri, 12 Jun 2020 11:16:46 -0700 [thread overview]
Message-ID: <20200612181646.GB1128@merlins.org> (raw)
In-Reply-To: <20200601173925.GB18421@twin.jikos.cz>
On Mon, Jun 01, 2020 at 07:39:25PM +0200, David Sterba wrote:
> 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.
Sorry, it looks like I never replied to you. Thanks for confirming my
guess.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
prev parent reply other threads:[~2020-06-12 18:19 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
2020-06-12 18:16 ` Marc MERLIN [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=20200612181646.GB1128@merlins.org \
--to=marc@merlins.org \
--cc=dsterba@suse.cz \
--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).