Disk size supported by statfs

Hello,
What is the exact limit of disk size which the statfs command supports?
Regards,
Yael

This question is a good candidate for one of OpenSolaris forums: http://www.opensolaris.org/jive/index.jspa?categoryID=1
Not sure if you can get help here, where Sun Studio dbx, analyzer, collector and similar stuff is being discussed.

Similar Messages

DV9000 Maximum Hard Disk Size Supported?

I'm searching for a used HP Pavilion DV9000. I need to know the maximum hard disk size the DV9000 series laptops support. To be clear, could I put a 750G or 1TB disk in each bay?
HP's web site isn't helpful. It gives only the "official" numbers at time of release which state it supports up to 240G, 120 in each bay. Those kinds of numbers are almost never an accurate statement of the limitation as I have seen similar "official" numbers for other HP laptops (supposedly limited to 120G or 250G or whatever) that have no problem supporting 640G in the real world.
The size of hard disk a computer supports is usually a function of the main board's chipset and I don't know how to determine the exact chipset or find the chipset's hard disk support capability. Again, HP's web site isn't helpful here either. They may list it has an nVidia chipset; but, they don't mention which nVidia chipset.
To be clear, I don't own a DV9000 yet and I need to know how to find this information maybe with the exact model number. The model series may be DV9000; but, there are dozens of more exacting model numbers on the bottoms of the DV9000 series computers (example: DV9025ea). I don't want to purchase a DV9000 and then find that its limitation really is 120G per bay.

Hard drive size is a limitation of the Bios, not the chipset, this was overcome with the implementation of Large Block Addressing 48bit in modern bios's in 2003
Hp does not state which bios's on older laptops support this or not.
Looking at the production dates of the 9000 series, I would be willing to bet it supports any size hard drive (48bit LBA), since 48bit LBA was introduced in 2003
http://en.wikipedia.org/wiki/Logical_block_addressing
That being said, there could be brand compatibility issues, so be sure to buy the hard drives from a source that has a friendly return policy.
Maybe some one can post that has actually installed a large hard drive in a 9000 series.

What's the maximum support disk size on v440

Hi,
My v440 have now 4x72GB disks, I want to replace them with 300GB or more. Did any one tested it? I know 146GB disks are supported but not enough.
Thanks..

If you have the system covered by a support contract, then you should keep only disks that have been qualified by Sun/Oracle to function. If you do not have support contract coverage, then you use whatever you want to use. It is your system, your property, so do with it as you wish.
If there is a contract that covers that system and you put unqualified components into it, you simply suspend any and all privileges for support or repairs. That's all.

MS 6147 max memory and disk sizes

For the MS 6147 can anybody confirm the max Hard disk size and max memory.
It will not recognise the 40Gb HD I am trying to fit, and only recognises half of the 256Mb memeory simm I have fitted.
The BIOS version is 1.9 but I think that is a 'special' by Packard Bell. The MSI BIOS download site makes no mention of disk problems rectified right up to V1.8 which is the latest, with the exception of one for the ZX chipset only which addresses EDMA 66 problem.
Anybody got a definitive answer on this?

Supports a maximum memory size of 256MB (8M x 8) or
512MB (16M x 4) registered DIMM only
how many chips on dimm is what counts with older boards
go to drive makers web site get jumper settings to limit it to 32gb and try

Maximum disk size?

That's the maximum disk size or volume size supported? Thanks for any insights.

The maximum volume size, and file size, in Mac OS X 10.4 or later, is close to 8 EB (exabyte, or 10**18 bytes). The actual number is 2**63 - 2**31.
See Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits

Silly question regarding sol 8 containers and disk sizes

I've got what is probably just about the silliest question, but I can't seem to find an answer whilst searching around for the past couple of hours. Say I have 2 boxen, one is a sol 8 server and the other is a brand new install of sol 10/8. They have the exact same hardware, including disk size. If I want to turn the first box into a solaris 8 container running under the second, how do I reconcile the fact that the disk sizes are the same? The sol 8 box is only using, say, 25-30GB of the 72GB on the disk. Do I have to resize the slice into something smaller to enable it fit into a container on the second server? It would seem that is the case, but I didn't know if there was some magic I was not aware of. I've not done a ufsdump or flash archive before so I don't know if the 'empty' space on the disc will be disregarded, possibly allowing me to squeeze it onto my sol 10 server and allow me to resize it smaller in zfs. This topic isn't touched in all the tutorials I've read, so I assume it's either a completely retarded/braindead concern, or everyone always migrates these boxen onto servers with much more in the way of resources.
Sorry if I offended anyone with my ignorance ; P

