Re: Please clarify /usr partition size for 6.9 release

2021-05-19 Thread Jay Hart
Ian,

Thanks for the reply. I figured maybe it was low issue for people and just 
wanted the list to know I resolved it so no time spent on it...

I reread the upgrade guide, and then looked at past upgrade guides and came to 
the conclusion the documentation just said you only needed
a partition for /usr greater in size than 1.1G, which I have (not that you 
needed 1.1GB of free space on the partition).  So I went ahead
and upgraded to 6.9, no issues noted...

The issue really is this: I set up this router years ago when the install 
documentation must have stated a [recommended] partition size
for /usr of 2.0GB.  2.0GB is the current partition size for /usr on this 
router.  I could be wrong on this.  Compared to other partitions
on this box /usr is far smaller than anything else...

/usr, right after I finished upgrading to 6.8 (all patches installed, 
ports/packages upgraded, sysclean ran, etc) had 783M free.  After
the same process going to 6.9, /usr has 813M free.

I really was/am concerned about running out of space on /usr.  I still am, and 
I could swap my /tmp and /usr partitions if I knew how to
do this...and, if the thought is /usr would fill up or cause issues in future 
upgrades.

I also have a /usr/obj, /usr/src, /usr/X11R6, etc., partitions.  All those have 
ample space.

Jay

>> Answered my own question.
>
> Posting that bare announcement to the list is either unnecessary
> (noise) or frustrating (no details provided).
>
> Future readers of your email who are facing the same problem might
> feel flummoxed, along the lines of, "Yes, but what was your answer?"
>
> Ian
>
> On 19/05/2021, Jay Hart  wrote:
>> Answered my own question.
>>
>> Jay
>>
>>> My partition size for /usr is 2.0G.  Currently using 1.1G, and df is
>>> reporting 783M available.
>>>
>>> Can I upgrade from 6.8 release to 6.9 release without the upgrade failing
>>> due to lack of space in /usr?
>>>
>>> I'm thinking I'm ok.
>>>
>>> In the future, would it be advisable to increase this partitions size?  I
>>> could swap /usr (2.0G) for /tmp (3.9G), if I had a process to do
>>> this.
>>>
>>> Thanks in Advance!
>>>
>>> Jay
>>>
>>>
>>
>>
>>
>




Re: Please clarify /usr partition size for 6.9 release

2021-05-18 Thread Jay Hart
Answered my own question.

Jay

> My partition size for /usr is 2.0G.  Currently using 1.1G, and df is 
> reporting 783M available.
>
> Can I upgrade from 6.8 release to 6.9 release without the upgrade failing due 
> to lack of space in /usr?
>
> I'm thinking I'm ok.
>
> In the future, would it be advisable to increase this partitions size?  I 
> could swap /usr (2.0G) for /tmp (3.9G), if I had a process to do
> this.
>
> Thanks in Advance!
>
> Jay
>
>




Please clarify /usr partition size for 6.9 release

2021-05-18 Thread Jay Hart
My partition size for /usr is 2.0G.  Currently using 1.1G, and df is reporting 
783M available.

Can I upgrade from 6.8 release to 6.9 release without the upgrade failing due 
to lack of space in /usr?

I'm thinking I'm ok.

In the future, would it be advisable to increase this partitions size?  I could 
swap /usr (2.0G) for /tmp (3.9G), if I had a process to do
this.

Thanks in Advance!

Jay



Re: change partition size impossible?

2016-02-24 Thread Josh Grosse

On 2016-02-24 07:55, dmitry.sensei wrote:

Like this:
http://daemonforums.org/showthread.php?t=5332


As the author of the guidance in that ancient forum thread, please note
that the recommendation in my first response to use one large filesystem 
should
be disregarded.  The prevalent use of disks larger than a BIOS is able 
to

address may cause boot problems -- as noted in FAQ 14.6.

I do think that the step-by-step "howto" I created for the thread's OP 
near
the end may be helpful, but only if it is understood that the whole 
point is

