From: Paul Jones <paul@pauljones.id.au>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: RE: trim not working and irreparable errors from btrfsck
Date: Fri, 14 Aug 2015 10:51:58 +0000 [thread overview]
Message-ID: <B7F2379062E32745A8651FBDB20F64596115E0A2@Server.waterlogic.com.au> (raw)
In-Reply-To: <20150814100555.24c01e93@thetick>
> -----Original Message-----
> From: linux-btrfs-owner@vger.kernel.org [mailto:linux-btrfs-
> owner@vger.kernel.org] On Behalf Of Marc Joliet
> Sent: Friday, 14 August 2015 6:06 PM
> To: linux-btrfs@vger.kernel.org
> Subject: Re: trim not working and irreparable errors from btrfsck
>
> Am Thu, 13 Aug 2015 17:14:36 -0600
> schrieb Chris Murphy <lists@colorremedies.com>:
>
> >
> > Right now I think there's no status because a.) no bug report and b.)
> > not enough information.
>
> I was mainly asking because apparently there *is* a patch that helps some
> people affected by this, but nobody ever commented on it. Perhaps there's
> a reason for that, but I found it curious. (I see now that it was submitted in
> early January, in the thread "[PATCH V2] Btrfs: really fix trim 0 bytes after a
> device delete".)
>
> I can open a bug (I mean, that's part of being a user of btrfs at this stage), I'm
> just surprised that nobody else has.
I have to use that patch on one of my systems. I just assumed it was never merged because it wasn't quite ready yet. It seems to work fine for me though.
Paul.
next prev parent reply other threads:[~2015-08-14 10:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 14:18 trim not working and irreparable errors from btrfsck Christian
2015-06-16 21:14 ` Chris Murphy
[not found] ` <55816E7B.5040905@gmail.com>
2015-06-17 14:22 ` Chris Murphy
2015-06-17 14:33 ` Christian
2015-06-17 15:28 ` Chris Murphy
2015-06-17 15:40 ` Christian
2015-06-17 17:17 ` Austin S Hemmelgarn
2015-06-18 5:25 ` Duncan
2015-08-14 15:11 ` Jeff Mahoney
2015-06-20 14:11 ` Lutz Euler
2015-06-21 7:21 ` Paul Jones
2015-08-13 9:23 ` Marc Joliet
2015-08-13 23:14 ` Chris Murphy
2015-08-14 8:05 ` Marc Joliet
2015-08-14 8:15 ` Marc Joliet
2015-08-14 10:51 ` Paul Jones [this message]
2015-06-18 2:20 ` Paul Jones
2015-06-18 4:15 ` Chris Murphy
2015-06-18 4:19 ` Chris Murphy
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=B7F2379062E32745A8651FBDB20F64596115E0A2@Server.waterlogic.com.au \
--to=paul@pauljones.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.