From: Tovo Rabemanantsoa <tovo.rabemanantsoa@bordeaux.inra.fr>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Bad performance with near-full FS
Date: Mon, 15 Jun 2015 14:47:24 +0200 [thread overview]
Message-ID: <557EC95C.8020902@bordeaux.inra.fr> (raw)
Hi all,
By browsing this list's archive, I've found a thread initiated by
Charles Cazabon entitled: "Oddly slow read performance with near-full
largish FS."
Actually, I'm living the same experience but with a not so large FS
(256GB on a SSD). Indeed, when I have less than 1GB of free space, the
applications (thunderbird, thunar ...) on the machine become awfully
slow but remain normal if I make some cleaning.
Is it due to the FS or because it's an SSD hard disk ?
Thanks in advance
--
Tovo J. Rabemanantsoa
IT Manager
Quality correspondent
INRA - UMR ISPA [Interactions Sol Plante Atmosphère]
Villenave d'Ornon - Gironde, France
+33 5 57 12 24 09
next reply other threads:[~2015-06-15 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 12:47 Tovo Rabemanantsoa [this message]
2015-06-15 13:29 ` Bad performance with near-full FS David Sterba
2015-06-15 14:44 ` Tovo Rabemanantsoa
2015-06-15 15:36 ` Clemens Eisserer
2015-06-15 15:37 ` Austin S Hemmelgarn
2015-06-16 6:27 ` Tovo Rabemanantsoa
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=557EC95C.8020902@bordeaux.inra.fr \
--to=tovo.rabemanantsoa@bordeaux.inra.fr \
--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