From: Muhammad Fakhrul Rozi Bin Mohd Seth <rozi@ramunia.com>
To: xfs@oss.sgi.com
Subject: XFS slow performance
Date: Mon, 20 Oct 2008 09:17:59 +0800 [thread overview]
Message-ID: <48FBDC47.5080700@ramunia.com> (raw)
Hi All,
I'm using the UBUNTU server with LVM group of SCSI harddisk.
I'm using this setting for XFS:
1. mkfs.xfs --l logdev=/dev/sda1,size=64m --d agcount=32
/dev/test/department
1. mount -o noatime,nodiratime,nobarrier,logbufs=8
/dev/test/department /data/
My current situation is :
1) I'm using XFS file system as my files server
2) i'm using snapshot to make a hot backup like shadow copies in windows
The problem is it takes a long time and some time it make time out for:
1) New file creation
2) Copy files from xfs shared to another local pc's
** what have i check is; if no snapshot was taken; the files sharing was
go on without problem and really fast.
This problem occurred only when we have a snapshot drives. even a single
drive.
please help me and advise me on this?
Regards
Rozi
[[HTML alternate version deleted]]
next reply other threads:[~2008-10-20 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 1:17 Muhammad Fakhrul Rozi Bin Mohd Seth [this message]
2008-10-20 2:24 ` XFS slow performance Eric Sandeen
[not found] ` <48FBED80.60604@ramunia.com>
2008-10-20 2:57 ` Eric Sandeen
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=48FBDC47.5080700@ramunia.com \
--to=rozi@ramunia.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.