We are planning to upgrade our QNX 4 archive nodes which currently have a
total of 74 Gig of disk space each. It seems there are some RAID solutions
out there that offer support for up to 520 Gig in a single array. Which
would solve our current storage problems nicely, but it also opens up the
possibility of combining multiple arrays for terabytes worth of disk on a
single system. I know about the (yet to be documented anywhere but in this
news group and QUICS archives -H option to Fsys and I would guess that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger? Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
We are planning to upgrade our QNX 4 archive nodes which currently have a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array. Which
would solve our current storage problems nicely, but it also opens up the
possibility of combining multiple arrays for terabytes worth of disk on a
single system. I know about the (yet to be documented anywhere but in
this
news group and QUICS archives > > -H option to Fsys and I would guess that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger? Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
We are planning to upgrade our QNX 4 archive nodes which currently have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array. Which
would solve our current storage problems nicely, but it also opens up
the
possibility of combining multiple arrays for terabytes worth of disk on
a
single system. I know about the (yet to be documented anywhere but in
this
news group and QUICS archives > > -H option to Fsys and I would guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
The file size limit on disk is 2 GB
The partition size limit should be 2 GBlocks
Laveau.
“Rob” <> rob@spamyouself.com> > a écrit dans le message de news:
arjf1m$1d1$> 1@inn.qnx.com> …
KA-PING! Fsys (reasonable) maximum disk size? Anyone? PLEASE?
We are planning to upgrade our QNX 4 archive nodes which currently
have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array.
Which
would solve our current storage problems nicely, but it also opens up
the
possibility of combining multiple arrays for terabytes worth of disk
on
a
single system. I know about the (yet to be documented anywhere but
in
this
news group and QUICS archives > > -H option to Fsys and I would guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
A 1 terabyte partition size limit, eh. Is that also a total disk space
limit, or could there be, say multiple 1 terabyte partitions?
We’ve ordered the equipment for the upgrade by the way… I’ll post a
follow
up to let everyone know what works or doesn’t work >
Someone had performance problem when there was a large number of files in a
directory (Robert are you listeninig)
-Rob
“Laveau Saint-Clair” <> laveau@qnx.fr> > wrote in message
news:arlep3$4q7$> 1@nntp.qnx.com> …
The file size limit on disk is 2 GB
The partition size limit should be 2 GBlocks
Laveau.
“Rob” <> rob@spamyouself.com> > a écrit dans le message de news:
arjf1m$1d1$> 1@inn.qnx.com> …
KA-PING! Fsys (reasonable) maximum disk size? Anyone? PLEASE?
We are planning to upgrade our QNX 4 archive nodes which currently
have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array.
Which
would solve our current storage problems nicely, but it also opens
up
the
possibility of combining multiple arrays for terabytes worth of disk
on
a
single system. I know about the (yet to be documented anywhere but
in
this
news group and QUICS archives > > -H option to Fsys and I would
guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of
disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in
the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for
Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
A 1 terabyte partition size limit, eh. Is that also a total disk space
limit, or could there be, say multiple 1 terabyte partitions?
We’ve ordered the equipment for the upgrade by the way… I’ll post a
follow
up to let everyone know what works or doesn’t work >
Someone had performance problem when there was a large number of files in a
directory (Robert are you listeninig)
No problems now that I’ve boosted -H to something stooopid; my “eatfds”
program can open ~900 files without getting the “too many open files”
error now. All is well. Directory problems went away as well.
That said, I still try to not have more than 256 files/dir just on
general principles. Use the tree-like nature of the filesystem to
solve this…
Cheers,
-RK
-Rob
“Laveau Saint-Clair” <> laveau@qnx.fr> > wrote in message
news:arlep3$4q7$> 1@nntp.qnx.com> …
The file size limit on disk is 2 GB
The partition size limit should be 2 GBlocks
Laveau.
“Rob” <> rob@spamyouself.com> > a ecrit dans le message de news:
arjf1m$1d1$> 1@inn.qnx.com> …
KA-PING! Fsys (reasonable) maximum disk size? Anyone? PLEASE?
We are planning to upgrade our QNX 4 archive nodes which currently
have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array.
Which
would solve our current storage problems nicely, but it also opens
up
the
possibility of combining multiple arrays for terabytes worth of disk
on
a
single system. I know about the (yet to be documented anywhere but
in
this
news group and QUICS archives > > -H option to Fsys and I would
guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of
disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in
the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for
Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
TIA
-Rob
\
–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.
One other thing to note, is what will the driver support (not Fsys).
E.g. Fsys.eide will only support upto 137GB due to the 28Bit addressing limit
in the BIOS (note even if you upgrade your BIOS this is still a limit on this
driver).
You’ll be fine wrt your 74Gig drives/arrays though.
We are planning to upgrade our QNX 4 archive nodes which currently have a
total of 74 Gig of disk space each. It seems there are some RAID solutions
out there that offer support for up to 520 Gig in a single array. Which
would solve our current storage problems nicely, but it also opens up the
possibility of combining multiple arrays for terabytes worth of disk on a
single system. I know about the (yet to be documented anywhere but in this
news group and QUICS archives > > -H option to Fsys and I would guess that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger? Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
Thanks for the info Erick. We’re going to be using an Ultra 160 SCSI RAID
system and talk to it via Fsys.aha8scsi. Any such limits in that driver?
FYI… We’re upgrading from 74G of disk to whatever we can get to work
that’s bigger. So yes, 74G systems do run just fine, they have been for
about 4 years now The RAID system we’ve ordered will support up to
580G. We’ll be thoroughly testing all this before putting anything into
production. Probably start with ~150G and keep adding drives to the array
to see what the real limit is.
One other thing to note, is what will the driver support (not Fsys).
E.g. Fsys.eide will only support upto 137GB due to the 28Bit addressing
limit
in the BIOS (note even if you upgrade your BIOS this is still a limit on
this
driver).
You’ll be fine wrt your 74Gig drives/arrays though.
We are planning to upgrade our QNX 4 archive nodes which currently have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array. Which
would solve our current storage problems nicely, but it also opens up
the
possibility of combining multiple arrays for terabytes worth of disk on
a
single system. I know about the (yet to be documented anywhere but in
this
news group and QUICS archives > > -H option to Fsys and I would guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
A 1 terabyte partition size limit, eh. Is that also a total disk space
limit, or could there be, say multiple 1 terabyte partitions?
We’ve ordered the equipment for the upgrade by the way… I’ll post a
follow
up to let everyone know what works or doesn’t work >
-Rob
“Laveau Saint-Clair” <> laveau@qnx.fr> > wrote in message
news:arlep3$4q7$> 1@nntp.qnx.com> …
The file size limit on disk is 2 GB
The partition size limit should be 2 GBlocks
Laveau.
“Rob” <> rob@spamyouself.com> > a écrit dans le message de news:
arjf1m$1d1$> 1@inn.qnx.com> …
KA-PING! Fsys (reasonable) maximum disk size? Anyone? PLEASE?
We are planning to upgrade our QNX 4 archive nodes which currently
have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array.
Which
would solve our current storage problems nicely, but it also opens
up
the
possibility of combining multiple arrays for terabytes worth of disk
on
a
single system. I know about the (yet to be documented anywhere but
in
this
news group and QUICS archives > > -H option to Fsys and I would
guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of
disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in
the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for
Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
Thanks for the info Erick. We’re going to be using an Ultra 160 SCSI RAID
system and talk to it via Fsys.aha8scsi. Any such limits in that driver?
FYI… We’re upgrading from 74G of disk to whatever we can get to work
that’s bigger. So yes, 74G systems do run just fine, they have been for
about 4 years now > > The RAID system we’ve ordered will support up to
580G. We’ll be thoroughly testing all this before putting anything into
production. Probably start with ~150G and keep adding drives to the array
to see what the real limit is.
-Rob
“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:artu20$8d9$> 1@nntp.qnx.com> …
Hi Rob,
One other thing to note, is what will the driver support (not Fsys).
E.g. Fsys.eide will only support upto 137GB due to the 28Bit addressing
limit
in the BIOS (note even if you upgrade your BIOS this is still a limit on
this
driver).
You’ll be fine wrt your 74Gig drives/arrays though.
We are planning to upgrade our QNX 4 archive nodes which currently have
a
total of 74 Gig of disk space each. It seems there are some RAID
solutions
out there that offer support for up to 520 Gig in a single array. Which
would solve our current storage problems nicely, but it also opens up
the
possibility of combining multiple arrays for terabytes worth of disk on
a
single system. I know about the (yet to be documented anywhere but in
this
news group and QUICS archives > > -H option to Fsys and I would guess
that
we’d need to specify at minimum ~2.5 Meg of heap for 520 Gig of disk.
That’s fine, we’re planning on putting at least 1 Gig of memory in the
systems. BUT… Will Fsys support something that large? Or larger?
Has
anyone out there tried this? What is the theoretical maximum for Fsys
and/or an Fsys.* driver? … Anyone? … John G? … Bueller?
-H option to Fsys and I would guess that