Hi all;

I have an E450 running Solaris 2.8, not up to patch level for various
reasons. I am attached via an Emulex HBA to a Network Appliance
storage array. I want to mount the disks as simple slices (Veritas
Volume Manager will not recognize the disks), and I am curious why I
see more space on the file system than I have allocated. Here's an
specific example:

1) created a 107GB LUN on the NetAPP filer
2) set the partition table on the device on the server for slice 0 to
be the whole thing:

Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 6443 106.98GB (6444/0/0)
224354304
1 unassigned wu 0 0
(0/0/0) 0
2 backup wu 0 - 6443 106.98GB (6444/0/0)
224354304
3 unassigned wm 0 0
(0/0/0) 0
4 unassigned wm 0 0
(0/0/0) 0
5 unassigned wm 0 0
(0/0/0) 0
6 unassigned wu 0 0
(0/0/0) 0
7 unassigned wm 0 0
(0/0/0) 0

3) make a new file system specifying 1% minfree:

[root@mcghosng:/] # newfs -m 1 /dev/rdsk/c6t500A098185C60EC2d25s0
newfs: construct a new file system /dev/rdsk/c6t500A098185C60EC2d25s0:
(y/n)? y
/dev/rdsk/c6t500A098185C60EC2d25s0: 224354304 sectors in 6444
cylinders of 16 tracks, 2176 sectors
109548.0MB in 2148 cyl groups (3 c/g, 51.00MB/g, 6208 i/g)

** Note that the geometry shows 109.5 GB in size? **

4) mount it up and check the space:
[root@mcghosng:/] # mount -F ufs /dev/dsk/c6t500A098185C60EC2d25s0 /
mnt

[root@mcghosng:/] # df -k /mnt
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c6t500A098185C60EC2d25s0
110475886 9 109371119 1% /mnt

As you can see, I have 110 GB of space as the size, of which 109 is
available. What gives here?

Any thoughts appreciated. I'm stumped/concerned

Thanks as always.....

Joe D.

In comp.sys.sun.admin Joe D. <newbie_from_newbie@yahoo.com> wrote:
[KB vs MB vs GB]
> Any thoughts appreciated. I'm stumped/concerned

1024 KB = 1 MB
1024 MB = 1 GB
1048576 KB = 1024 MB = 1 GB

Jens

On Jun 21, 1:53 pm, "Joe D." <newbie_from_new...@yahoo.com> wrote:
> Hi all;
>
> I have an E450 running Solaris 2.8, not up to patch level for various
> reasons. I am attached via an Emulex HBA to a Network Appliance
> storage array. I want to mount the disks as simple slices (Veritas
> Volume Manager will not recognize the disks), and I am curious why I
> see more space on the file system than I have allocated. Here's an
> specific example:
>
> 1) created a 107GB LUN on the NetAPP filer
> 2) set the partition table on the device on the server for slice 0 to
> be the whole thing:
>
> Part Tag Flag Cylinders Size Blocks
> 0 root wm 0 - 6443 106.98GB (6444/0/0)
> 224354304
> 1 unassigned wu 0 0
> (0/0/0) 0
> 2 backup wu 0 - 6443 106.98GB (6444/0/0)
> 224354304
> 3 unassigned wm 0 0
> (0/0/0) 0
> 4 unassigned wm 0 0
> (0/0/0) 0
> 5 unassigned wm 0 0
> (0/0/0) 0
> 6 unassigned wu 0 0
> (0/0/0) 0
> 7 unassigned wm 0 0
> (0/0/0) 0
>
> 3) make a new file system specifying 1% minfree:
>
> [root@mcghosng:/] # newfs -m 1 /dev/rdsk/c6t500A098185C60EC2d25s0
> newfs: construct a new file system /dev/rdsk/c6t500A098185C60EC2d25s0:
> (y/n)? y
> /dev/rdsk/c6t500A098185C60EC2d25s0: 224354304 sectors in 6444
> cylinders of 16 tracks, 2176 sectors
> 109548.0MB in 2148 cyl groups (3 c/g, 51.00MB/g, 6208 i/g)
>
> ** Note that the geometry shows 109.5 GB in size? **
>
> 4) mount it up and check the space:
> [root@mcghosng:/] # mount -F ufs /dev/dsk/c6t500A098185C60EC2d25s0 /
> mnt
>
> [root@mcghosng:/] # df -k /mnt
> Filesystem kbytes used avail capacity Mounted on
> /dev/dsk/c6t500A098185C60EC2d25s0
> 110475886 9 109371119 1% /mnt
>
> As you can see, I have 110 GB of space as the size, of which 109 is
> available. What gives here?
>
> Any thoughts appreciated. I'm stumped/concerned
>
> Thanks as always.....
>
> Joe D.

