linux-ext4 - Re: trim support on 2.6.37

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 08 Jan 2011 02:11:47 +0100
From:	Jens Kasten <igraltist@...ac.org>
To:	Greg Freemyer <greg.freemyer@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: trim support on 2.6.37

Am Freitag, den 07.01.2011, 18:29 -0500 schrieb Greg Freemyer:
> On Fri, Jan 7, 2011 at 5:52 PM, Jens Kasten <igraltist@...ac.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@...hat.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@...r.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html