No. Solaris8/9 containers make use the "branded zones" technology. But it's still the same thing and there's no "disk image", at least not like you might think of for VMware or Xen.
Now if you want to call a ufsdump or flash archive an "image", then that's fine. But you can see in either case, the free space or minor changes is size are irrelevant. You're just copying files. It's a system image, not a "disk image".
                  Installer Options :
                        Option          Description
                        -a filepath     Location of archive from which to copy system image.
                                        Full flash archive and cpio, gzip compressed cpio,
                                        bzip compressed cpio, and level 0 ufsdump are
                                        supported. Refer to the gzip man page available in the
                                        SUNWsfman package.--
Darren

I need collect some system information like free disk size how can i do ?

I wrote a backup applications on client/server style. But i can collect some information about system like free disk size , running application or running services( especially on windows).
i know i can do with using system commands like dir, ls etc..
But i want to collect this sysem informations with native java api and codes.
Dou you know any java api ?
Please i need help urgent ...

There is nothing in Java to do that. The Java language is independent of the os, and doesn't support (many) os-specific attributes.

D1000 Max Disk Size

I have found conflicting information. I am hoping one if the experts here can help. I am trying to find out what the max disk size is for the D1000's. The handbook says 73GB but the sunstore sells 146GB drives that are for the D1000. So which is it? I don't want to buy 12 x 146GB drives to find they won't work in that configuration.
http://sunsolve.sun.com/handbook_pub/Systems/D1000/component s.html#Disks
http://sunsolve.sun.com/handbook_pub/Systems/D1000/D1000.htm l
Thanks!

Hello Andrew,
the 146GB disks are listed in the <b>Full Components List</b> (your first link). If you order the disks from Sun, you can confirm that information.
While the disks work in the D1000, you should keep in mind that the disk array is attached with Ultra40 and these disks are Ultra320. The disks are capable of a much higher transfer rate than the connection can support.
Michael

OEL5 disk size

Hi All,
I've just installed OEL5 update 3. I have a problem understanding my disk size.
If I type: fdisk -l |grep Disk I got 2 lines:
Disk /dev/sda 320.0 GB
Disk /dev/sdb 250.0 GB
that make sense to me cause it's exactly my hard disk on the hardware, but if I type df - K , i got:
/dev/mapper/VolGroup00-LogVol00 233G Mounted on /
/dev/sdb1 104M Mounted on /boot
tmpfd 4G Mounted on /dev/shm
What's wrong with this configuration, where is the 320 GB disk?
Thanks a lot
Claudio

Well, if you read the piece carefully, you knew you have to query the physical volumes of your system (pvdisplay)
that would reveal that the (ntfs formatted) disk was not part of the current lvm configuration.
next, a little search on the big internet shows how you can use ntfs with oel5/rhel5: http://platonic.techfiz.info/2008/10/23/ntfs-support-on-rhel5/

Disk utility gives "Error: Partition map repair failed while adjusting structures to fit current whole disk size"

I am getting the following error when running Disk Utility (under ML) on an exteral USB hard drive:
Error: Partition map repair failed while adjusting structures to fit current whole disk size.
I get thsi when I ask Disk Utility to "Repair Disk" at the top level of the disk hierarchy (i.e. not on one of the partitions within the disk but on the disk itself). I was not getting this error with Lion on the same disk before I upgraded from Lion to ML.
It seems like a bug in ML. I found websites where they suggest that you just run Lion's Disk Utility and it will show the disk to be fine.
Any thoughts?

So, I finally seemed to have resolved things with the Seagate 4TB Firewire external drive. If you Google about, you will find a thread on Seagate's own support forum that describes how to disable the sleep function on the drive. You CANNOT ALLOW THE DRIVE TO SLEEP WHILE CONNECTED TO YOUR MAC.
After a lot of reading, here's what I think is happening: the drive goes to sleep, after some period of inactivity, and when you shutdown your Mac, OS X tries to write something to the drive as part of the dismount / disconnect / shutdown process. That fails in some manner, leaving the drive 'corrupted' at the filesystem or partition level.
Then, on the next boot-up, Mountain Lion tells you that it cannot repair the drive and it mounts as read only. Your only fix at that point is to re-partition / re-format and start over (which is big fun with 3TB of data to copy back on to the drive).
If you prevent the drive from sleeping, whenever it's connected to the MacBook, then the above process doesn't occur and voila, the drive just works. So far, I haven't had any problems with about a week of starting / shutting down my MacBook connected to the offending drive (translation: I was going to return the drive, but the problem is clearly with Mac OS X Mountain Lion).