df -h /mnt

In article <1182430411.424408.264410@m36g2000hse.googlegroups .com>,
Joe D. <newbie_from_newbie@yahoo.com> wrote:
>Hi all;
>
>I have an E450 running Solaris 2.8, not up to patch level for various
>reasons. I am attached via an Emulex HBA to a Network Appliance
>storage array. I want to mount the disks as simple slices (Veritas
>Volume Manager will not recognize the disks), and I am curious why I
>see more space on the file system than I have allocated. Here's an
>specific example:
>
>1) created a 107GB LUN on the NetAPP filer
>2) set the partition table on the device on the server for slice 0 to
>be the whole thing:
>
>Part Tag Flag Cylinders Size Blocks
> 0 root wm 0 - 6443 106.98GB (6444/0/0)
>224354304
> 1 unassigned wu 0 0
>(0/0/0) 0
> 2 backup wu 0 - 6443 106.98GB (6444/0/0)
>224354304
> 3 unassigned wm 0 0
>(0/0/0) 0
> 4 unassigned wm 0 0
>(0/0/0) 0
> 5 unassigned wm 0 0
>(0/0/0) 0
> 6 unassigned wu 0 0
>(0/0/0) 0
> 7 unassigned wm 0 0
>(0/0/0) 0
>
>3) make a new file system specifying 1% minfree:
>
>[root@mcghosng:/] # newfs -m 1 /dev/rdsk/c6t500A098185C60EC2d25s0
>newfs: construct a new file system /dev/rdsk/c6t500A098185C60EC2d25s0:
>(y/n)? y
>/dev/rdsk/c6t500A098185C60EC2d25s0: 224354304 sectors in 6444
>cylinders of 16 tracks, 2176 sectors
> 109548.0MB in 2148 cyl groups (3 c/g, 51.00MB/g, 6208 i/g)
>
>** Note that the geometry shows 109.5 GB in size? **
>
>4) mount it up and check the space:
>[root@mcghosng:/] # mount -F ufs /dev/dsk/c6t500A098185C60EC2d25s0 /
>mnt
>
>[root@mcghosng:/] # df -k /mnt
>Filesystem kbytes used avail capacity Mounted on
>/dev/dsk/c6t500A098185C60EC2d25s0
> 110475886 9 109371119 1% /mnt
>
>As you can see, I have 110 GB of space as the size, of which 109 is
>available. What gives here?
>
>Any thoughts appreciated. I'm stumped/concerned

110475886KB / 1024 / 1024 = 105.358GB

-tom
--

"You can only be -so- accurate with a claw-hammer." --me

In article <1182431287.064513.54970@q69g2000hsb.googlegroups. com>,
Franco S. <franco_spencer@yahoo.com> wrote:
>On Jun 21, 1:53 pm, "Joe D." <newbie_from_new...@yahoo.com> wrote:
>> Hi all;
>>
>> I have an E450 running Solaris 2.8, not up to patch level for various
>> reasons.
>
>df -h /mnt

Didn't thing "-h" was added to `df` until Solaris 9?

-tom
--

"You can only be -so- accurate with a claw-hammer." --me

D'OH! Thanks, all; I didn't do the math until after I sent the post
(obviously)!

No coffee yet : )

Sorry for wasting your time; many thanks again. Hope at least you'll
get half a laff from it with your colleagues. "You won't believe
what some bozo posted to the group this morning..."

Joe D.

