Re: 200g harddisk after newfs = Available 174g?
bits are absolute. this discussion should take a turn to beck's ass again. On Thu, Oct 29, 2009 at 07:29:54PM +0100, Jurjen Oskam wrote: > On Wed, Oct 28, 2009 at 10:28:00AM +0100, Daniel Gracia Garallar wrote: > > > Computer programmers, OS and all around computer chit-chat use the > > prefix 'giga' to refer 2^30 = 1,073,741,824 bytes. > > > > IEC recommends calling this GiB, but it's uncommon. > > > > Today, you could assume safely only manufacturers write Gb in the > > International System meaning; everybody else is refering to GiBs when > > talking about Gb. > > ... except when talking about computer networks: in that case everybody > *does* use the SI-prefixes and 1 Gb/sec really is 10 bits/second, > and not 1073741824 bits/second. > > -- > Jurjen Oskam > > Savage's Law of Expediency: > You want it bad, you'll get it bad.
Re: 200g harddisk after newfs = Available 174g?
On Wed, Oct 28, 2009 at 10:28:00AM +0100, Daniel Gracia Garallar wrote: > Computer programmers, OS and all around computer chit-chat use the > prefix 'giga' to refer 2^30 = 1,073,741,824 bytes. > > IEC recommends calling this GiB, but it's uncommon. > > Today, you could assume safely only manufacturers write Gb in the > International System meaning; everybody else is refering to GiBs when > talking about Gb. ... except when talking about computer networks: in that case everybody *does* use the SI-prefixes and 1 Gb/sec really is 10 bits/second, and not 1073741824 bits/second. -- Jurjen Oskam Savage's Law of Expediency: You want it bad, you'll get it bad.
Re: 200g harddisk after newfs = Available 174g?
On Thu, Oct 29, 2009 at 10:13 AM, Bob Beck wrote: >> There are many stupid ideas in other operating systems, I >> don't see why we should be required to implement them. > > Yeah, and the discussion of my ass is a more productive discussion > than talking about making df display "marketing gigabytes" > > That'll happen in openbsd right after we switch the default filesystem > to apple hfs, and while we're at it replace the yp code with netinfo > because it's so much better. Would you also please switch all the config files to XML since it's the standard? -B
Re: 200g harddisk after newfs = Available 174g?
On Fri, Oct 30, 2009 at 12:13 AM, Bob Beck wrote: >> There are many stupid ideas in other operating systems, I >> don't see why we should be required to implement them. > > Yeah, and the discussion of my ass is a more productive discussion > than talking about making df display "marketing gigabytes" > for some reason I'm kind of offended by "SI = marketing" equation. note that I'm not suggesting anything. Things like this are already confusing and changing anything will probably just add even more confusion, etc. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Re: 200g harddisk after newfs = Available 174g?
> There are many stupid ideas in other operating systems, I > don't see why we should be required to implement them. Yeah, and the discussion of my ass is a more productive discussion than talking about making df display "marketing gigabytes" That'll happen in openbsd right after we switch the default filesystem to apple hfs, and while we're at it replace the yp code with netinfo because it's so much better.
Re: 200g harddisk after newfs = Available 174g?
On Thu, Oct 29, 2009 at 11:35:18PM +0700, Edho P Arief wrote: > On Wed, Oct 28, 2009 at 4:28 PM, Daniel Gracia Garallar > wrote: > > Manufactures use the 'giga' prefix in the International System meaning. That > > said, 1Gb would be 10^9 = 1,000,000,000 bytes. > > > > Computer programmers, OS and all around computer chit-chat use the prefix > > 'giga' to refer 2^30 = 1,073,741,824 bytes. > > > > IEC recommends calling this GiB, but it's uncommon. > > > > Today, you could assume safely only manufacturers write Gb in the > > International System meaning; > > and Apple's Mac OS X 10.6 > > http://support.apple.com/kb/TS2419 There are many stupid ideas in other operating systems, I don't see why we should be required to implement them.
Re: 200g harddisk after newfs = Available 174g?
On Wed, Oct 28, 2009 at 4:28 PM, Daniel Gracia Garallar wrote: > Manufactures use the 'giga' prefix in the International System meaning. That > said, 1Gb would be 10^9 = 1,000,000,000 bytes. > > Computer programmers, OS and all around computer chit-chat use the prefix > 'giga' to refer 2^30 = 1,073,741,824 bytes. > > IEC recommends calling this GiB, but it's uncommon. > > Today, you could assume safely only manufacturers write Gb in the > International System meaning; and Apple's Mac OS X 10.6 http://support.apple.com/kb/TS2419 -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Re: 200g harddisk after newfs = Available 174g?
Manufactures use the 'giga' prefix in the International System meaning. That said, 1Gb would be 10^9 = 1,000,000,000 bytes. Computer programmers, OS and all around computer chit-chat use the prefix 'giga' to refer 2^30 = 1,073,741,824 bytes. IEC recommends calling this GiB, but it's uncommon. Today, you could assume safely only manufacturers write Gb in the International System meaning; everybody else is refering to GiBs when talking about Gb. Sum this fact with filesystem overhead, and you may get all your space! Jennifer Ma escribis: hi all, lately, i obtained a seagate 200g(wd1) harddisk from my elder brother, after i disklabel, newfs and mount the disk. only 174g is shown as available, in windows(through samba), said 9.16g already been used. is there any way i can claim those space back? much thanks! # disklabel wd1 # /dev/rwd1c: type: ESDI disk: ESDI/IDE disk label: ST3200826A flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 390721968 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:390721905 63 4.2BSD 2048 163841 c:3907219680 unused # df -h # Filesystem SizeUsed Avail Capacity Mounted on /dev/wd0a 1.8G1.4G313M82%/ /dev/wd1a 183G2.0K174G 0%/www01
Re: 200g harddisk after newfs = Available 174g?
On 28 Oct 2009 at 14:59, Jennifer Ma wrote: > hi all, lately, i obtained a seagate 200g(wd1) harddisk from my elder > brother, after i disklabel, newfs and mount the disk. only 174g is > shown as available, in windows(through samba), said 9.16g already been > used. is there any way i can claim those space back? much thanks! > ... > bytes/sector: 512 > total sectors: 390721968 Harddisk manufacturers gigabyte != computer gigabyte $ bc scale=2 390721968*512/10^9 200.04 390721968*512/2^30 186.31 So, you have a 186GB disk
Re: 200g harddisk after newfs = Available 174g?
On Wed, 28 Oct 2009 14:59:01 +0800 Jennifer Ma wrote: > hi all, lately, i obtained a seagate 200g(wd1) harddisk from my elder > brother, after i disklabel, newfs and mount the disk. only 174g is > shown as available, in windows(through samba), said 9.16g already been > used. is there any way i can claim those space back? much thanks! > > # disklabel wd1 > # /dev/rwd1c: > type: ESDI > disk: ESDI/IDE disk > label: ST3200826A > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 16 > sectors/cylinder: 1008 > cylinders: 16383 > total sectors: 390721968 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 16 partitions: > #size offset fstype [fsize bsize cpg] > a:390721905 63 4.2BSD 2048 163841 > c:3907219680 unused > > > # df -h > # Filesystem SizeUsed Avail Capacity Mounted on > /dev/wd0a 1.8G1.4G313M82%/ > /dev/wd1a 183G2.0K174G 0%/www01 newfs(8): -m free-space The percentage of space reserved from normal users; the mini- mum free space threshold. The default value used is 5%. See tunefs(8) for more details on how to set this option. tunefs(8): -m minfree This value specifies the percentage of space held back from nor- mal users; the minimum free space threshold. The default value is set during creation of the filesystem; see newfs(8). This value can be set to zero, however up to a factor of three in throughput will be lost over the performance obtained at a 5% threshold. Note that if the value is raised above the current usage level, users will be unable to allocate files until enough files have been deleted to get under the higher threshold. - Robert
Re: 200g harddisk after newfs = Available 174g?
Hi Jennifer, On Wed, Oct 28, 2009 at 02:59:01PM +0800, Jennifer Ma wrote: | 16 partitions: | #size offset fstype [fsize bsize cpg] | a:390721905 63 4.2BSD 2048 163841 | c:3907219680 unused | | | # df -h | # Filesystem SizeUsed Avail Capacity Mounted on | /dev/wd0a 1.8G1.4G313M82%/ | /dev/wd1a 183G2.0K174G 0%/www01 390721905 sectors of 512 bytes each gives you 200049615360 bytes of storage. That's ~195360952 kilobyte or ~190782 megabyte or ~186 gigabyte. Unlike storage vendors, df considers a kilobyte to be 1024 bytes, a megabyte to be 1048576 bytes and a gigabyte to be 1073741824 bytes; storage vendors take the mega and giga prefixes to take their original SI meaning. (there's even a small army gathering on the internet that wants everybody to use special terms for these amounts, but you can safely ignore them as it doesn't really matter all that much for practical purposes) Add to this the fact that the filesystem reserves 5% of space for "overflowing" purposes (which can only be used by root) and the numbers add up nicely. For more details on the reserved space, see the tunefs(8) manpage, specifically the -m option. Cheers, Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: 200g harddisk after newfs = Available 174g?
Two words: Filesystem Overhead. On Tue, Oct 27, 2009 at 11:59 PM, Jennifer Ma wrote: > hi all, lately, i obtained a seagate 200g(wd1) harddisk from my elder > brother, after i disklabel, newfs and mount the disk. only 174g is > shown as available, in windows(through samba), said 9.16g already been > used. is there any way i can claim those space back? much thanks! > > # disklabel wd1 > # /dev/rwd1c: > type: ESDI > disk: ESDI/IDE disk > label: ST3200826A > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 16 > sectors/cylinder: 1008 > cylinders: 16383 > total sectors: 390721968 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 16 partitions: > #size offset fstype [fsize bsize cpg] > a:390721905 63 4.2BSD 2048 163841 > c:3907219680 unused > > > # df -h > # Filesystem SizeUsed Avail Capacity Mounted on > /dev/wd0a 1.8G1.4G313M82%/ > /dev/wd1a 183G2.0K174G 0%/www01