A colleague was attempting to recreate a WPAR. The WPAR had previously
been removed using the WPAR Manager Web GUI. This worked, or so he tells me!

Anyway, when he tried to create the WPAR again from the GUI, using
the same WPAR name (wpar20), it
failed. The error claimed that /wpars/wpar20
already existed. But it didn’t!

Now, before I go any further, looking back at the issue now, it is
pretty obvious what the problem might have been. However, the solution was not
evident at first. This proves one thing for certain: some problems cannot be
resolved without TWO cups of coffee in the morning.

Of course, I resorted to the command line to see what was REALLY
happening.

The mkwpar command was
indeed complaining that /wpars/wpar20 already existed.

#
mkwpar -n wpar20

mkwpar:
0960-288 The /wpars/wpar20 file system already exists.

mkwpar:
0960-417 Specify -p to create this workload partition using the existing file
system data.

I could not find any directory or file system with that name,
anywhere under /wpars or elsewhere.

#
ls -l /wpars/wpar20

/wpars/wpar20
not found

#
ls -l /wpars

total
0

#

#
df –g | grep –i wpar

#

#
lsvg | lsvg –il | grep –i wpar

#

I ran the mkwpar with truss to try to find out where it was
finding the reference to /wpars/wpar20.
At this point you have probably already determined where the problem might be!

The truss output
pointed me in the direction of /etc/filesystems.....of
course! Another “facepalm“ moment!

#
truss mkwpar -n wpar20 > /tmp/wpar20 2>&1

#
vi /tmp/wpar220

statx("/wpars/wpar20",
0x30008AB8, 128, 010) = -1

kopen("/etc/filesystems", O_RDONLY|O_LARGEFILE) =
4

Whatever my learned colleague had done when he “removed” the WPAR
with the GUI, it left entries for the WPARs file systems in /etc/filesystems.