the procedure is to chaing the wings on our aircraft while we are parked
on the tarmac, and not currently in flight at 10,000 meters.

And, like any random "howto" one finds on the Interwebs, use with 
caution.

Never ever ever blindly copying and pasting *any* of it.  ANY OF IT.



On Wed, Feb 24, 2016 at 12:20 PM, Jaap Bosman  wrote:

Hello

Is it possible to change partition size in OpenBSD 5.9?

Try to change partition size on install: error message: "partition f 
is
currently 4194304 sectors in size and can have a maximum size of 
4194304

sectors."

Tried to use disklabel.
delete partition and make new one with preferred size  message is now 
"Open

partition would move or shrink"

I want partition l and f and e to change.

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd0a 1005M   51.8M903M 5%/
/dev/sd0l  298G   36.0K283G 0%/home -->  10 GB
/dev/sd0d  3.9G   10.0K3.7G 0%/tmp
/dev/sd0f  2.0G364M1.5G19%/usr --->  150 GB
/dev/sd0g 1005M210M745M22%/usr/X11R6
/dev/sd0h  9.8G218K9.3G 0%/usr/local
/dev/sd0k  2.0G2.0K1.9G 0%/usr/obj
/dev/sd0j  2.0G2.0K1.9G 0%/usr/src
/dev/sd0e 11.5G7.6M   10.9G 0%/var -->  150 GB

I am on amd64 OpenBSD_5.9

thanks

Jaap




Re: change partition size impossible?

2016-02-24 Thread Jaap Bosman

Problem solved.
I did a re install and edit the filesystem
first delete all partitions from d and above
than add all partitions and give the size I want.
and add mounted parts.

thanks again

On 24-02-16 wk8 08.20, Jaap Bosman wrote:

Hello

Is it possible to change partition size in OpenBSD 5.9?

Try to change partition size on install: error message: "partition f is
currently 4194304 sectors in size and can have a maximum size of 4194304
sectors."

Tried to use disklabel.
delete partition and make new one with preferred size  message is now
"Open partition would move or shrink"

I want partition l and f and e to change.

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd0a 1005M   51.8M903M 5%/
/dev/sd0l  298G   36.0K283G 0%/home -->  10 GB
/dev/sd0d  3.9G   10.0K3.7G 0%/tmp
/dev/sd0f  2.0G364M1.5G19%/usr --->  150 GB
/dev/sd0g 1005M210M745M22%/usr/X11R6
/dev/sd0h  9.8G218K9.3G 0%/usr/local
/dev/sd0k  2.0G2.0K1.9G 0%/usr/obj
/dev/sd0j  2.0G2.0K1.9G 0%/usr/src
/dev/sd0e 11.5G7.6M   10.9G 0%/var -->  150 GB

I am on amd64 OpenBSD_5.9

thanks

Jaap




Re: change partition size impossible?

2016-02-24 Thread dmitry.sensei
Like this:
http://daemonforums.org/showthread.php?t=5332

On Wed, Feb 24, 2016 at 12:20 PM, Jaap Bosman  wrote:
> Hello
>
> Is it possible to change partition size in OpenBSD 5.9?
>
> Try to change partition size on install: error message: "partition f is
> currently 4194304 sectors in size and can have a maximum size of 4194304
> sectors."
>
> Tried to use disklabel.
> delete partition and make new one with preferred size  message is now "Open
> partition would move or shrink"
>
> I want partition l and f and e to change.
>
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/sd0a 1005M   51.8M903M 5%/
> /dev/sd0l  298G   36.0K283G 0%/home -->  10 GB
> /dev/sd0d  3.9G   10.0K3.7G 0%/tmp
> /dev/sd0f  2.0G364M1.5G19%/usr --->  150 GB
> /dev/sd0g 1005M210M745M22%/usr/X11R6
> /dev/sd0h  9.8G218K9.3G 0%/usr/local
> /dev/sd0k  2.0G2.0K1.9G 0%/usr/obj
> /dev/sd0j  2.0G2.0K1.9G 0%/usr/src
> /dev/sd0e 11.5G7.6M   10.9G 0%/var -->  150 GB
>
> I am on amd64 OpenBSD_5.9
>
> thanks
>
> Jaap
>



