public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Janos Haar" <janos.haar@netcenter.hu>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: 2 question about XFS fragmentation and _fsr: SPLITTED Q1:sparese files
Date: Tue, 26 Apr 2011 23:50:43 +0200	[thread overview]
Message-ID: <2FDAD38566FF4F8B9C5ACF3F900287D6@myXP> (raw)
In-Reply-To: 4DA36676.1070206@hardwarefreak.com

Note: I have splitted my previous letter for easyer discusion...
This have only Question-1 the storage with only sparse files.

----- Original Message ----- 
From: "Stan Hoeppner" <stan@hardwarefreak.com>
To: "Janos Haar" <janos.haar@netcenter.hu>
Cc: <linux-xfs@oss.sgi.com>
Sent: Monday, April 11, 2011 10:37 PM
Subject: Re: 2 question about XFS fragmentation and _fsr


> 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.

Actually less than 1%.
I know, this is too less for xfs_fsr, but i am only thinking actually to try 
because i am unsure this is useful for me.

>
>> 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.
>
> -- 
> Stan

Thanks,
Janos 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2011-04-26 21:48 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
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   ` Janos Haar [this message]
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=2FDAD38566FF4F8B9C5ACF3F900287D6@myXP \
    --to=janos.haar@netcenter.hu \
    --cc=linux-xfs@oss.sgi.com \
    --cc=stan@hardwarefreak.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