Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*allocsize\s+mount\s+option\s*$/: 13 ]

Total 13 documents matching your query.

1. allocsize mount option (score: 1)
Author: Gim Leong Chin <chingimleong@xxxxxxxxxxxx>
Date: Tue, 12 Jan 2010 01:25:14 +0800 (SGT)
Hi, Mount options for xfs allocsize=size Sets the buffered I/O end-of-file preallocation size when doing delayed allocation writeout (default size is 64KiB). I read that setting allocsize to a big va
/archives/xfs/2010-01/msg00164.html (8,360 bytes)

2. Re: allocsize mount option (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 11 Jan 2010 12:16:08 -0600
That's not universally necessary though, depending on how you are writing them. I've only used it in the very specific case of mythtv calling "sync" every couple seconds, and defeating delalloc. poss
/archives/xfs/2010-01/msg00166.html (8,864 bytes)

3. Re: allocsize mount option (score: 1)
Author: Gim Leong Chin <chingimleong@xxxxxxxxxxxx>
Date: Wed, 13 Jan 2010 17:42:16 +0800 (SGT)
Hi, The application is ANSYS, which writes 128 GB files.  The existing computer with SUSE Linux Enterprise Desktop 11 which is used for running ANSYS, has two software RAID 0 devices made up of five
/archives/xfs/2010-01/msg00212.html (13,574 bytes)

4. Re: allocsize mount option (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 13 Jan 2010 21:50:18 +1100
XFS will start to fragment when the filesystem gets beyond 85% full - it seems that you are very close to that threshold. That being said, if you've pulled the figure of 19% from the xfs_db measure o
/archives/xfs/2010-01/msg00214.html (11,342 bytes)

5. Re: allocsize mount option (score: 1)
Author: Gim Leong Chin <chingimleong@xxxxxxxxxxxx>
Date: Fri, 15 Jan 2010 01:25:15 +0800 (SGT)
Hi Dave, There are many files that are 128 GB. When I did the tests with dd on this computer, the 20 GB files had up to > 50 extents. I just learnt from you that I can have a filesystem without a par
/archives/xfs/2010-01/msg00272.html (16,514 bytes)

6. Re: allocsize mount option (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 14 Jan 2010 11:42:11 -0600
which is at least 400mb per extent, which is really not so bad. -Eric
/archives/xfs/2010-01/msg00273.html (8,121 bytes)

7. Re: allocsize mount option (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 15 Jan 2010 10:28:09 +1100
That's still an average of 400MB extents, which is more than large enough to guarantee optimal disk bandwidth when reading or writing them on your setup.... That's the main benefit, though there are
/archives/xfs/2010-01/msg00287.html (15,304 bytes)

8. Re: allocsize mount option (score: 1)
Author: Gim Leong Chin <chingimleong@xxxxxxxxxxxx>
Date: Fri, 15 Jan 2010 11:08:22 +0800 (SGT)
Hi Dave, Thank you for the advice! I have done Direct IO dd tests writing the same 20 GB files.  The results are an eye opener!  bs=1GB, count=2 Single instance repeats of 830, 800 MB/s, compared to
/archives/xfs/2010-01/msg00293.html (12,571 bytes)

9. Re: allocsize mount option (score: 1)
Author: Gim Leong Chin <chingimleong@xxxxxxxxxxxx>
Date: Sun, 24 Jan 2010 14:44:08 +0800 (SGT)
Hi Guys, An update: SUSE Linux Enterprise 11 SP1 will be based on kernel 2.6.32, according to Novell support, when I asked for backporting. That will solve my problems. I do confirm that all the driv
/archives/xfs/2010-01/msg00523.html (15,566 bytes)

10. allocsize mount option (score: 1)
Author: <Ivan.Novick@xxxxxxx>
Date: Tue, 28 Sep 2010 14:53:46 -0400
Hi all, According to the documentation the allocsize mount option: "Sets the buffered I/O end-of-file preallocation size when doing delayed allocation writeout" Will this value limit "extent" sizes t
/archives/xfs/2010-09/msg00546.html (7,290 bytes)

11. Re: allocsize mount option (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 29 Sep 2010 10:31:10 +1000
No - it's specualtive preallocation. /me wishes he could run a sed script across the internet. noatime implies nodiratime, and logbufs=8 is the default, so you only need "noatime,allocsize=512m" It's
/archives/xfs/2010-09/msg00549.html (8,446 bytes)

12. allocsize mount option (score: 1)
Author: Peter Vajgel <pv@xxxxxx>
Date: Thu, 20 Jan 2011 20:41:19 +0000
We write about 100 100GB files into a single 10TB volume with xfs. We are using allocsize=1g to limit the fragmentation with a great success. We also need to reserve some space (~200GB) on each files
/archives/xfs/2011-01/msg00308.html (7,290 bytes)

13. Re: allocsize mount option (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 21 Jan 2011 11:48:16 +1100
No and no. However, if you take a look at the new dynamic specualtive allocation code in 2.6.38-rc1, it scales back the preallocation as ENOSPC is approached but doesn't do any reclaiming of existing
/archives/xfs/2011-01/msg00311.html (11,993 bytes)


This search system is powered by Namazu