Disk size in Solaris 10

I have some confusion about disk subsystem in Solaris, i am trying to clarify from this forum.
I have recently installed Solaris 10 in one SPARC box. After i installed, the format gives the bellow output.
0 root wm 19491 - 29648 4.88GB (10158/0/0) 10239264
1 swap wu 0 - 4062 1.95GB (4063/0/0) 4095504
2 backup wm 0 - 29648 14.25GB (29649/0/0) 29886192
From the above output, is the size of my disk is 14 GB ?, or the size of my disk is 14+2+5=21 GB ?
I am trying to learn ZFS, so i want another partition in this disk so that i create ZFS on that partition.
I have gone to single user mode by using CD. I assumed that, from the above "format" command output, i thought i have 21GB of disk size and 14GB of free space. So i created another partition with 14GB. Now the format command gives bellow output.
0 root wm 19491 - 29648 4.88GB (10158/0/0) 10239264
1 swap wu 0 - 4062 1.95GB (4063/0/0) 4095504
2 backup wm 0 - 29648 14.25GB (29649/0/0) 29886192
3 reserved wm 0 - 29127 14.00GB (29128/0/0) 29361024
When i am creating ZFS, it given me a warning that the the partition i have specified is spanned into root partition (first partition), and it mentioned to use "-f" option.
With "-f", it created successfully.
If i assume now that the size of my disk is 14GB only then,
(1) how come two partitions are pointing to the same area in the disk ?
(2) How come two different filesystems are pointing to the same area ?
Please anyone clarify my doubts. Thank you.

Assuming a standard labeled disk it is standrad practice to have section/slice 2 being 'whole disk' for purposes of 'backup'. That would tend to indicate you have a 14GB disk. A prtvtoc /dev/dsk/c?t?d?s2 (change the ?s to the right values) will give a little more on the disk geometry.
In the display from format column 4 is the start cylinder of the partition and column 5 is the end cylinder. From the first set out output it looks like cyclinders 4063 to 19490 are not allocated
In the second set you have created a new slice (section 3) that overlaps both sections 0 and 1 - which is generally considered to be bad!

Is there a max SATA disk size in OSX 10.4.11 and G4/1.25?

Hello,
I am trying to set up a G4/1.25 (2 gig in memory) as a fileserver with a SATA card and 2 x 3 TB seagate disks. This is the setup:
http://lowendmac.com/ppc/mdd-power-mac-g4-1.25-ghz.html
http://firmtek.com/seritek/seritek-1v4/
http://eshop.macsales.com/item/Seagate/ST3000DM001/
The system is OSX 10.4.11. I am unable to initialize the disks in disk utility. The process starts but then halts and says that it can not continue.
My question is if there is a max disk size in OSX 10.4.11?
Any help greatly appriceated.
Best regards,
Ingolfur Bruun

Hello again,
I tried to work my way around armed with your input and succeeded
By using a FireWire dock I was able to see the disks in 10.4.11. What I did was to partition the disks with ONE partition in Disk Utility and then format with GUID partitioning scheme instead of the Apple Partition Mapping scheme which I had done before. And as I am using a ATA disk as a startup disk it dosen't matter if the 3 TB disks are not bootable. They will only be used for data, not as system disks.
You saved my day! Thanks again.
Best regards,
Ingolfur

MacBook in target disk mode shows incorrect disk size

My 80 GB hard drive in MacBook has gone bad (the filesystem is in inconsistent state). I connected it to an iMac in Target Disk Mode. It shows up (unmounted) but the capacity reported by Disk Utility is 20 GB. Does someone know why is that? Is it due to the corrupt filesystem?
I am afraid that given this situation, if I buy and run DiskWarrior, that too might not be able to see the full disk and fail to repair it. Note that if I boot my MacBook using the Apple CD, the Disk Utility shows the correct disk size.
Thanks.