Joe D. wrote:
> Hi all;
>
> I have an E450 running Solaris 2.8, not up to patch level for various
> reasons. I am attached via an Emulex HBA to a Network Appliance
> storage array. I want to mount the disks as simple slices (Veritas
> Volume Manager will not recognize the disks), and I am curious why I
> see more space on the file system than I have allocated. Here's an
> specific example:
>
> 1) created a 107GB LUN on the NetAPP filer
> 2) set the partition table on the device on the server for slice 0 to
> be the whole thing:
>
> Part Tag Flag Cylinders Size Blocks
> 0 root wm 0 - 6443 106.98GB (6444/0/0)
> 224354304
> 1 unassigned wu 0 0
> (0/0/0) 0
> 2 backup wu 0 - 6443 106.98GB (6444/0/0)
> 224354304
> 3 unassigned wm 0 0
> (0/0/0) 0
> 4 unassigned wm 0 0
> (0/0/0) 0
> 5 unassigned wm 0 0
> (0/0/0) 0
> 6 unassigned wu 0 0
> (0/0/0) 0
> 7 unassigned wm 0 0
> (0/0/0) 0
>
> 3) make a new file system specifying 1% minfree:
>
> [root@mcghosng:/] # newfs -m 1 /dev/rdsk/c6t500A098185C60EC2d25s0
> newfs: construct a new file system /dev/rdsk/c6t500A098185C60EC2d25s0:
> (y/n)? y
> /dev/rdsk/c6t500A098185C60EC2d25s0: 224354304 sectors in 6444
> cylinders of 16 tracks, 2176 sectors
> 109548.0MB in 2148 cyl groups (3 c/g, 51.00MB/g, 6208 i/g)
>
> ** Note that the geometry shows 109.5 GB in size? **
>
> 4) mount it up and check the space:
> [root@mcghosng:/] # mount -F ufs /dev/dsk/c6t500A098185C60EC2d25s0 /
> mnt
>
> [root@mcghosng:/] # df -k /mnt
> Filesystem kbytes used avail capacity Mounted on
> /dev/dsk/c6t500A098185C60EC2d25s0
> 110475886 9 109371119 1% /mnt
>
> As you can see, I have 110 GB of space as the size, of which 109 is
> available. What gives here?
>
> Any thoughts appreciated. I'm stumped/concerned
>
> Thanks as always.....
>
> Joe D.
>

A file system, even an empty file system, occupies disk space. Every
file the file system will support will require at least one inode. Each
and every inode occupies some modest amount of disk space. If I ever
knew exactly how much, I have long since forgotten. So that's where
your space has gone. Research into the internal workings of a UFS file
system is left as an exercise for the student!

On Jun 21, 2:10 pm, fer...@xanthia.com (Thomas H Jones II) wrote:
> In article <1182431287.064513.54...@q69g2000hsb.googlegroups. com>,
>
> Franco S. <franco_spen...@yahoo.com> wrote:
> >On Jun 21, 1:53 pm, "Joe D." <newbie_from_new...@yahoo.com> wrote:
> >> Hi all;
>
> >> I have an E450 running Solaris 2.8, not up to patch level for various
> >> reasons.
>
> >df -h /mnt
>
> Didn't thing "-h" was added to `df` until Solaris 9?
>
> -tom
> --
>
> "You can only be -so- accurate with a claw-hammer." --me

Oops, should of "read" the OP instead of "scanning" it

:-Z

[j.goerke@mobilcom.de]:
>
> 1024 KB = 1 MB
> 1024 MB = 1 GB
> 1048576 KB = 1024 MB = 1 GB

please get your units right. there is no such thing as "KB", it's
either kB (1000 bytes) or KiB (1024 bytes).

1024 B = 1 KiB
1024 KiB = 1 MiB
1048576 KiB = 1 GiB

1000 B = 1 kB
1000 kB = 1 MB
1000000 kB = 1 GB

--
Kjetil T.

Kjetil Torgrim Homme wrote:
> [j.goerke@mobilcom.de]:
>
>> 1024 KB = 1 MB
>> 1024 MB = 1 GB
>> 1048576 KB = 1024 MB = 1 GB
>
>
> please get your units right. there is no such thing as "KB", it's
> either kB (1000 bytes) or KiB (1024 bytes).
>
> 1024 B = 1 KiB
> 1024 KiB = 1 MiB
> 1048576 KiB = 1 GiB
>
> 1000 B = 1 kB
> 1000 kB = 1 MB
> 1000000 kB = 1 GB
>

This convention if, in fact, it is a convention, is a new one to me.
Perhaps I've been doing it wrong for the last forty years?