linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Kasten <igraltist@rsbac.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: trim support on 2.6.37
Date: Sat, 08 Jan 2011 02:11:47 +0100	[thread overview]
Message-ID: <1294449107.8289.1.camel@jaschtschik-malo> (raw)
In-Reply-To: <AANLkTimkf4n8Oyf0c17SCZFbNrpdV9mbcHeTQpkMxbMJ@mail.gmail.com>

Am Freitag, den 07.01.2011, 18:29 -0500 schrieb Greg Freemyer:
> On Fri, Jan 7, 2011 at 5:52 PM, Jens Kasten <igraltist@rsbac.org> wrote:
> > Hi list,
> >
> > It is the first time the i write to this list.
> > I am not sure if it the right place.
> >
> > I use the kernel 2.6.37 with cryptsetup and lvm on a intel ssd.
> > In the logfile after booting i see this entry:
> > EXT4-fs (dm-1): re-mounted. Opts: discard,errors=remount-ro
> > EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard
> > EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: discard
> > EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: discard
> > EXT4-fs warning (device dm-1): ext4_issue_discard:2619: discard not
> > supported, disabling
> > EXT4-fs warning (device dm-3): ext4_issue_discard:2619: discard not
> > supported, disabling
> > EXT4-fs warning (device dm-3): ext4_issue_discard:2619: discard not
> > supported, disabling
> > EXT4-fs warning (device dm-3): ext4_issue_discard:2619: discard not
> > supported, disabling
> > EXT4-fs (sda1): re-mounted. Opts: discard,commit=0
> > EXT4-fs (dm-3): re-mounted. Opts: discard,commit=0
> > EXT4-fs (dm-2): re-mounted. Opts: discard,commit=0
> >
> > The mount command shows:
> > /dev/mapper/System2-root_ssd on / type ext2
> > (rw,noatime,errors=remount-ro,barrier=1,stripe=32,data=ordered,discard)
> > and the corresponding entry from fstab:
> > UUID="635a1ad9-9ebb-4d1e-b8c3-30e11148bd92"     /                   ext4
> > noatime,discard,errors=remount-ro               0       1
> >
> > My question is now, I don't have trim support now?
> >
> > Viele Grüsse
> > Jens Kasten
> 
> Jens,
> 
> I don't believe DM supports discard / trim passthru.  For
> clarification, you should ask on the Device Mapper list.
> <dm-devel@redhat.com>
> 
> Alternatively, you may find that the wiper.sh script packaged with
> hdparm may work.  wiper.sh bypasses the DM layer and talks directly to
> the drives, but it too has limitations.  The wiper.sh script is meant
> to be called on a routine basis via cron, etc.
> 
> Greg
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi Greg,

ok i will ask on this list.

Jens

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-01-08  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 22:52 trim support on 2.6.37 Jens Kasten
2011-01-07 23:29 ` Greg Freemyer
2011-01-08  1:11   ` Jens Kasten [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=1294449107.8289.1.camel@jaschtschik-malo \
    --to=igraltist@rsbac.org \
    --cc=greg.freemyer@gmail.com \
    --cc=linux-ext4@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).