-- 
Dmitry Orlov



change partition size impossible?

2016-02-24 Thread Jaap Bosman

Hello

Is it possible to change partition size in OpenBSD 5.9?

Try to change partition size on install: error message: "partition f is 
currently 4194304 sectors in size and can have a maximum size of 4194304 
sectors."


Tried to use disklabel.
delete partition and make new one with preferred size  message is now 
"Open partition would move or shrink"


I want partition l and f and e to change.

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd0a 1005M   51.8M903M 5%/
/dev/sd0l  298G   36.0K283G 0%/home -->  10 GB
/dev/sd0d  3.9G   10.0K3.7G 0%/tmp
/dev/sd0f  2.0G364M1.5G19%/usr --->  150 GB
/dev/sd0g 1005M210M745M22%/usr/X11R6
/dev/sd0h  9.8G218K9.3G 0%/usr/local
/dev/sd0k  2.0G2.0K1.9G 0%/usr/obj
/dev/sd0j  2.0G2.0K1.9G 0%/usr/src
/dev/sd0e 11.5G7.6M   10.9G 0%/var -->  150 GB

I am on amd64 OpenBSD_5.9

thanks

Jaap



Re: Partition size

2011-11-12 Thread Norman Golisz
Hi Leonardo,

On Fri Nov 11 2011 15:47, Leonardo M. Rami wrote:
> Hi, I have an 4.4OpenBSD server running on a VMWare ESXi server as a
> virtual machine. On the server, I configured a 21GB disk for this
> virtual machine, but it doesn't shows all that space, but this:
> 
> [root@openbsd44:~] # df -h
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/sd0a 1008M794M164M83%/
> /dev/sd0d  5.9G5.2G380M93%/var
> 
> 
> [root@openbsd44:~] # fdisk sd0
> Disk: sd0   geometry: 1174/255/63 [18874368 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
>  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
> *3: A6  0   1   1 -   1043 254  63 [  63:16771797 ] OpenBSD
> 
> How can I let the operating system see the whole disk?.

as you can see, fdisk(8) only shows 9216 MB in total for this disc.
Are these 21 GBs the original virtual disc's capacity, or did you enlarge
it afterwards? In the latter, you would have to extend the OpenBSD
partition to the new sector boundary, effectively enlarging it,
repartition your disklabel(8) and possibly growfs(8) your filesystems.

Norman.

PS: Your OBSD installation is antiquated. Consider upgrading.



Partition size

2011-11-11 Thread Leonardo M . Ramé
Hi, I have an 4.4OpenBSD server running on a VMWare ESXi server as a
virtual machine. On the server, I configured a 21GB disk for this
virtual machine, but it doesn't shows all that space, but this:

[root@openbsd44:~] # df -h
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd0a 1008M794M164M83%/
/dev/sd0d  5.9G5.2G380M93%/var


[root@openbsd44:~] # fdisk sd0
Disk: sd0   geometry: 1174/255/63 [18874368 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
*3: A6  0   1   1 -   1043 254  63 [  63:16771797 ] OpenBSD

How can I let the operating system see the whole disk?.

Thanks in advance,
-- 
Leonardo M. Rami
Medical IT - Griensu S.A.
Av. Colsn 636 - Piso 8 Of. A
X5000EPT -- Csrdoba
Tel.: +54(351)4246924 +54(351)4247788 +54(351)4247979 int. 19
Cel.: +54(351)156629292



Re: mount_mfs partition size (sparc64)

2009-04-27 Thread Michael
Hi,

Otto Moerbeek wrote:
> You missed some context. Look at the #if 0 a few lines higher.

Just to clarify... because of some weird thing (bug?) it can only use 32
bit even though the arch is actually 64 bit?

>From the 32-bit part of: /usr/src/sys/arch/sparc64/include/vmparam.h

 * This is silly.  Apparently if we go above these numbers
 * integer overflows in other parts of the kernel cause hangs.


Michael



Re: mount_mfs partition size (sparc64)

2009-04-27 Thread Otto Moerbeek
On Mon, Apr 27, 2009 at 10:30:45AM +0200, Michael wrote:

> Hi,
> 
> when trying to create a mfs file system I can never get is larger than 1
> GB even though I actually got >6 GB of free RAM.
> 
> Depening on how close I get to the 1 GB barrier I see the following
> error messages. The last attempt was successfull, but that doesn't mean
> that,l even though it was successfull now, it will be again... the limit
> seems to be varying.
> 
> # mount_mfs -s 2097000 swap /mnt && umount /mnt
> mount_mfs: mmap: Cannot allocate memory
> 
> # mount_mfs -s 2096900 swap /mnt && umount /mnt
> mount_mfs: calloc failed
> 
> # mount_mfs -s 2096833 swap /mnt && umount /mnt
> mount_mfs: cannot allocate I/O buffer
> 
> # mount_mfs -s 2096832 swap /mnt && umount /mnt
> 
> ... wait some time ...
> 
> # mount_mfs -s 3096832 swap /mnt && umount /mnt
> mount_mfs: mmap: Cannot allocate memory
> 
> 
> The manpage of mfs says the following:
> 
> Note however that for mount_mfs the practical limit is based on datasize
> in login.conf(5), and ultimately depends on the per-arch MAXDSIZ limit.
> 
> Well, the datasize is set ti infinity for root (daemon) so it must be
> MAXDSIZ that is set in /usr/src/sys/arch/sparc64/include/vmparam.h and
> describes as values in byte.
> 
> for 64 bit
> #define MAXDSIZ (512L*1024*1024*1024)   /* max data size */
> 
> for 32 bit
> #define MAXDSIZ (1*1024*1024*1024)  /* max data size */
> 
> What does that 512L for 64 bit mean? However, if I read that correctly,
> I should be able to allocate way more than just ~1 GB of memory for each
> MFS partition?
> 
> Is anyone here able to enlighten me? Is ~1 GB the limit or do I miss
> something?

You missed some context. Look at the #if 0 a few lines higher.

-Otto



mount_mfs partition size (sparc64)

2009-04-27 Thread Michael
Hi,

when trying to create a mfs file system I can never get is larger than 1
GB even though I actually got >6 GB of free RAM.

Depening on how close I get to the 1 GB barrier I see the following
error messages. The last attempt was successfull, but that doesn't mean
that,l even though it was successfull now, it will be again... the limit
seems to be varying.

# mount_mfs -s 2097000 swap /mnt && umount /mnt
mount_mfs: mmap: Cannot allocate memory

# mount_mfs -s 2096900 swap /mnt && umount /mnt
mount_mfs: calloc failed

# mount_mfs -s 2096833 swap /mnt && umount /mnt
mount_mfs: cannot allocate I/O buffer

# mount_mfs -s 2096832 swap /mnt && umount /mnt

... wait some time ...

# mount_mfs -s 3096832 swap /mnt && umount /mnt
mount_mfs: mmap: Cannot allocate memory


The manpage of mfs says the following:

Note however that for mount_mfs the practical limit is based on datasize
in login.conf(5), and ultimately depends on the per-arch MAXDSIZ limit.

Well, the datasize is set ti infinity for root (daemon) so it must be
MAXDSIZ that is set in /usr/src/sys/arch/sparc64/include/vmparam.h and
describes as values in byte.

for 64 bit
#define MAXDSIZ (512L*1024*1024*1024)   /* max data size */

for 32 bit
#define MAXDSIZ (1*1024*1024*1024)  /* max data size */

What does that 512L for 64 bit mean? However, if I read that correctly,
I should be able to allocate way more than just ~1 GB of memory for each
MFS partition?

Is anyone here able to enlighten me? Is ~1 GB the limit or do I miss
something?

Thanks in advance,

Michael


OpenBSD 4.4-current (GENERIC.MP) #585: Fri Jan  9 11:36:04 MST 2009
t...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP
real mem = 8589934592 (8192MB)
avail mem = 8367955968 (7980MB)
mainbus0 at root: Sun Fire V440
cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz
cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K
external (64 b/l)
cpu1 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz
cpu1: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K
external (64 b/l)
cpu2 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz
cpu2: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K
external (64 b/l)
cpu3 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz
cpu3: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K
external (64 b/l)
"memory-controller" at mainbus0 not configured
"memory-controller" at mainbus0 not configured
"memory-controller" at mainbus0 not configured
"memory-controller" at mainbus0 not configured
schizo0 at mainbus0: "Tomatillo", version 4, ign 700, bus A 0 to 0
schizo0: dvma map c000-dfff
pci0 at schizo0
cas0 at pci0 dev 2 function 0 "Sun Cassini" rev 0x20: ivec 0x718,
address 00:03:ba:66:75:d1
brgphy0 at cas0 phy 1: BCM5421 10/100/1000baseT PHY, rev. 1
"ppm" at mainbus0 not configured
schizo1 at mainbus0: "Tomatillo", version 4, ign 740, bus B 0 to 0
schizo1: dvma map c000-dfff
pci1 at schizo1
mpi0 at pci1 dev 2 function 0 "Symbios Logic 53c1030" rev 0x08: ivec 0x740
scsibus0 at mpi0: 16 targets, initiator 7
schizo2 at mainbus0: "Tomatillo", version 4, ign 780, bus A 0 to 0
schizo2: dvma map c000-dfff
pci2 at schizo2
ebus0 at pci2 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00
"flashprom" at ebus0 addr 0-f, 290-290 not configured
rtc0 at ebus0 addr 70-71: m5819p
pcfiic0 at ebus0 addr 320-321 ivec 0x1b
iic0 at pcfiic0
"SUNW,i2c-imax" at iic0 addr 0xb not configured
"SUNW,i2c-imax" at iic0 addr 0xc not configured
admtemp0 at iic0 addr 0x18: max1617, cannot get control register
"pca9555" at iic0 addr 0x21 not configured
"pca9555" at iic0 addr 0x22 not configured
"pca9555" at iic0 addr 0x23 not configured
"pca9555" at iic0 addr 0x24 not configured
"adm1026" at iic0 addr 0x2e not configured
admtemp1 at iic0 addr 0x32: max1617, cannot get control register
admtemp2 at iic0 addr 0x40: max1617, cannot get control register
admtemp3 at iic0 addr 0x48: max1617, cannot get control register
lmtemp0 at iic0 addr 0x4e: lm75, fails to respond
"spd" at iic0 addr 0x5b not configured
"spd" at iic0 addr 0x5c not configured
"spd" at iic0 addr 0x5d not configured
"spd" at iic0 addr 0x5e not configured
"spd" at iic0 addr 0x63 not configured
"spd" at iic0 addr 0x64 not configured
"spd" at iic0 addr 0x65 not configured
"spd" at iic0 addr 0x66 not configured
"spd" at iic0 addr 0x6b not configured
"spd" at iic0 addr 0x6c not configured
"spd" at iic0 addr 0x6d not configured
"spd" at iic0 addr 0x6e not configured
"spd" at iic0 addr 0x73 not configured
"spd" at iic0 addr 0x74 not configured
"spd" at iic0 addr 0x75 not configured
"spd" at iic0 addr 0x76 not configured
"ics951601" at iic0 addr 0x69 not configured
power0 at ebus0 addr 800-82f ivec 0x1a
com0 at ebus0 addr 3f8-3ff ivec 0x22: ns16550a, 16 byte fifo
com1 at ebus0 addr 2e8-2ef ivec 0x22: ns16550a, 16 byte fifo
"rmc-comm" at ebus0 addr 3e8-3ef ivec 0x22 not configured
cas1 at pci2 dev 2 function 0 "NS Saturn" rev 0x30: ivec