On 9 Jun 2005 at 9:46, Alex Zbyslaw wrote:
> >A local friend has suggested to increase the block size
> >
> It ought also make sense if you are serving up *large* files (didn't you
> say video/audio?).
...
> I don't have anything on your scale (23Gb
> of document database pales into insignificanc
Frantisek Rysanek wrote:
Thanks a lot to Mr. Zbyslaw.
You're welcome.
A local friend has suggested to increase the block size to
newfs, or something along those lines - essentially to
decrease the FS overhead and the size of the "blockmap".
I haven't tried that but I guess it sounds reaso
Thanks a lot to Mr. Zbyslaw.
Being too lazy myself to fiddle with the soft limit via the
shell or bootloader, I did the following in the kernel build
config file:
options MAXDSIZ=(1024UL*1024*1024)
options DFLDSIZ=(1024UL*1024*1024)
This way, fsck works just fine.
To address ot
Tony Shadwick wrote:
Did I just understand you right, or did you just say that the default
amount of RAM that FreeBSD allows in the kernel is 512MB without
throwing that switch at compile time
Aw crap. If you're right, you just explained one of the grander
mysteries I'm experiencing wit
Dan Nelson wrote:
You can also set it in /boot/loader.conf: kern.maxdsiz="1024M"
Nice. Did not know that. Thanks,
--Alex
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe
In the last episode (Jun 08), Tony Shadwick said:
> On Wed, 8 Jun 2005, Alex Zbyslaw wrote:
> >which is all my 1Gb physical memory. The default is a mere 512Mb.
> >You might need users to be limited to a bit less, but I don't have
> >any of them
>
> Whoa.wait a sec there.
>
> Did I just un
On Wed, 8 Jun 2005, Alex Zbyslaw wrote:
Frantisek Rysanek wrote:
I thought "fsck" would be a plausible benchmarking tool.
-bash-2.05b# fsck_ufs /dev/stripe/data
** /dev/stripe/data
cannot alloc 768053748 bytes for blockmap
* FILE SYSTEM MARKED DIRTY *
After a forced mount, the 12TB
Frantisek Rysanek wrote:
I thought "fsck" would be a plausible benchmarking tool.
-bash-2.05b# fsck_ufs /dev/stripe/data
** /dev/stripe/data
cannot alloc 768053748 bytes for blockmap
* FILE SYSTEM MARKED DIRTY *
After a forced mount, the 12TB volume works fine. It just
can't be fsck
Just curious, what happens if you run the fsck with -f? Since it isn't
production I won't feel bad if it clobbers something. ;)
On Wed, 8 Jun 2005, Frantisek Rysanek wrote:
Dear everyone,
this is not an important issue, but I'd like to ask anyway,
just in case the solution was obvious:
I've
Dear everyone,
this is not an important issue, but I'd like to ask anyway,
just in case the solution was obvious:
I've bundled three 4TB RAID boxes using GEOM::stripe into a
single 12TB volume. I didn't partition it, I just created UFS
on it using newfs (a "dangerously dedicated" volume).
T
10 matches
Mail list logo
