From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM & fstrim behaviour (Fedora 19)
Date: Tue, 24 Sep 2013 12:05:25 -0400 [thread overview]
Message-ID: <5241B845.4060102@gmail.com> (raw)
In-Reply-To: <5241B520.6080408@gmail.com>
On 09/24/2013 11:52 AM, Jorge F�bregas wrote:
> I can't recreate the original problem when I opened the bug (fstrim reporting
> always 124 MiB). I'm not sure if any update had to do anything with it.
Arrrgh. Please discard my last email (with my sample run). I totaly
forgot that I had "discard" as a mount option in /etc/fstab (I did this
as fstrim wasn't properly working). I'll remove the option now and will
perform the tests again.
next prev parent reply other threads:[~2013-09-24 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 18:38 [linux-lvm] LVM & fstrim behaviour (Fedora 19) Jorge Fábregas
2013-09-24 13:20 ` Lukáš Czerner
2013-09-24 15:01 ` Lukáš Czerner
2013-09-24 15:52 ` Jorge Fábregas
2013-09-24 16:05 ` Jorge Fábregas [this message]
2013-09-24 16:14 ` Jorge Fábregas
2013-09-24 18:03 ` Jorge Fábregas
2013-09-25 8:39 ` Lukáš Czerner
2013-09-25 10:15 ` Jorge Fábregas
2013-09-24 15:14 ` Jorge Fábregas
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=5241B845.4060102@gmail.com \
--to=jorge.fabregas@gmail.com \
--cc=linux-lvm@redhat.com \
/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).