Jump to content
Welcome to our new Citrix community!

Increase space on VPX 13.1 21.x onwards


Joost Sannen

Recommended Posts

Hi,

 

According to the latest documentation it's finally possible to increase space on a VPX instance. See https://docs.citrix.com/en-us/citrix-adc/current-release/deploying-vpx/deploy-vpx-faq.html .

 

When trying this in a test environment I get the output below. And I'm a curious about the lines with 'Invalid argument'. I did not use hard links. How can I check if the new space is actually being used for the folders?

 

da1 at mpt0 bus 0 scbus2 target 1 lun 0
da1: <VMware Virtual disk 2.0> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 6000c291239e430c9169394e61acd307
da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
da1: Command Queueing enabled
da1: 20480MB (41943040 512 byte sectors)
da1: quirks=0x140<RETRY_BUSY,STRICT_UNMAP>
ns_physmem_init:
    reserving 3253929 (0x31a6a9) of 3909289 (0x3ba6a9) free pages
    (12710 (0x31a6) of 15270 (0x3ba6) MB) for Netscaler use
NS-KERN CPU Cycle Clock Based Rate: 3192MHz (319195340 Hz / 10 ticks)
NS-KERN skipping /dev/md0c...
Trying to mount root from ufs:/dev/md0 []...
random: unblocking device.

rc script started: rc.version 7.0-$Date netscaler.version=NetScaler NS13.1: Build 24.38.nc, Date: May 29 2022, 22:48:36   (64-bit)
Define disks configuration: da1 created
da1p1 added
da1p2 added
swapon: da0s1b: No such file or directory
swap.da1p2 da0s1b 
/ns-13.1-24.38 -> /flash/ns-13.1-24.38mv: rename /var/core/. to /var/crash/core/.: Invalid argument
mv: rename /var/core/.. to /var/crash/core/..: Invalid argument
mv: rename /var/nslog/. to /var/crash/nslog/.: Invalid argument
mv: rename /var/nslog/.. to /var/crash/nslog/..: Invalid argument
mv: rename /var/nsproflog/. to /var/crash/nsproflog/.: Invalid argument
mv: rename /var/nsproflog/.. to /var/crash/nsproflog/..: Invalid argument
mv: rename /var/nstrace/. to /var/crash/nstrace/.: Invalid argument
mv: rename /var/nstrace/.. to /var/crash/nstrace/..: Invalid argument
/dev/md0 on / (ufs, local)
devfs on /dev (devfs, local, multilabel)
procfs on /proc (procfs, local)
/dev/da0s1a on /flash (ufs, local, soft-updates)
/dev/da0s1e on /var (ufs, local, soft-updates)
/dev/da1p1 on /var/crash (ufs, local, soft-updates)

Link to comment
Share on other sites

3 hours ago, Carl Stalhood1709151912 said:

Does it work? If you "cd /var" and then run "ls -al", do you see the links for example /var/nslog going to /var/crash/nslog? The new path should have a new nslog file.

I can see the links.

 

core -> /var/crash/core
nslog -> /var/crash/nslog
nsproflog -> /var/crash/nsproflog
nstrace -> /var/crash/nstrace
 

nslog or /var/crash/nslog shows older files too. I don't know much about linking but this is how it's supposed to work?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...