From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] XFS FileSystem - Slow Writes - GNOME/nautilus Issue?
Date: Wed, 30 Aug 2006 10:05:49 +0800 [thread overview]
Message-ID: <1156903549.31875.19.camel@neuromancer.home.net> (raw)
In-Reply-To: <7573e9640608291835k5f614653v7d8933950a712fee@mail.gmail.com>
On Tue, 2006-08-29 at 18:35 -0700, Richard Fish wrote:
> On 8/29/06, Ow Mun Heng <Ow.Mun.Heng@wdc.com> wrote:
> > $ mount | grep xfs
> > /dev/hda6 on /home type xfs (rw)
>
> Hmm, I missed this before. "nobarrier" should be showing up here. Try:
>
> mount /home -o remount,nobarrier
>
I did mention that I tried that as well. (but I just re-tried it anyway)
and it didn't have any changes.
Out of curiousity, I just tried to copy a file using an xterm (instead
of using nautilus) from DIsk 2 to disk1
disk2/partition2 - VFAT
disk1/partition6 - XFS partition (/home)
$ ls -lah WinXP-000001-cl1-000001-cl1-000001-s002.vmdk
-rwxrwxrwx 1 root root 620M Aug 29 19:10
WinXP-000001-cl1-000001-cl1-000001-s002.vmdk
$ time cp WinXP-000001-cl1-000001-cl1-000001-s001.vmdk ~/Desktop/
real 0m37.353s
user 0m0.157s
sys 0m5.445s
Transfer rate ~16.8MB/s
Using Nautilus (I don't know of a good way to measure throughput using
this, so it's basically what I see in the progress bar
~5min
gkrellm2 notes transfer rate ~2.0MB/s
However, doing the same thing to my /tmp directory (ext3 partition) the
same file copies in ~30secs and w/ ~17MB/s transfer rate.
What gives??
BTW, what's the difference between mc and mc-mp??
* app-misc/mc
Latest version available: 4.6.1
Latest version installed: [ Not Installed ]
Size of downloaded files: 11,606 kB
Homepage: http://www.ibiblio.org/mc/
Description: GNU Midnight Commander cli-based file manager
License: GPL-2
* app-misc/mc-mp [ Masked ]
Latest version available: 4.1.40_pre9
Latest version installed: [ Not Installed ]
Size of downloaded files: 2,904 kB
Homepage: http://mc.linuxinside.com/cgi-bin/dir.cgi
Description: GNU Midnight Commander cli-based file manager. 4.1.x
branch
License: GPL-2
> -Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-30 2:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 4:03 [gentoo-user] XFS FileSystem - Slow Writes Ow Mun Heng
2006-08-29 4:25 ` Jason Weisberger
2006-08-29 6:11 ` Mark Kirkwood
2006-08-29 6:37 ` Ow Mun Heng
2006-08-30 1:23 ` Mark Kirkwood
2006-08-30 23:23 ` Mark Kirkwood
2006-08-30 23:25 ` Justin Piszcz
2006-08-29 9:37 ` Richard Fish
2006-08-29 9:55 ` Mick
2006-08-29 9:58 ` Justin Piszcz
[not found] ` <1156845176.2843.24.camel@neuromancer.home.net>
2006-08-29 17:54 ` Richard Fish
2006-08-29 22:10 ` Ow Mun Heng
[not found] ` <7573e9640608291055p313ccac8m65a1523b5ad03a37@mail.gmail.com>
2006-08-29 18:03 ` Jeff Grant
2006-08-29 18:13 ` Richard Fish
2006-08-29 18:22 ` Jeff Grant
2006-08-30 1:35 ` Richard Fish
2006-08-30 2:05 ` Ow Mun Heng [this message]
2006-08-30 16:38 ` [gentoo-user] XFS FileSystem - Slow Writes - GNOME/nautilus Issue? Joshua Schmidlkofer
2006-08-31 3:37 ` [gentoo-user] XFS FileSystem - Slow Writes - GNOME/nautilus Issue? (SOLVED w/ ReFORMAT) Ow Mun Heng
[not found] ` <200608300951.58922.michaelkintzios@gmail.com>
2006-08-30 8:52 ` [gentoo-user] XFS FileSystem - Slow Writes Justin Piszcz
2006-08-30 9:27 ` Richard Fish
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=1156903549.31875.19.camel@neuromancer.home.net \
--to=ow.mun.heng@wdc.com \
--cc=gentoo-user@lists.gentoo.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