From: Stan Hoeppner <stan@hardwarefreak.com>
To: Janos Haar <janos.haar@netcenter.hu>
Cc: linux-xfs@oss.sgi.com
Subject: Re: 2 question about XFS fragmentation and _fsr
Date: Mon, 11 Apr 2011 15:37:10 -0500 [thread overview]
Message-ID: <4DA36676.1070206@hardwarefreak.com> (raw)
In-Reply-To: <DFA094D472104424BEA7AA9060DE0D6F@myXP>
Janos Haar put forth on 4/11/2011 12:39 PM:
> In the result, actually we have >6TB images on the 3TB disk, wich is
> 97.9% fragmented.
How much free space does the filesystem have? How big is each image
file? For xfs_fsr to work properly it must have sufficient free space
in the filesystem.
> Basically the sparse RAW disk images should be more faster accessible
> than the original drive, because this is 4disk raid, instead of one, AND
> the head don't need to travel through the empty space of the drive...
It sounds like you may have some other issues besides filesystem
fragmentation.
> The XFS_FSR can be good for me or not?
If you have plenty of free space.
> Question 2:
> One of our customers have one storage wich is exactly the same like the
> one wich is described on the Q1, but only used for samba storage for
> storing media files (big files.)
Writing large files sequentially shouldn't cause fragmentation.
> I am sure, there is no torrent or similar, and i have told to the
> customers on the beginning "don't write more files parallel, to avoid
> fragmentation", but today the storage is >95% fragmented.
> The customer sad, he only does file write one by one, and nothing more.
> How can this be?
What were the mkfs.xfs arguments you used when creating these
filesystem? Please share xfs_info output for the filesystems in
question, and details of the underlying hardware RAID storage.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-11 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 17:39 2 question about XFS fragmentation and _fsr Janos Haar
2011-04-11 20:37 ` Stan Hoeppner [this message]
2011-04-26 21:21 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q2:normal files, samba share Janos Haar
2011-04-26 21:50 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q1:sparese files Janos Haar
2011-04-11 21:42 ` 2 question about XFS fragmentation and _fsr Dave Chinner
2011-04-11 23:37 ` Christoph Hellwig
2011-04-26 21:49 ` 2 question about XFS fragmentation and _fsr: Q2 Janos Haar
2011-04-26 21:51 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q1:sparse files Janos Haar
2011-04-27 20:18 ` Eric Sandeen
2011-04-27 20:37 ` Eric Sandeen
2011-04-26 21:51 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q2:normal files, samba share Janos Haar
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=4DA36676.1070206@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=janos.haar@netcenter.hu \
--cc=linux-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