All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lutz Vieweg <lvml@5t9.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: fstrim tries to discard data beyond the last sector of a device
Date: Fri, 21 Nov 2014 17:44:52 +0100	[thread overview]
Message-ID: <546F6C04.4060300@5t9.de> (raw)
In-Reply-To: <20141118110329.GG6704@x2.net.home>

On 11/18/2014 12:03 PM, Karel Zak wrote:
> what is your fstrim command line, it would be nice to see strace
> output to verify the ioctl return code.

I will run the test again and post the relevant strace output.

>> If email to this list is not a suitable form to report such issues,
>> please let me know where I can report this issue better.
>
> Maybe you can ask linux-fs mailing list. It really does not seem like
> fstrim command issue.

Ok, I'll direct my next post on this issue to linux-fsdevel@vger.kernel.org
(CC this mailing list, just in case...)

Thanks for the pointer!

Regards,

Lutz Vieweg

  reply	other threads:[~2014-11-21 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 16:07 fstrim: "fitrim ioctl failed: input/output error" -> "Logical block address out of range" Lutz Vieweg
2014-11-18 10:32 ` fstrim tries to discard data beyond the last sector of a device Lutz Vieweg
2014-11-18 11:03   ` Karel Zak
2014-11-21 16:44     ` Lutz Vieweg [this message]
2014-11-21 17:09   ` fstrim on newly created filesystem " Lutz Vieweg
2014-11-21 17:09     ` Lutz Vieweg
2014-11-21 21:20     ` Mike Frysinger
2014-11-21 21:20       ` Mike Frysinger
2014-11-24  9:23       ` Karel Zak
2014-11-24 12:25     ` Lukáš Czerner
2014-11-24 19:30       ` Lutz Vieweg
2014-11-24 19:30         ` Lutz Vieweg
2014-11-24 19:43         ` Bernd Schubert
2014-11-24 19:43           ` Bernd Schubert
2014-11-24 20:03           ` Lutz Vieweg
2014-11-24 20:03             ` Lutz Vieweg
2014-11-24 20:18             ` Bernd Schubert
2014-11-24 21:24     ` Dave Chinner
2014-11-24 21:24       ` Dave Chinner

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=546F6C04.4060300@5t9.de \
    --to=lvml@5t9.de \
    --cc=kzak@redhat.com \
    --cc=util-linux@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.