If you have a disk that is in really, really bad shape to the point that Disk Utility looks at you like a 5 year old that just spilled a glass of apple juice on the kitchen floor, it's time to bring in the big guns.
DiskWarrior.
I love it, I love it. If someone has something bad to say about it, they are lying. If there is a chance that you can get everything back to normal without spending the huge dough to send your drive out to be dismantled in a clean room, DiskWarrior is that chance.
It's worth every single penny.
Let me know if you have other queries.

Re-read disk size in Solaris 10 x86 / VMware

Hi
Using
# uname -a
SunOS host1 5.10 Generic_142910-17 i86pc i386 i86pc
We have a 30G virtual disk, on top of which a UFS filesystem is living, mounted, and used.
The Virtual disk has been resized to 40G.
I know I need to change the fdisk partition size, after which i can change the "format" partition size, then use growfs.
But I don't know how to get S10 to recognise the new size for the disk.
fdisk tells me
Total disk size is 3916 cylinders
Cylinder size is 16065 (512 byte) blocks
Cylinders
Partition   Status
Type
Start   End   Length
=========   ======
============ =====   ===   ======   ===
1
Active
Solaris2
1 3915
3915
100
# prtvtoc -h /dev/dsk/c1t2d0s2
       0      0    00      16065 62846280 62862344   /xxx
       2      5    01          0 62862345 62862344
       8      1    01          0     16065     16064
# df -h /xxx
Filesystem             size   used avail capacity Mounted on
/dev/dsk/c1t2d0s0       30G    29G   498M    99%    /xxx
On Linux I might use partprobe or blockdev --rereadpt but on Solaris?
Cheers
KM

Hello
this document should help, but make a backkup before running it
How to expand a UFS Lun in Solaris 10 (Doc ID 1451858.1)
Regards
Eze

Disk size in ise

Hi
I have a strange problem after instaling licenses in ISE the following information is in a "show tech"
This info is for 1.3 clean install + license.
% WARNING: ISE DISK SIZE NOT LARGE ENOUGH FOR PRODUCTION USE
% RECOMMENDED DISK SIZE: 200 GB, CURRENT DISK SIZE: 0 GB
It is the same in the Eval version but in this server there is a 2500 license
The same is observed in both ISE 1.2.1 and 1.3 (running a POC on ISE)
When trying to upgrade ISE 1.2.1 > 1.3 the following output
Getting bundle to local machine...
md5: ad7d87d383661bce671804a9e125e42b
sha256: 2a7ebe5196e3d956ac42ec2e5acdf3815a3e0f80db954b58e2c68843bb3c42fd
% Please confirm above crypto hash matches what is posted on Cisco download site.
% Continue? Y/N [Y] ? Y
Unbundling Application Package...
Initiating Application Upgrade...
% Warning: Do not use Ctrl-C or close this terminal window until upgrade completes.
-Checking VM for minimum hardware requirements
% Error: At least 100GB sized hard disk required for upgrade.
the disk is
Hard Disk Count(*): 1
Disk 0: Device Name: /dev/sda
Disk 0: Capacity: 644.20 GB
Disk 0: Geometry: 255 heads 63 sectors/track 78325 cylinders
Thanks
Erik Loeth

Attached is the output from VMware, this is made with the OVA
ISE-1.3.0.876-virtual-SNS3495-2.ova
The disk output from show inventory
NAME: "ISE-VM-K9 chassis", DESCR: "ISE-VM-K9 chassis"
PID: ISE-VM-K9 , VID: V01 , SN: XXXXXXXXXXXXXXX
Total RAM Memory: 16467264 kB
CPU Core Count: 4
CPU 0: Model Info: Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz
CPU 1: Model Info: Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz
CPU 2: Model Info: Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz
CPU 3: Model Info: Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz
Hard Disk Count(*): 1
Disk 0: Device Name: /dev/sda
Disk 0: Capacity: 644.20 GB
Disk 0: Geometry: 255 heads 63 sectors/track 78325 cylinders
NIC Count: 1
NIC 0: Device Name: eth0
NIC 0: HW Address: XXXXXXXXXXXXXXXXXX
NIC 0: Driver Descr: Intel(R) PRO/1000 Network Driver
(*) Hard Disk Count may be Logical.
Reards
Erik Loeth

Disk size supported by statfs

Similar Messages

Maybe you are looking for