On 23.09.2004 23:12, Matthias Schniedermeyer wrote:
> On 24.09.2004 06:41, Nathan Scott wrote:
> > On Thu, Sep 23, 2004 at 10:06:56AM +0200, Matthias Schniedermeyer wrote:
>
> It seems the problem got fixed the way that there now can be larger
> allocation groups, whereas i thought that mkfs program got fixed and the
> 4GB limit was system immanent.
>
> Seems i was wrong with this and i didn't need to manually raise the
> agcount (again) when i swaped my 100GB HDDs with 200GB HDDs and mkfs.xfs
> still used agcount=16 when i formated the 200GB HDDs.
> (I immediatly did another mkfs.xfs when i saw that agcount was so small.
> I didn't test it as the last time (last year when i first had that
> problem) the agcount was so small it killed my machine the moment a
> DVD-Image was "big enough")
I just reformated one of my 200GB HDDs with mkfs.xfs default (it shows
agcount=16)
Then i created a 10GB file. My machine survived. :-)
So i guess i zero points for me. :-)
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
|