From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs on small (embedded) systems
Date: Mon, 28 Sep 2009 14:47:51 +0200 [thread overview]
Message-ID: <4AC0B077.6080809@wpkg.org> (raw)
FYI - I've been using btrfs with 2.6.31.1 kernel for a few days as a
rootfs on a small mips system (ASUS WL-500gP - 32 MB RAM, 266 MHz CPU).
btrfs filesystem is placed on a USB-stick connected to the device
(internal flash only contains the kernel).
My main motivation for using btrfs on this small system was compression
this filesystem offers - flash storage is still prohibitively expensive
when compared to traditional hard disks (i.e. 32 GB USB-stick costs as
much as a 1 TB HDD).
So far, everything looks fine, although I didn't try to stress it much
(or use snapshots and/or make the filesystem full).
Certainly one thing I'm missing in btrfs is the ability to use swapfiles
- is it planned one day (or perhaps some serious surgery in MM would be
needed first)?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2009-09-28 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 12:47 Tomasz Chmielewski [this message]
2009-10-17 5:54 ` btrfs on small (embedded) systems Zhu Yanhai
2009-10-17 5:56 ` Zhu Yanhai
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=4AC0B077.6080809@wpkg.org \
--to=mangoo@wpkg.org \
--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