From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: cwillu <cwillu@cwillu.com>
Cc: Hubert Kario <hka@qbs.com.pl>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: ssd option for USB flash drive?
Date: Thu, 19 May 2011 23:12:33 +0100 [thread overview]
Message-ID: <20110519221233.GB4209@yahoo.fr> (raw)
In-Reply-To: <BANLkTinxt3N2_=STRiiJsOAYWEd2-yx_FA@mail.gmail.com>
2011-05-19 15:54:23 -0600, cwillu:
[...]
> Try with the "ssd_spread" mount option.
[...]
Thanks. I'll try that.
> > I wonder now what credit to give to recommendations like in
> > http://www.patriotmemory.com/forums/showthread.php?3696-HOWTO-Increase-write-speed-by-aligning-FAT32
> > http://linux-howto-guide.blogspot.com/2009/10/increase-usb-flash-drive-write-speed.html
> >
> > Doing a apt-get upgrade on that stick takes hours when the same
> > takes a few minutes on an internal drive.
>
> Also, there's a package "libeatmydata" which will provide an
> "eatmydata" command, which you can prefix your apt-get commands with.
> This will disable the excessive sync calls that dpkg makes, and should
> dramatically decrease the time for those sorts of things to finish.
> Flash as found in thumb drives doesn't have much in the way of crash
> guarantees anyway, so you're not really giving up much safety.
Thanks. That's very useful indeed.
Note that if you use that on aptitude/apg-get that means that
the daemons started/restarted in the process will be affected,
but it could be all the better in my case.
Now, with that eatmydata, I'm thinking of trying qemu-nbd -c
/dev/nbd0 /dev/mapper/original-device with that and have the
rootfs mounted on that /dev/nbd0.
That eatmydata could be a work around to the problem I was
mentionning at
https://lists.ubuntu.com/archives/ubuntu-server-bugs/2010-June/037846.html
--
Stephane
next prev parent reply other threads:[~2011-05-19 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 22:02 ssd option for USB flash drive? Stephane Chazelas
2011-05-19 19:04 ` Hubert Kario
2011-05-19 19:53 ` Hubert Kario
2011-05-19 21:47 ` Stephane Chazelas
2011-05-19 21:54 ` cwillu
2011-05-19 22:12 ` Stephane Chazelas [this message]
2011-05-19 22:19 ` cwillu
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=20110519221233.GB4209@yahoo.fr \
--to=stephane_chazelas@yahoo.fr \
--cc=cwillu@cwillu.com \
--cc=hka@qbs.com.pl \
--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