From: M G Berberich <btrfs@oss.m-berberich.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: your mail
Date: Thu, 1 Sep 2016 23:15:18 +0200 [thread overview]
Message-ID: <20160901211518.jk5tpmwnhbb22xf4@invalid> (raw)
In-Reply-To: <31a75b1a-445a-47cd-816e-1e7e9d1c4bb8@gmail.com>
Am Donnerstag, den 01. September schrieb Austin S. Hemmelgarn:
> On 2016-09-01 03:44, M G Berberich wrote:
> > Am Mittwoch, den 31. August schrieb Fennec Fox:
> > > Linux Titanium 4.7.2-1-MANJARO #1 SMP PREEMPT Sun Aug 21 15:04:37 UTC
> > > 2016 x86_64 GNU/Linux
> > > btrfs-progs v4.7
> > >
> > > Data, single: total=30.01GiB, used=18.95GiB
> > > System, single: total=4.00MiB, used=16.00KiB
> > > Metadata, single: total=1.01GiB, used=422.17MiB
> > > GlobalReserve, single: total=144.00MiB, used=0.00B
> > >
> > > {02:50} Wed Aug 31
> > > [fennectech@Titanium ~]$ sudo fstrim -v /
> > > [sudo] password for fennectech:
> > > Sorry, try again.
> > > [sudo] password for fennectech:
> > > /: 99.8 GiB (107167244288 bytes) trimmed
> > >
> > > {03:08} Wed Aug 31
> > > [fennectech@Titanium ~]$ sudo fstrim -v /
> > > [sudo] password for fennectech:
> > > /: 99.9 GiB (107262181376 bytes) trimmed
> > >
> > > I ran these commands minutes after echother ane each time it is
> > > trimming the entire free space
> > >
> > > Anyone else seen this? the filesystem is the root FS and is compressed
> >
> > You should be very happy that it is trimming at all. Typical situation
> > on a used btrfs is
> >
> > # fstrim -v /
> > /: 0 B (0 bytes) trimmed
> >
> > even if there is 33G unused space ob the fs:
> >
> > # df -h /
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/sda2 96G 61G 33G 66% /
> >
> I think you're using an old kernel, this has been working since at least
> 4.5, but was broken in some older releases.
No, I’m always running a fairly up-to-date vanilla kernel on this
system. At the moment it’s:
Linux hermione 4.7.2 #4 SMP PREEMPT Wed Aug 24 17:12:03 CEST 2016 x86_64 GNU/Linux
I’m running kernels ≥ 4.5.0 since about April and I first reported this
problem at 7 Jul 2016 (Subject: fstrim problem/bug) probably with a
4.6.3 kernel.
MfG
bmg
--
„Des is völlig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!“ | mail@m-berberich.de
(SPD-Stadtrat Kurt Schindler; Regensburg) |
next prev parent reply other threads:[~2016-09-01 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 2:02 Fennec Fox
2016-09-01 3:10 ` Jeff Mahoney
2016-09-01 19:32 ` Re: Kai Krakow
2016-09-01 7:44 ` your mail M G Berberich
2016-09-01 11:17 ` Austin S. Hemmelgarn
2016-09-01 16:44 ` Kyle Gates
2016-09-01 17:06 ` Austin S. Hemmelgarn
2016-09-02 1:51 ` Jeff Mahoney
2016-09-01 21:15 ` M G Berberich [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-18 8:14 Tomasz Kłoczko
2018-02-18 9:28 ` your mail Tomasz Pala
2018-02-18 9:34 ` Tomasz Pala
[not found] <1330599216.71336.YahooMailNeo@web30703.mail.mud.yahoo.com>
2012-03-01 12:41 ` (unknown) bella tk
2012-03-01 12:58 ` your mail David Sterba
2012-03-01 14:26 ` Chris Mason
2011-09-20 15:24 (unknown) Ken D'Ambrosio
2011-09-20 15:35 ` your mail Hugo Mills
2011-09-20 15:40 ` Hugo Mills
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=20160901211518.jk5tpmwnhbb22xf4@invalid \
--to=btrfs@oss.m-berberich.de \
--cc=linux-btrfs@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).