mkfs problem: "Filesystem helper: Access denied or could not execute"

[BARBID]

I have a AIX 4.3 system on which I am trying to do mkfs on a logical volume I created as follows:

/usr/sbin/mkfs -V jfs -s 65536 /dev/hd4

to which I am getting the error message:

Filesystem Helper: Access denied or could not execute


Can some expert tell me what I am missing? I have tried many variations of mkfs arguments and tried to supply more arguments than the above, but same result.

 

[MoshiachNow]

HI,

Please post the results of:

1.df
2.lslv hd4
3.ls -la /usr/sbin/mkfs
4.whoami
5.Is /dev/hd4 big enough for a filesystem size you have chosen (65536) ?
"Long live king Moshiach !"
h

http://www.noahide.com/movement.htm

 

[risc6k]

Hi! BARBID
If you got already hd4, you couln't excute mkfs commands
If you want to increase hd4 size, excute chfs commands
of cause you've got root permit.
hope to help
sorry for bed english
thanks & regards

 

[MoshiachNow]

risc6k ,

If you run the above the system will prompt you for a confirmation to delete the existing LV.
"Long live king Moshiach !"
h

http://www.noahide.com/movement.htm

 

[DSMARWAY]

Hi,

hd4 is the root filesystem, you are trying to re-create it with mkfs , you don't want to delete this.
I suspect all you want to do is increase the size , you can do this via smit or chfs command ( man chfs) OR
if you want to create a new one specify a new device.

 

[BARBID]

To answer levw's questions:

1) df Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/ram0 237120 218680 8% 243 1% / 192.168.1.58:/aixSPOT/usr 14120552 7093176 50% 114783 13% /usr

Note that I am using a client that is booted as a diskless machine but actually has local disks

2) lslv hd4 LOGICAL VOLUME: hd4 VOLUME GROUP: vg00 LV IDENTIFIER: 000a775aa72ebeb8.4 PERMISSION: read/write VG STATE: active/complete LV STATE: closed/syncd TYPE: jfs WRITE VERIFY: off MAX LPs: 512 PP SIZE: 32 megabyte(s) COPIES: 1 SCHED POLICY: parallel LPs: 1 PPs: 1 STALE PPs: 0 BB POLICY: relocatable INTER-POLICY: maximum RELOCATABLE: yes INTRA-POLICY: middle UPPER BOUND: 32 MOUNT POINT: N/A LABEL: / MIRROR WRITE CONSISTENCY: on EACH LP COPY ON A SEPARATE PV ?: yes

3)
ls -la /usr/sbin/mkfs -r-xr-xr-x 1 daemon staff 14358 Mar 19 2001 /usr/sbin/mkfs

4) whoami
root

5) yes (as you can see from (2) above).

I suspect that the problem is that I have something missing from my /etc or root directory since I have my own spot for both /usr and / file systems

 

[BARBID]

BTW: doing fsck also gives me the same "Filesystem helper: access denied..." error message. And I think the root cause is the same.

 

[BARBID]

I found the problem, but when I fixed it I ran into another problem:

It seems the problem on my machine was that the file /sbin/helpers/v3fshelper was missing and that caused the cryptic message to appear. When I copied that file from another (4.3) system. The mkfs started working but then I was unable to nfs mount any remote directories which was working perfectly fine before the mkfs using v3fshelper.
The nfs mount gives the following message:

Giving up on:
192.168.1.58:/opt/bapps
vmount: Invalid argument

Now I don't understand why making v3fshelper available and using it once with mkfs messes up NFS mounting. I then noticed the rc.dd_boot file also deleted v3fshelper and that must be because there is a known problem with using v3fshelper on diskless/dataless machines. Any expert advice?