From: Eric Sandeen <sandeen@sandeen.net>
To: Muhammad Fakhrul Rozi Bin Mohd Seth <rozi@ramunia.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: XFS slow performance
Date: Sun, 19 Oct 2008 21:57:09 -0500 [thread overview]
Message-ID: <48FBF385.2010709@sandeen.net> (raw)
In-Reply-To: <48FBED80.60604@ramunia.com>
Muhammad Fakhrul Rozi Bin Mohd Seth wrote:
> Thanks for the reply;
No problem; please keep the list on cc: so that others with similar
problems will have something to find on google :)
> Yes i have test the other's and it is more worst than XFS.
> So here the snapshot is provide by the LVM not the XFS itself?
That's right; xfs itself has no snapshot capability. It's done at the
block layer (via lvm in your case).
> Have face any issue on snapshot using LVM before?
I don't use snapshots much so can't say, but they do have overhead. You
may have more luck asking for suggestions on the lvm users list. There
might be some tuning you can do.
-Eric
> Regards
> Rozi
prev parent reply other threads:[~2008-10-20 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 1:17 XFS slow performance Muhammad Fakhrul Rozi Bin Mohd Seth
2008-10-20 2:24 ` Eric Sandeen
[not found] ` <48FBED80.60604@ramunia.com>
2008-10-20 2:57 ` Eric Sandeen [this message]
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=48FBF385.2010709@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox