All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Dusty Mabe <dustymabe@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] fstrim and cache=none
Date: Tue, 04 Jun 2013 08:53:14 +0200	[thread overview]
Message-ID: <51AD8EDA.6060606@redhat.com> (raw)
In-Reply-To: <CAFfJ-R6KngbEiuGXDSrAyFM0H8VmaRB4s=NWgB_N5k+bqb_xSg@mail.gmail.com>

Il 04/06/2013 03:02, Dusty Mabe ha scritto:
> On Mon, Jun 3, 2013 at 5:39 PM, Dusty Mabe <dustymabe@gmail.com> wrote:
>>
>> It is possible that I was mistaken. Now when I switch back to
>> cache=none I am still able to execute trim operations. I'll
>> investigate a little more into my exact steps that I took and see if I
>> can come up with a reproducer for the issue I observed.
>>
> 
> Paolo,
> 
> I was mistaken. I had added a disk to the guest and then created an
> ext4 FS on the disk. I then noticed that I couldn't perform fstrim
> operations. I then examined the xml and the only difference between
> this disk and the other disk in the system was the cache=none. So I
> removed cache=none and then shutdown/booted the guest. After the
> reboot all worked fine so I assumed it was the cache=none line. This
> was wrong.
> 
> Actually it is the formatting of the filesystem. When i create an FS
> in the guest it disables discard. There are also some errors printed
> in /var/log/messages.
> 
> Please see the output in file at the following location:
> 
> http://dustymabe.com/content/qemu-devel-mail.txt

Please attach the QEMU command line too.  I'll try to reproduce.

Paolo

  reply	other threads:[~2013-06-04  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 20:21 [Qemu-devel] fstrim and cache=none Dusty Mabe
2013-06-03  6:39 ` Paolo Bonzini
2013-06-03 21:39   ` Dusty Mabe
2013-06-04  1:02     ` Dusty Mabe
2013-06-04  6:53       ` Paolo Bonzini [this message]
2013-06-04 12:01         ` Dusty Mabe
2013-06-11 23:18           ` Dusty Mabe
2013-06-12 12:49             ` Paolo Bonzini
2013-06-27  2:56               ` Dusty Mabe

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=51AD8EDA.6060606@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dustymabe@gmail.com \
    --cc=qemu-devel@nongnu.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.