Disk size measured incorrectly.
Hello once again boys and girls. I added two drives to my server via /stand/sysinstall. they are one western digital, 120 gig and a maxtor, 120 gig. This is what i see via df /dev/ad1s1e 113G89G15G86%/mirror /dev/ad2s1e 110G12K 101G 0%/mirror2 I dont _need_ the space. Not even close. but it cant hurt to use the disk at its most, and mostly though im obsessive compulsive and i would prefer to see the output below :) as i got another 120 gig drive on the way. Did i initialize them wrong or something? The bios is set to have both drives auto detected and the access mode is auto as well. Thanks guys. /dev/ad1s1e 120G89G15G86%/mirror /dev/ad2s1e 120G12K 101G 0%/mirror2 -- Independent WWW/FreeBSD/Linux/Unix consultant, email me for more information. Founder/WebMaster/ The unixhideout network http://www.unixhideout.com [EMAIL PROTECTED] - Free, secure and stable email from UnixHideout The UnixHideout network http://www.unixhideout.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Disk size measured incorrectly.
On Thu, Mar 13, 2003 at 07:40:02PM -0500, Michael wrote: Hello once again boys and girls. I added two drives to my server via /stand/sysinstall. they are one western digital, 120 gig and a maxtor, 120 gig. This is what i see via df /dev/ad1s1e 113G89G15G86%/mirror /dev/ad2s1e 110G12K 101G 0%/mirror2 I dont _need_ the space. Not even close. but it cant hurt to use the disk at its most, and mostly though im obsessive compulsive and i would prefer to see the output below :) as i got another 120 gig drive on the way. Did i initialize them wrong or something? The bios is set to have both drives auto detected and the access mode is auto as well. Thanks guys. /dev/ad1s1e 120G89G15G86%/mirror /dev/ad2s1e 120G12K 101G 0%/mirror2 The drive manufacturers are probably measuring a gigabyte at 1 billion byes, whereas as true gigabyte, in binary terms is 1073741824 bytes. Dividing 1200/1073741824 yields about 112GB, or close to what you are seeing. Although, this is just a guess. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc pgp0.pgp Description: PGP signature
Re: Disk size measured incorrectly.
On Thu, Mar 13, 2003 at 07:40:02PM -0500, Michael wrote: Hello once again boys and girls. I added two drives to my server via /stand/sysinstall. they are one western digital, 120 gig and a maxtor, 120 gig. This is what i see via df /dev/ad1s1e 113G89G15G86%/mirror /dev/ad2s1e 110G12K 101G 0%/mirror2 I dont _need_ the space. Not even close. but it cant hurt to use the disk at its most, and mostly though im obsessive compulsive and i would prefer to see the output below :) as i got another 120 gig drive on the way. Did i initialize them wrong or something? The bios is set to have both drives auto detected and the access mode is auto as well. Thanks guys. /dev/ad1s1e 120G89G15G86%/mirror /dev/ad2s1e 120G12K 101G 0%/mirror2 Don't forget that 8% of the drive (by default, it's configurable) is reserved. Thus, a drive that shows 110G is actually right about 120G in size (110 * 1.08 = 118.8). `tunefs -p device` will give you the actual value that is reserved for any particular filesystem. -T -- Page 30: Leaving a terminal logged in is like leaving your car unlocked with the keys in the ignition. - Harley Hahn, _The Unix Companion_ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
